JBT – Joomla Branches Tester

Imagine a little slice of a parallel universe where testing different Joomla versions becomes a fluffy, cosy and almost magical experience. In this universe, you can effortlessly test with the Patch Tester, glide through the Cypress GUI, or even enjoy the smooth efficiency of Cypress Headless. Picture the warmth of being able to peer into any database table as if through a magical glass, or seamlessly switch between five different database variants with just a small wave of a magic wand. Wouldn't that create a truly fluffy and cosy environment to work in?

Alright, alright, apologies to those who enjoyed the whimsical writing style, but now it's time to dive into the technical depths. Let's transition from the cozy, magical universe into the world of technical documentation, where we'll explore the numerous options, parameters and configurations that power this experience ...

Software Architecture

Within Docker container environment you are able to:

Use almost 300 different Joomla versions, based on the Git development branches or Git tags (Joomla 3.9.0 ... 6.0-dev).
Running one Joomla version or multiple Joomla versions in parallel.
Manual testing, including database inspections and email verifications.
Running Joomla System Tests with Cypress in interactive mode (GUI) or automated mode (headless or with noVNC).
Executing unit tests, verifying coding standards and checking CSS styles and JavaScript standards, just like Drone.
Automated Joomla Patch Tester installation.
Apply pull requests (PR) from Git repositories joomla-cms, joomla-cypress and joomla-framework/database.
Switching between 8 database variants (MySQL, MariaDB, or PostgreSQL and the two database drivers: MySQLi or PHP Data Objects and the option to use Unix sockets, instead of TCP host).
Switching between PHP versions (PHP 7.4 ... 8.3).
Installing Joomla from a cloned 'joomla-cms' Git repository.
Grafting a Joomla package.
Using Xdebug for PHP debugging.
Using IPv6 network.

The software architecture picture shows the simplest installation with only one Joomla 5.2 web server container plus the 9 base containers. You'll notice the one orange Joomla 5.2 Web Server container, based on the joomla-52 folder, which is available inside and outside Docker. On the right, you can see the three blue containers running the databases: MySQL, MariaDB and PostgreSQL. To inspect the databases, two additional blue containers are included: phpMyAdmin (for MySQL and MariaDB) and pgAdmin (for PostgreSQL). A green Docker container runs Cypress-based Joomla System Tests, either with a GUI or in headless mode. The green noVNC container enables real-time viewing of automated Cypress System Tests. If you need to investigate a failed test spec, you can easily switch to running Cypress with the interactive GUI.

The red mail relay container triplicates all emails sent during manual Joomla tests or System Tests. The second red mail catcher container makes these emails accessible via a web application for easy review.

On the Docker Host system (left side), your red web browser is running. On macOS and Ubuntu, the native Cypress GUI is displayed in green.

The Joomla Docker images are from the official images for Joomla (see docker-joomla and the Docker Hub page). Thank you! 🙏

Everything is fully scripted and can be easily parameterised for maximum flexibility. The /scripts folder serves as the source of JBT functionality. Ensure that your current working directory is always the joomla-branches-tester directory.

👉 For the complete list of all scripts see scripts/README.md.

🧚 "The scripts have a sprinkle of hacks and just a touch of magic to keep things fluffy. For those with a taste for the finer details, the comments are a gourmet treat."

By default (without specifying a Joomla version number) scripts/create takes all used Joomla development branches. Used Joomla development branches refer to the GitHub joomla-cms repository, including default, active and stale branches. At the beginning of November 2024, these are 4.4-dev, 5.1-dev, 5.2-dev, 5.3-dev and 6.0-dev.

👉 Since used branches are subject to frequent changes, the latest version numbers are always be retrieved directly from the joomla-cms repository.

For the web server containers, the official Docker Joomla images (e.g., 5.2-php8.3-apache) are used as a starting point to simplify life. Within the container, the source code from the corresponding Joomla Git development branch or tag is copied and a second Joomla installation is run. Refer to the Versions section for a list of all usable Joomla versions and Docker images available for each Joomla version.

JBT Parallel Installation Environment

JBT has its own Cypress installation environment located in the installation folder. This environment includes Cypress, the latest main branch version of joomla-cypress and three Cypress scripts:

Install Joomla
Disable Joomla B/C plugins
Install and configure Joomla Patch Tester

The scripts capture Joomla web application JavaScript errors to prevent Cypress from stopping unexpectedly. The JavaScript errors are displayed, logged and can be verified using scripts/check.

Furthermore, the installation environment saves each Joomla release's installation folder to preserve it and restore it if needed for the next Joomla installation, e.g. when switching databases after grafting.

Version Naming

With scripts/create, Joomla versions need to be specified as a Git branch (e.g., 5.2-dev) or a Git tag (e.g., 5.1.1-rc1).
When creating an instance from a Git branch, either the full branch name or just the major and minor version numbers can be used (e.g., 52 instead of 5.2-dev).
Once the Joomla instances are created, all other scripts use only the major and minor version numbers.
For example, an instance created from the Git tag 3.10.12 runs as jbt-310, and you can use 310 throughout to specify the instance.

See the detailed list of Docker containers.

The abbreviation jbt stands for Joomla Branches Tester.

Name	Docker IPs	Host Port: Container Inside	Directory ✳️	Comment
jbt-mya	10.0.0.2 fd00::2	7002		Web App to manage MariaDB and MySQL auto-login configured, root / root
jbt-pga	10.0.0.3 fd00::3	7003		Web App to manage PostgreSQL auto-login configured, root / root, postgres / prostgres
jbt-mail	10.0.0.4 fd00::4	7004 SMTP 7225:1025		Web interface to verify emails.
jbt-novnc	10.0.0.5 fd00::5	7005		If you run automated Cypress System Tests with the `novnc` option, you can watch them.
jbt-relay	10.0.0.6 fd00::6	SMTP 7025:7025		SMTP relay triplicator
jbt-cypress	10.0.0.7 fd00::7	SMTP :7125		Cypress Headless Test Environment SMTP server is only running during test execution
jbt-mysql	10.0.0.11 fd00::11 ✴️	7011:3306		Database Server MySQL version 8.1
jbt-madb	10.0.0.12 fd00::12	7012:3306		Database Server MariaDB version 10.4
jbt-pg	10.0.0.13 fd00::13	7013:5432		Database Server PostgreSQL version 12.20
jbt-39	10.0.0.39 fd00::39	7039	/joomla-39	Web Server Joomla e.g. tag 3.9.28 user ci-admin / joomla-17082005
jbt-310	10.0.3.10 fd00::310	7310	/joomla-310	Web Server Joomla e.g. tag 3.10.12 user ci-admin / joomla-17082005
...
jbt-53	10.0.0.53 fd00::53	7053	/joomla-53	Web Server Joomla e.g. 5.3-dev user ci-admin / joomla-17082005
jbt-60	10.0.0.60 fd00::60	7060	/joomla-60	Web Server Joomla e.g. 6.0-dev user ci-admin / joomla-17082005

✳️ The directories are available on the Docker host inside /jbt to:

Inspect and change the configuration files (configuration.php or cypress.config.mjs),
To edit the test specs below tests/System or
To inspect screenshots from failed tests or
To inspect and hack the Joomla sources from Docker host system.

✴️ Gnome: "Yes, yes, I know that 11 in decimal is B in hex, but can you instantly recall that 44 is 2C? That's why, for easier visual recognition, we're sticking with 11 — it just needs to be unique!"

👉 Using host.docker.internal ensures consistent hostnames and URLs between containers and the Docker host machine. However, there are exceptions to note:

Database Performance: For database connections, the Docker container name and the default database port are used to avoid performance issues.
Running Cypress GUI on the Docker host: localhost and the mapped database port are used instead, as Docker container hostnames aren't accessible outside Docker, and no performance issues have been observed in this configuration.

Therefore, there is a separate Cypress configuration file cypress.config.local.mjs for the local execution of Cypress GUI on the Docker host.

Prerequisites

All you need is the ability to run Git, Docker and Bash scripts. Thanks to Docker, it is not necessary to install one of the databases, the database management tools, PHP, Node or Composer.

Git, Docker and a bash scripting environment are required and must be installed. The following /etc/hosts entry will be created:

127.0.0.1 host.docker.internal

Setup Script for Ubuntu (Native and WSL 2 on Windows)

For setting up and configuring an Ubuntu Linux environment with required Git, Docker and firewall configuration, one of the helpful gnomes has crafted the ubuntu_setup.sh script. This script is designed to work on both a fresh Ubuntu desktop installation and Ubuntu running on Windows Subsystem for Linux (WSL).

Download the script as raw file to any directory and run in terminal window with superuser privileges:

sudo bash ./ubuntu_setup.sh

After the script completes, please run sudo reboot. Once your system has rebooted, verify the Docker installation by running docker ps.

Installation

Last tested in early November 2024 with:

Intel chip macOS 15 Sequoia,
Apple silicon macOS 15 Sequoia,
Windows 11 Pro WSL 2 Ubuntu and
Ubuntu 24 Noble Numbat (the absolute minimum, if you also wish to use the Cypress GUI, is a VPS with 2 shared vCPUs and 4 GB RAM).

You can create all base Docker containers and the current (early November 2024) five Joomla dev-branch containers using scripts/create without any arguments:

git clone https://github.com/muhme/joomla-branches-tester
cd joomla-branches-tester
scripts/create

👉 The script can run without sudo, but depending on the platform, it may ask you to enter your user password for individual sudo actions.

The initial scripts/create runs some time, especially the very first time when the Docker images still need to be downloaded. For this installation with five Joomla web server containers the joomla-branches-tester folder requires about 2 GB of disc space. Docker needs additionally about 20 GB for images and volumes. If you are installing for the first time and downloading all necessary Docker images, you will need to download approximately 4 GB of data over the network.

Optional scripts/create Parameters

Install can use multiple Joomla versions, e.g. two tags and two dev-branches 3.9.28 3.10.12 52 60 (your system architecture will look like the picture on the right), defaults to all dev-branches.
The used database and database driver, e.g. pgsql, defaults to use MariaDB with MySQLi driver.
The used PHP version. For available PHP versions see Versions section. Defaults to highest. See more details in Switch PHP Version.
Instead using joomla-cms repository, you can specify a different Git repository and branch. For example, using https://github.com/Elfangor93/joomla-cms:mod_community_info. In this case, exactly one version must be provided, and it should match the version of the given joomla-cms cloned repository.
The Docker jbt-network, used by all containers, defaults to IPv4. To use IPv6, run the script with the IPv6 option.
The optional recreate option is used to create or recreate one Joomla web server container for the specified version. Base containers and unnamed Joomla web server containers remain unchanged.
To force a fresh build with no-cache, defaults to build from cache.

👉 In case of trouble, see Trouble-Shooting.

For the different operating systems, there are more detailed descriptions available:

Windows WSL2 Ubuntu Setup

Install Windows WSL 2 (if not already installed). Open PowerShell Window with administrator rights and run:
```
wsl --install -d Ubuntu
```
Restart your computer after the installation.
Install Ubuntu by creating a user and setting a password. Open PowerShell as a regular user and run:
```
wsl --install Ubuntu
```
👉 In the future, simply type wsl to start WSL 2 with Ubuntu.

Install git inside WSL 2 Ubuntu:

sudo apt-get update
sudo apt-get -y upgrade
sudo apt-get -y install git

Clone Joomla Branches Tester repository e.g. in your home directory:

cd
git clone https://github.com/muhme/joomla-branches-tester

Continue the installation with the Ubuntu setup script:
```
cd ~/joomla-branches-tester
sudo scripts/ubuntu_setup.sh
```
To run Docker as regular user it is needed to restart Ubuntu:
```
sudo reboot
```
Open WSL again and verify Docker is running and you have access without sudo:
```
docker ps
```
Should show no containers:
```
CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES
```
👉 It may take a moment for the Docker service to run. This can also be checked with sudo service docker status command.
Create a hosts entry on Windows to map host.docker.internal to 127.0.0.1, follow these steps:
- Open Notepad as Administrator
  - Press the Start button, type Notepad.
  - Right-click on Notepad and select Run as administrator.
- Open the Hosts File:
  - In Notepad, click File -> Open.
  - Navigate to the hosts file location: C:\Windows\System32\drivers\etc\.
  - In the Open dialog, make sure to select All Files (*.*) in the file type dropdown at the bottom right (since the hosts file doesn't have a .txt extension). Select the hosts file and click Open.
- Add the Host Entry:
  - At the end of the file, add a new line with the following entry:
```
127.0.0.1 host.docker.internal
```
- Save the Hosts File:
  - Click File -> Save to save your changes.
- Test the New Hosts Entry:
  - Open Windows Command Prompt Terminal and ping the host.docker.internal to ensure it resolves to 127.0.0.1:
```
ping host.docker.internal
```
    It should return responses from 127.0.0.1.
Now you are ready to create Joomla Branches Tester. Open WSL Ubuntu and run:
```
cd ~/joomla-branches-tester
scripts/create
```

👉 To run the interactive Cypress GUI from the Docker container jbt-cypress, Windows 11 (with included Windows Subsystem for Linux GUI – WSLg) is required.

macOS Setup

To install the required Docker and Git, one possible approach is to follow these four steps:

Install Docker Desktop on Mac for either Apple silicon or Intel chip and then run it.

Verify Docker is running:

docker ps

Should show no containers:

CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES

Install Homebrew and follow the instructions to add /opt/homebrew/bin to your PATH.
Install git

brew install git

Once Docker and Git are installed, open a terminal window, clone the repository and create the Joomla Branches Tester:

git clone https://github.com/muhme/joomla-branches-tester
cd joomla-branches-tester
scripts/create

If you like to run Cypress GUI locally you have to install Node.js. Actual use LTS version 20 and follow the instructions to extend PATH:

brew install node@20
echo 'export PATH="/opt/homebrew/opt/node@20/bin:$PATH"' >> ~/.zshrc

You can now run System Tests using the Cypress GUI locally. The script will automatically install the appropriate version specified for each instance the first time you open it:

scripts/cypress 53 local

Ubuntu Setup

Installing the Joomla Branches Tester on Ubuntu with a user that is able to run sudo.

To setup Git, Docker and firewall configuration download the ubuntu_setup.sh script as a raw file, run in terminal window with superuser privileges and reboot the system:
```
sudo bash ./ubuntu_setup.sh
sudo reboot
```

Clone Joomla Branches Tester repository e.g. in your home directory:

cd
git clone https://github.com/muhme/joomla-branches-tester

Now you are ready to create Joomla Branches Tester:
```
cd ~/joomla-branches-tester
scripts/create
```

Usage

Joomla Configuration

The Joomla development version installed in the web server container is configured with the following settings:

Joomla Super User: ci-admin with the password joomla-17082005 (used from CI System Tests).
Used language Pack is English (United Kingdom) (en-GB).
The /installation folder remains intact after the installation.
- Earlier Joomla versions delete the /installation folder after setup. If the folder is missing, it is checked out from Git during the next installation.
Error Reporting is set to Maximum in Global Configuration | Server.
A cron job is configured to run the Joomla Task Scheduler every minute.
The 'System - Joomla! Statistics' plugin is disabled to prevent prompting users on the backend Home Dashboard.
The 'Behaviour - Backward Compatibility' plugins are disabled to detect backward compatibility issues.
The automatic run of the 'Welcome to Joomla!' guided tour is canceled from Joomla version 5.1 onwards.
Not configured for logging, due to deprecation warnings.

Manual Testing

From your Docker Host system you can test the Joomla Frontend e.g. for Joomla release 5.2 with http://host.docker.internal:7052 and the backend http://host.docker.internal:7052/administrator. User ci-admin and password joomla-17082005 (Whose birthday is it anyway?) are from Joomla System Tests.

In parallel you can inspect MariaDB and MySQL database with phpMyAdmin on http://host.docker.internal:7002 or PostgreSQL database with pgAdmin on http://host.docker.internal:7003. And verify all emails from Joomla and the System Tests with MailDev on http://host.docker.internal:7004.

If you need to inspect files, they are available in the directory joomla-52 for this Joomla release 5.2 sample.

Drone-like Tests

A subset of seven tests from the full Joomla Drone CI test suite has been implemented:

php-cs-fixer – PHP Coding Standards Fixer (dry-run)
phpcs – PHP Coding Sniffer
unit - PHP Testsuite Unit
lint:css - CSS Linter
lint:js - JS Linter
lint:testjs – JS Linter for Tests
system – System Tests

Running all seven tests on all instances is simple with the following command:

scripts/test

Some optional arguments are:

Joomla version number(s): Choose one or multiple versions; all versions are tested by default.
Test name(s): Choose one or multiple tests; all tests are executed by default.

For example run the linter tests on three Joomla instances:

scripts/test 51 52 53 lint:css lint:js lint:testjs

To avoid issues with running php-cs-fixer, the auto-generated file administrator/cache/autoload_psr4.php is corrected beforehand. And the configurations for php-cs-fixer and phpcs has been extended to exclude the com_patchtester component.

👉 The PHP Unit Test Suite integration and the Phan static analyzer for PHP have not been implemented. Additionally, the tests are not configured to run on multiple PHP versions, as Drone typically does in the Joomla CI environment.

Cypress Automated System Tests

To simply run the Joomla System Tests with all specs - except for the installation step - from the Joomla System Tests in all Joomla instances with headless Cypress:

scripts/test system

🧚 "To protect you, the first step Installation.cy.js of the Joomla System Tests is excluded in the automated tests if you run all test specs. If you run the installation, this can lead to inconsistencies between the file system and the database, as the Joomla database will be recreated.

Some more optional arguments for System Tests are:

Browser to be used: Choose between electron (default), firefox, chrome, or edge.
Test spec pattern: All test specs (except the installation) are used by default.

As an example, run all the test specs (except the installation) on 5.1 instance with Mozilla Firefox:

scripts/test 51 system firefox

Run one test spec with default Electron in all Joomla instances (of course, Cypress System Tests and the spec must exist):

scripts/test system administrator/components/com_users/Users.cy.js

👉 When specifying a single test spec file, you can omit the tests/System/integration/ path at the beginning.

Test all site specs with Microsoft Edge in the Joomla instances 5.1, 5.2 and 5.3 using a pattern:

scripts/test 51 52 53 system edge 'tests/System/integration/site/**/*.cy.{js,jsx,ts,tsx}'

One more optional argument is novnc. The jbt-vnc container allows to view the automated browser tests via the web-based VNC viewer noVNC. This is useful for watching the automated Cypress System Tests in real-time, for example, when the gnome is too impatient to wait for the 120-second timeout from installJoomla again. In this case Cypress runs headed and uses jbt-vnc as DISPLAY and you can watch the execution of the automated tests with the URL:

http://host.docker.internal:7005/vnc.html?autoconnect=true&resize=scale

scripts/test 53 system novnc administrator/components/com_users/Users.cy.js

To additional show console.log messages from Electron browser by setting environment variable:

export ELECTRON_ENABLE_LOGGING=1
scripts/test 44 system administrator/components/com_actionlogs/Actionlogs.cy.js

Cypress Interactive System Tests

If a test spec fails, the screenshot is helpful. More enlightening is to execute the single failed test spec with the Cypress GUI in interactive mode. You can see all the Cypress log messages, use the time-traveling debugger and observe how the browser runs in parallel.

Cypress GUI can be started from Docker container jbt-cypress with X11 forwarding (recommended for Windows 11 WSL 2 Ubuntu):

scripts/cypress 51

Or from locally installed Cypress (recommended for macOS and native Ubuntu) with additional argument local:

scripts/cypress 51 local

The script will automatically install the appropriate Cypress version locally for each Joomla instance if it doesn't already exist. Using the Cypress container has the advantage of having Chrome, Edge, Electron and Chromium browsers pre-installed. If you run Cypress locally, only the browsers installed on your Docker host system will be available.

👿 Are you see the Installation.cy.js test spec? Here you finally have the chance to do it. Who cares about Database and File System Consistency? Go on, click on it. Go on, go on ...

Check Email

To check the emails sent by Joomla, the MailDev container provides you with a web interface at http://host.docker.internal:7004. The Cypress based Joomla System Tests is using an own SMTP server smtp-tester to receive, check and delete emails. Since we run Cypress locally or in a container, it is necessary to triple emails. This is done by the SMTP relay triplicator jbt-relay.

🧚 "Oh, dear Gnome, now I can really read all the emails from the System Tests, thank you."

👿 "Postal dispatch nonsense picture? Don't open it, you'll get a triple headache!"

🧚 "Shut up and listen. The email traffic is explained using a Joomla 5.1 instance with the use cases of password reset and System Tests."

A user (not in the Super User group) requests a password reset by clicking 'Forgot your Password?' in their web browser. This request is sent to the Joomla PHP code on the web server jbt-51.
An email is sent via SMTP from the web server jbt-51 to the email relay jbt-relay. In the Joomla configuration.php file, the smtpport is configured as 7025.
The email relay jbt-relay triplicates the email and sends the first email via SMTP to the email catcher jbt-mail.
The email relay jbt-relay tries to deliver the second email to smtp-tester. But no System Tests is running, the email cannot be delivered and is thrown away.
The email relay jbt-relay tries to deliver the third email to locally running Cypress GUI with smtp-tester. But no Cypress GUI is running, the email cannot be delivered and is thrown away.
System Test is started with scripts/test in the Cypress container jbt-cypress. In the Cypress cypress.config.mjs file, the smtp_port is configured as 7125. While the System Tests is running smtp-tester is listening on port 7125.
One of the System Tests specs executes an action in Joomla PHP code that generates an email.
Again the email is sent via SMTP from the web server jbt-51 to the email relay jbt-relay.
Again the email relay jbt-relay triplicates the email and sends the one email via SMTP to the jbt-cypress container with smtp-tester running in . The Cypress test can check and validate the email.
Again the email relay jbt-relay sents one copy via SMTP to the email catcher jbt-mail.
Again the email relay jbt-relay tries to deliver the third email to locally running Cypress GUI with smtp-tester. But no Cypress GUI is running, the email cannot be delivered and is thrown away.

Therefore, the cypress.config.mjs file uses a different SMTP port (7125) than the configuration.php file (7025). Additionally, the cypress.config.local.mjs file is used with yet another SMTP port (7325) for running the Cypress GUI locally.

Databases

The Joomla Branches Tester includes one container for each of the three supported databases (version numbers as of the beginning of November 2024):

jbt-mysql – MySQL version 8.1.0 Community Server
jbt-madb – MariaDB version 10.4.34
jbt-pg – PostgreSQL version 15.8

You can set the desired database and database driver using scripts/create or switch them later with scripts/database.

Switch Database and Database Driver

You can simply switch between one of the three supported databases (MariaDB, PostgreSQL or MySQL) and the database driver used (MySQL improved or PHP Data Objects). Firstly, the settings for the database server with db_host and the database driver with db_type are adjusted in the configuration file Cypress.config.cy.mjs. Secondly, a Joomla installation is performed with the Joomla System Tests.

Five variants are available:

mariadbi – MariaDB with MySQLi (improved)
mariadb – MariaDB with MySQL PDO (PHP Data Objects)
pgsql - PostgreSQL PDO (PHP Data Objects)
mysqli – MySQL with MySQLi (improved)
mysql – MySQL with MySQL PDO (PHP Data Objects)

Use MariaDB with driver MySQLi for Joomla 5.1 and Joomla 5.2:

scripts/database 51 52 mariadbi

Change all Joomla instances to use PostgreSQL:

scripts/database pgsql

⚠️ The overall database content is lost. If you have installed the Joomla Patch Tester, you need to reinstall it now. For more details, see Database and File System Consistency.

🧚 The good fairy waves her magic wand and says: "When in doubt, it's wiser to use scripts/create to ensure a clean installation. With a sprinkle of stardust, you can specify the desired database variant, and if you're only installing one Joomla version, it will be done in the blink of an eye."

Database Unix Sockets

Database Unix sockets are available in the Cypress and Joomla Web Server containers:

/jbt/run/postgresql-socket
/jbt/run/mysql-socket/mysqld.sock
/jbt/run/mysql-socket/mysqlx.sock
/jbt/run/mariadb-socket/mysqld.sock

They are used in scripts/create and scripts/database with the socket option. Without this option, the database connection defaults to using the TCP host.

scripts/database mysqli socket

Without using the Unix sockets for Joomla, you can still take advantage of them with command-line client tools. For example:

docker exec -it jbt-pg bash -c "psql -h /var/run/postgresql -U root -d test_joomla_44"
docker exec -it jbt-madb bash -c "mariadb --socket=/var/run/mysqld/mysqld.sock -u root -proot"
docker exec -it jbt-mysql bash -c "mysql --socket=/var/run/mysqld/mysqld.sock -u root -proot"

Switch PHP Version

The Joomla Docker images are available in various PHP versions, from PHP 7.4 to PHP 8.3. To check which PHP versions are available, use scripts/versions first.

You can switch the PHP version for all installed Joomla instances:

scripts/php php8.3

Or specify the desired Joomla instances:

scripts/php 44 51 php8.1

👉 There are no Docker images for Joomla 5.3 and Joomla 6.0 available (as of early November 2024). Instead, the Joomla 5.2 image is being used. This should not cause any issues, as the source code for 5.3 and 6.0 is pulled from the respective GitHub branches and installed over the existing version.

Grafting a Joomla Package

Do you have a bundled Joomla package to test? No problem! Just like in plant grafting, where a scion is joined to a rootstock, you can graft a Joomla package onto the Joomla instance for testing. Simply choose the same major and minor version numbers and graft the package for a seamless experience:

scripts/graft 52 ~/Downloads/Joomla_5.2.0-alpha4-dev-Development-Full_Package.zip

Mandatory arguments are the Joomla instance version and the local package file. Supported file formats are .zip, .tar, .tar.zst, .tar.gz and .tar.bz2. An optional argument is the database variant, such as PostgreSQL in the following example:

scripts/graft 51 pgsql ~/Downloads/Joomla_5.1.3-Stable-Full_Package.zip

⚠️ The overall database content is lost. If you have installed the Joomla Patch Tester, you need to reinstall it now. For more details, see Database and File System Consistency.

After grafting, you can still switch the database variant, change the PHP version, install the Joomla Patch Tester, or run Joomla System Tests. There is no Git repository, so you cannot run the other tests and scripts/pull will be skipped. Grafting can also be done multiple times. 😄

What distinguishes a JBT grafted Joomla from a standard package-installed Joomla? A JBT grafted Joomla contains additional files and two directories from the development branch:

Files: cypress.config.* and package*.json
Directories: node_modules and tests/System

Syncing from GitHub Repository

To avoid recreating Joomla dev-branch instances the next day, you can simply fetch and merge the latest changes from the Joomla GitHub repository into your local dev-branch based instances. This can be done for all installed Joomla instances without any arguments or for specific versions:

scripts/pull 53 60

If changes are pulled then:

Just in case the command composer install is executed.
If package-lock.json file has changed the command npm ci is executed.

Finally, the Git status is displayed.

👉 This works only for dev-branch based Joomla instances. If the instance was installed from a tag or is a grafted one, then scripts/pull skips over the instance.

🧚 Gaze Into the Spellbook

In the mystical world of Joomla, the database is the enchanted tome where all the secrets are stored. Sometimes, the wise must delve into this spellbook to uncover and weave new spells, adjusting rows and columns with precision.

Fear not, for magical tools are at your disposal, each one a trusted companion. They are so finely attuned to your needs that they require no login, no password — just a single click, and the pages of the database open before you as if by magic:

http://host.docker.internal:7002 phpMyAdmin – for MariaDB and MySQL
http://host.docker.internal:7003 pgAdmin – for PostgreSQL

Simply approach these gateways and the secrets of the database will reveal themselves effortlessly, ready for your exploration.

Xdebug

Joomla web server containers are ready with a second PHP installation for switching to Xdebug. You can switch to the PHP version with Xdebug for example:

scripts/xdebug 53 on

A .vscode/launch.json file is also prepared for all enabled instances. In Visual Studio Code, select 'Start Debugging' and choose the corresponding entry Listen jbt-53.

Finally, it may be reset again to improve performance:

scripts/xdebug off

Enabling Xdebug requires at least PHP 8.0. Used ports are 79xx, for the given example 7953 and for Joomla version 3.10 using port 7910.

IPv6

As shown in the Installation chapter, you can create the Docker Branches Tester instance using scripts/create with the IPv6 option instead of the default IPv4 network. IP addresses are fixed from the predefined private, non-routable subnet fd00::/8.

You can use the IPv6 address (instead of the hostname) to open the PostgreSQL interactive terminal:

docker exec -it jbt-pg bash -c "PGPASSWORD=root psql -h fd00::13 -U root -d postgres"

👉 IPv6 networking is limited to within Docker. The host.docker.internal feature generally defaults to IPv4, and there is no built-in IPv6 equivalent. As scripts/cypress local works with host.docker.internal, the database custom commands executed by a local running Cypress GUI use the IPv4 address to access the database.

Install Joomla Patch Tester

For your convenience, the latest version of the Joomla Patch Tester can be installed on the Joomla instances from version 4.2 onwards. The script also sets the GitHub token and fetches the data. This can be done without version number for all Joomla instances or for e.g. Joomla 5.3:

scripts/patchtester 53 ghp_4711n8uCZtp17nbNrEWsTrFfQgYAU18N542

  Running:  patchtester.cy.js                             (1 of 1)
    Install 'Joomla! Patch Tester' with
    ✓ install component (7747ms)
    ✓ set GitHub token (2556ms)
    ✓ fetch data (6254ms)

👉 The GitHub token can also be given by environment variable JBT_GITHUB_TOKEN. And of course the sample token does not work.

🧚 "You need to reinstall the Joomla Patch Tester if, for example you switch the database. For more details, see Database and File System Consistency."

👉 Alternatively, to apply patches, you can use scripts/patch, see Back to the Future - Patch.

Back to the Future - Patch

As Doc Brown said: "Roads? Where we're going, we don't need roads."

JBT can install patches using Git merge from pull requests (PRs) with scripts/patch (or even with scripts/create), applicable to the following repositories:

joomla-cms - joomla/joomla-cms
joomla-cypress - joomla-projects/joomla-cypress
database - joomla-framework/database

This can be done for all installed Joomla instances without any arguments, or for specific versions:

# Apply non-standard database port for Joomla 4.4 and 5.2 instances
scripts/patch 44 52 joomla-cypress-33 joomla-cms-43968

# Allow to specify port number or UNIX socket in Joomla 5.3 instance
scripts/patch 53 database-310

⚠️ Be cautious when applying patches, as we perform a full merge, which could introduce additional changes beyond the original pull request. Always pay attention to the number of changed lines. If you encounter merge conflicts, you will need to resolve them or recreate the instance.

While there's no way to remove a patch, you can use the scripts/create recreate to go back in time and restore the instance to the original state.

👉 Alternatively, to apply joomla-cms patches, you can use Joomla Patch Tester.

DeLorean

You can take a seat and pick up additional code from the future on your own. As of early November 2024, several pull requests (PRs) in the Joomla ecosystem remain unmerged, unreleased, or absent from specific branches. Testing certain PRs may necessitate the prior integration of others. For instance, database-317 required the merging of database-310 as well as joomla-cypress-33 and joomla-cypress-36 to facilitate comprehensive testing.

🔧 joomla-cypress-33 Install Joomla with non-standard db_port
- Working for 4.4-dev, 5.1-dev (and updates joomla-cypress from 1.0.3 to 1.1.1 - which is a good idea anyway), 5.2-dev, 5.3-dev and 6.0-dev
🔧 joomla-cypress-35 Install Joomla for Stable Releases
- Working for 4.4-dev, 5.1-dev (and updates joomla-cypress from 1.0.3 to 1.1.1 - which is a good idea anyway), 5.2-dev, 5.3-dev and 6.0-dev
🔧 joomla-cypress-36 Wrap IPv6 address in brackets [ ] if needed
- Working for 4.4-dev, 5.1-dev (and updates joomla-cypress from 1.0.3 to 1.1.1 - which is a good idea anyway), 5.2-dev, 5.3-dev and 6.0-dev
🔧 database-310 [3.x] Allow to specify port number or UNIX socket in host option also for MySQL (PDO) and PostgreSQL (PDO)
- Working for 5.1-dev, 5.2-dev, 5.3-dev and 6.0-dev
🔧 database-317 [3.x] Remove square brackets from ipv6 host on PostgreSQL, refactor changes from PR 310 and move options modifications to constructor
- Working for 5.1-dev, 5.2-dev, 5.3-dev and 6.0-dev

👉 All these patches are for the web server Docker containers running the Joomla instances. JBT uses its own Cypress installation environment with the latest joomla-cypress main branch clone.

Versions

Running scripts/versions without any arguments will display all available branches and tags with Joomla versions. These can be used as arguments for the scripts/create command:

scripts/versions

5 Usable Branches from the 'joomla-cms' Repository
    4.4-dev       5.1-dev       5.2-dev       5.3-dev       6.0-dev

292 Usable Tags from the 'joomla-cms' Repository
    3.9.0         3.9.0-alpha   3.9.0-beta    3.9.0-beta2   3.9.0-beta3   3.9.0-beta4   3.9.0-rc      3.9.0-rc2
    ...
    5.2.0         5.2.0-alpha1  5.2.0-alpha2  5.2.0-alpha3  5.2.0-beta1   5.2.0-beta2   5.2.0-beta3   5.2.0-rc1
    5.2.0-rc2     5.2.0-rc3     5.2.0-rc4     5.2.1

To see which Joomla Docker images are available for a specific version – and therefore which PHP versions you can use – run the script with the desired Joomla version:

scripts/versions 5.2.1

  5.2-php8.1-apache
  5.2-php8.2-apache
  5.2-php8.3-apache

Usable Joomla development branches refer to the GitHub joomla-cms repository, including default, active and stale branches in the format number.number-dev. See joomla-cms/branches for details.

Info

You can retrieve some interesting Joomla Branches Tester status information. If no argument is provided, all information will be displayed:

scripts/info

The following example illustrates an IPv6 installation with three Joomla instances:

jbt-310 – Cloned from Joomla 3.10.12 tag and PHP 8.0 running with Xdebug
jbt-51 – Grafted from Joomla 5.1.3 Stable Joomla package, running PHP 8.1 and using MariaDB with driver MySQLi
jbt-53 – Cloned from 5.3-dev branch of version 5.2.0 with additional patches applied, running PHP 8.3scripts/info and using PostgreSQL

Joomla Branches Tester (JBT) version 2.0.19
  Docker version 27.2.0 is running with 12 containers and 14 images
  EnableIPv6: true
Base Containers:
  jbt-mysql   is running, ports: 3306/tcp -> 0.0.0.0:7011; 3306/tcp -> [::]:7011
  jbt-madb    is running, ports: 3306/tcp -> 0.0.0.0:7012; 3306/tcp -> [::]:7012
  jbt-pg      is running, ports: 5432/tcp -> 0.0.0.0:7013; 5432/tcp -> [::]:7013
  jbt-mya     is running, ports: 80/tcp -> 0.0.0.0:7002; 80/tcp -> [::]:7002
  jbt-pga     is running, ports: 80/tcp -> 0.0.0.0:7003; 80/tcp -> [::]:7003
  jbt-cypress is running, ports: 7125/tcp -> 0.0.0.0:7125; 7125/tcp -> [::]:7125
  jbt-novnc   is running, ports: 8080/tcp -> 0.0.0.0:7005; 8080/tcp -> [::]:7005
  jbt-relay   is running, ports: 7025/tcp -> 0.0.0.0:7025; 7025/tcp -> [::]:7025
  jbt-mail    is running, ports: 1025/tcp -> 0.0.0.0:7225; 1025/tcp -> [::]:7225; 1080/tcp -> 0.0.0.0:7004; 1080/tcp -> [::]:7004
jbt-310 Tag 3.10.12
  Container jbt-310 is running, ports: 80/tcp -> 0.0.0.0:7310
  Joomla Version: Joomla! 3.10.12 Stable
  PHP 8.0.30 with Xdebug
  Without Cypress configuration file
  /joomla-310: 86MB
  Git Repository joomla-310/
    Remote Origin: https://github.com/joomla/joomla-cms
    Tag: 3.10.12
    Status: 277 changes
jbt-51 Branch development
  Container jbt-51 is running, ports: 80/tcp -> 0.0.0.0:7051
  Joomla Version: Joomla! 5.1.0 Stable
  PHP 8.1.29
  MySQLi, jbt-madb, 
  /joomla-51: 393MB
jbt-53 Branch 5.3-dev
  Container jbt-53 is running, ports: 80/tcp -> 0.0.0.0:7053
  Joomla Version: Joomla! 5.3.0 Development
  PHP 8.3.11
  PostgreSQL(PDO), jbt-pg, 
  /joomla-53: 525MB
  Git Repository joomla-53/libraries/vendor/joomla/database/
    Remote Origin: https://github.com/joomla-framework/database
    Branch: jbt-merged database-317
    Status: 0 changes
  Git Repository joomla-53/
    Remote Origin: https://github.com/joomla/joomla-cms
    Branch: 5.3-dev
    Status: 0 changes

Optional arguments that can be combined as desired are:

instance to display Joomla Branches Tester instance information,
base to display information about all base containers,
version number to display information about this version number web server container.

For example, to check only JBT instance and jbt-44 container information:

scripts/info instance 44

Check & Logging

Most scripts automatically duplicate their output to a log file in the logs folder. The scripts/check command supports searching JBT log files for critical issues or specific information. You can run scripts/check without any arguments to check the latest log file, or specify a log file name to review a particular log.

Optional Arguments:

scripts: Show only the start and end lines of scripts.
jbt: Show only JBT-specific log messages.

If no argument is provided, the log file will be checked for errors and critical messages by default.

Example to see last file JBT log messages only:

scripts/check jbt

Sometimes everything appears to be working fine, but errors may still occur. For example, Joomla JavaScript exceptions might be caught during installation. As there are numerous log messages, you might overlook them. However, you can run scripts/check after running scripts/create, scripts/database, scripts/patchtester or scripts/graft and you will see the error. You can then investigate the JavaScript exception in the log file. For example:

[6927:1114/174511.623420:INFO:CONSOLE(1230)] "ERROR uncaught:exception err :TypeError: The following error originated from your application code, not from Cypress.
  > Cannot read properties of null (reading 'getAttribute')

Cleaning Up

If you want to be rid of all Docker containers and free up multiple gigabytes of disk space from the joomla-* and other directories, simply run:

scripts/clean

Database and File System Consistency

When installing extensions, it's important to be aware of database and file system consistency. The following operations will break that consistency, as the Joomla database will be recreated:

scripts/database
scripts/create and scripts/create recreate
scripts/test system install/Installation.cy.js

While grafting a Joomla package with scripts/graft doesn't break database consistency, you will lose all additionally installed extensions as the files are installed from package.

Switching between PHP versions using scripts/php or enabling/disabling Xdebug with scripts/xdebug does not affect consistency. The Joomla files and the database remain unchanged.

If you've used scripts/patchtester to install the Joomla Patch Tester, remember that it’s a Joomla extension. To protect you, scripts/database (which is also used by scripts/create) will clear the autoload classes cache file and remove all com_patchtester directories to prevent issues during the next installation. After that, you'll need to reinstall the Joomla Patch Tester using scripts/patchtester.

🧚 "To protect you, the first step Installation.cy.js of the Cypress based Joomla System Tests is excluded if you run all system test specs."

Trouble-Shooting

To fully grasp the process, it's helpful to both see the diagrams and read the explanations provided.
Simply try running it a second time. All scripts are designed to be run multiple times without issues.
On scripts/create, if you see the log message Base installation is completed, you can use the recreate option if one Joomla instance fails during installation.
One advantage of Docker and scripting: you can easily start fresh. As Roy from The IT Crowd says, "Have you tried turning it off and on again?" It takes just 2.5 minutes on a 2024 entry-level MacBook Air to delete everything and create the 10 containers with Joomla 5.2-dev branch and PostgreSQL.
```
scripts/create 52 pgsql
```

Check the Docker container logs to monitor activity. For example, the jbt-relay container logs will display information about receiving and delivering emails.

docker logs jbt-relay

2024-08-22 10:09:34,082 - INFO - SMTP relay running on port 7025 and forwarding emails...
2024-08-22 10:21:45,082 - INFO - ('192.168.65.1', 31625) >> b'MAIL FROM:<[email protected]>'
2024-08-22 10:21:45,083 - INFO - ('192.168.65.1', 31625) >> b'RCPT TO:<[email protected]>'
2024-08-22 10:21:45,219 - INFO - Email forwarded to host.docker.internal:7125
2024-08-22 10:21:45,345 - INFO - Email forwarded to host.docker.internal:7225
2024-08-22 10:21:45,346 - ERROR - Failed to forward email to host.docker.internal:7325: [Errno 111] Connection refused

An email is received by jbt-relay:7025 and delivered to the Cypress container smtp-tester listening on jbt-cypress:7125, delivered to the mail catcher listening on jbt-mail:7225, and could not be delivered to the locally running Cypress GUI smtp-tester listening on localhost:7325 (equivalent host names are used for clarity).

Run a script with the option -x to enable detailed debugging output that shows each command executed along with its arguments. You have to use the .sh variant, for example:
```
bash -x scripts/pull.sh 53
```
It is generally recommended to use the latest patch level of a Joomla version and the highest compatible PHP version possible.
Always use the latest version of Docker software. And I mean it – do it, I’m not joking here!
And always keep JBT up to date. You’ll get a reminder when you run scripts/info, and you should run git pull to stay current.
If you need to cancel a running script, send an interrupt by pressing <Ctrl> + <C> together. You may need to press the keys multiple times to fully stop the process.

Automated Cypress System Test runs may persist even after the scripts/test process is terminated. If you attempt to run another Cypress System Tests, you might encounter the: Error: listen EADDRINUSE: address already in use :::7125. To stop the still-running Cypress System Tests, use the command: docker restart jbt-cypress.
Open an issue.

Limitations

The different Joomla versions exist in parallel, but the test runs sequentially, as there is the one Cypress container used.
Database server versions cannot be changed.
The setup does not support HTTPS, secure connections issues are not testable. → #7
If IPv6 networking is chosen, it is used only within Docker.
The predefined port range run from 7000 to 7900. If another service is already using this range, it may cause a conflict. → #3
Usable Joomla Git tags start with 3.9.0 (for earlier versions apt-get update does not work so easily).
For each Joomla major and minor version (e.g., 5.2, 5.3), only one Docker container is possible. This means you can run containers for versions such as 52 (for Joomla 5.2.) and 53 (for Joomla 5.3.), but you cannot have multiple containers for different patch versions like 5.2.0 and 5.2.1 running in parallel.
Tests phan and integrationare not implemented yet. → #4

More Information

Join the discussion on Mattermost: joomla-branches-tester
Watch the presentation on the architecture and live demo (in German) from JoomlaDay DACH, September 2024: Video Ticket

License

Distributed under the GNU General Public License version 2 or later, see LICENSE

If it is used, I would like to pass it on to the Joomla! project.

Contact

Don't hesitate to ask if you have any questions or comments. If you encounter any problems or have suggestions for enhancements, please feel free to open an issue.

Name		Name	Last commit message	Last commit date
Latest commit History 383 Commits
configs		configs
hooks		hooks
images		images
installation		installation
scripts		scripts
.gitignore		.gitignore
LICENSE		LICENSE
README.md		README.md
RELEASE_CHECKLIST.md		RELEASE_CHECKLIST.md
VERSION		VERSION
dockerfile-relay.yml		dockerfile-relay.yml

License

muhme/joomla-branches-tester

Folders and files

Latest commit

History

Repository files navigation

JBT – Joomla Branches Tester

Software Architecture

JBT Parallel Installation Environment

Version Naming

Prerequisites

Installation

Usage

Joomla Configuration

Manual Testing

Drone-like Tests

Cypress Automated System Tests

Cypress Interactive System Tests

Check Email

Databases

Switch Database and Database Driver

Database Unix Sockets

Switch PHP Version

Grafting a Joomla Package

Syncing from GitHub Repository

🧚 Gaze Into the Spellbook

Xdebug

IPv6

Install Joomla Patch Tester

Back to the Future - Patch

DeLorean

Versions

Info

Check & Logging

Cleaning Up

Database and File System Consistency

Trouble-Shooting

Limitations

More Information

License

Contact

About

Topics

Resources

License

Stars

Watchers

Forks

Releases 3

Contributors 2

Languages