Difference between revisions of "Running Automated Tests for the Joomla CMS"

From Joomla! Documentation

m (clean up formatting)
(84 intermediate revisions by 15 users not shown)
Line 1: Line 1:
 +
{{RightTOC}}
 
== Introduction ==
 
== Introduction ==
−
As of February 2010, a tests folder has been added to the Joomla! SVN download. This folder contains a growing library of unit and functional tests. The unit tests use PHPUnit and the functional tests use PHPUnit and Selenium. The unit tests perform tests primarily on the Joomla! framework. The Selenium functional tests actually run Joomla! from a browser and test it as a user would.
+
'''This article has been updated during the Testing Sprint in October 2014 to reflect the latest information for running unit and system tests for Joomla version 3.x'''
  
−
Before you can run the tests, you need to install some programs on your local workstation, as documented below. This document explains how to run the functional tests from your local workstation.
+
When you checkout the staging branch of Joomla from Github.com (https://github.com/joomla/joomla-cms) you will see a folder called "tests". This folder contains unit and two types of system tests for the CMS. The unit tests use PHPUnit and the system tests use PHPUnit and Selenium. The unit tests perform tests on the framework and cms library files (libraries/cms and libraries/joomla) and on parts of com_finder. The Webdriver system tests run Joomla! from a browser and test it as a user would.
 +
 
 +
Before you can run the tests, you need to install some programs on your local workstation, as documented below. This document explains how to run those tests from your local workstation.
 +
 
 +
== PHP Requirements ==
 +
You may need to modify your PHP configuration. This is done by editing your <code>php.ini</code> file and then restarting your Apache service.
 +
 
 +
=== CMS Unit Tests ===
 +
Some of the CMS unit tests rely on the PHP extension Sqlite3. To run these tests, make sure that the following line in your php.ini file is uncommented:
 +
* For Windows: <code>extension=php_sqlite3.dll</code>
 +
* For Linux: <code>extension=php_sqlite3.so</code>
 +
 
 +
On top of that, it might be necessary to increase your PHP memory limit, as some tests are consuming a lot of resources:
 +
memory_limit=512M
 +
 
 +
=== Webdriver System Tests ===
 +
The Webdriver system tests require that the Curl extension is installed. Make sure the following line in your php.ini file is uncommented:
 +
* For Windows: <code>extension=php_curl.dll</code>
 +
* For Linux: <code>extension=php_curl.so</code>
  
 
== Install PHPUnit ==
 
== Install PHPUnit ==
−
Both the unit and functional tests rely on PHPUnit. On most PHP installations, this can be installed using the standard PEAR installation process.
+
Both the unit and system tests rely on PHPUnit. PHPUnit is a testing framework that requires PHP to be installed on the local workstation. Please visit [http://phpunit.de/getting-started.html http://phpunit.de/] and follow the instructions to install the PHPUnit PHAR Archive.
 +
 
 +
=== Windows Users ===
 +
The instructions at http://phpunit.de/ may not work on Windows. Most likely, Windows users will not have the `wget` command used in the instructions. However, if msysgit is installed, curl should be available. If it is, then the simplest way to install PHPUnit on Windows is to just use this command:
 +
 
 +
    curl https://phar.phpunit.de/phpunit.phar > _some_directory_in_your_path_/phpunit
 +
 
 +
This will download the phar file and store it without the phar extension so that you can run the command simply by running:
 +
 +
    phpunit
 +
 
 +
== Running Unit Tests ==
 +
===Run Suite from XML File===
 +
Once PHPUnit is installed, it's easy to run the unit tests. The command that runs the tests is called <code>phpunit</code>. This file is found in your PHP folder. For example, in Windows with Xampp, it would be <code>c:/xampp/php/phpunit</code>. In Linux, with Xampp, it might be <code>/opt/lampp/bin/phpunit</code>. If you add this to your operating system path, you can execute it from any folder without using the full path name.
 +
 
 +
When you run <code>phpunit</code> it looks for a PHPUnit configuration XML file (either <code>phpunit.xml</code> or <code>phpunit.xml.dist</code>). The CMS unit tests are run from the Joomla root folder, where you will find the <code>phpunit.xml.dist</code> file. This file is included in the Git repository and can be used as is or customized (by making a copy called <code>phpunit.xml</code>).
 +
 
 +
To run all of the unit tests from the command line:
 +
# Change Joomla root folder
 +
# Execute the command <code>phpunit</code>.
 +
 
 +
The following example runs the entire unit test suite on OS X.
 +
 
 +
MyMacbook:joomla-cms sniper$ phpunit
 +
PHPUnit 4.3.2 by Sebastian Bergmann.
 +
 +
Configuration read from /Users/myself/joomla-cms/phpunit.xml
 +
 +
.....S.......................................................  61 / 5373 (  1%)
 +
............................................................. 2745 / 5373 ( 51%)
 +
SSSSSSSSSSSSSSSSSSSSSSSS..................................... 5368 / 5373 ( 99%)
 +
.....
 +
 +
Time: 57.29 seconds, Memory: 186.75Mb
 +
 +
OK, but incomplete, skipped, or risky tests!
 +
Tests: 5373, Assertions: 9914, Skipped: 157.
 +
 +
Generating code coverage report in Clover XML format ... done
 +
 +
Generating code coverage report in HTML format ... done
 +
 
 +
The dots indicate a successful test. If you have errors or failures, they will show as "E" or "F" letters and a detailed message for each will show. If you are generating code coverage or other logs, you can see the folders where these are generated in the XML file. In the default file, all of the logs are generated in <code>build/logs</code>, with coverage information in a folder called <code>build/coverage</code>.
 +
 
 +
You can create your own phpunit.xml file by copying the phpunit.xml.dist file and making the desired changes. For example, if you don't want to create the coverage information, remove the <code>log type="coverage-html"</code> element.
 +
 
 +
===Run Selected Unit Tests===
 +
====Running A Selected Suite====
 +
Joomla's unit tests are grouped into a number of different suites:
 +
* libraries-cms
 +
* libraries-platform
 +
* libraries-legacy
 +
* database
 +
* administrator
 +
* FinderIndexer
 +
 
 +
You can run unit tests grouped in a specific folder by appending the --testsuite parameter. The following example runs all of the tests in the database suite:
 +
 
 +
MyMacbook:joomla-cms sniper$ phpunit --testsuite database
 +
PHPUnit 4.3.2 by Sebastian Bergmann.
 +
 +
Configuration read from /Users/myself/joomla-cms/phpunit.xml
 +
 +
...............................................................  63 / 354 ( 17%)
 +
............................................................... 126 / 354 ( 35%)
 +
..............................SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS 189 / 354 ( 53%)
 +
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS................................ 252 / 354 ( 71%)
 +
..................SSSSSS....................................... 315 / 354 ( 88%)
 +
...........SSSSSSSSSSSSSSSSSSSSSSSSS...
 +
 +
Time: 2.51 seconds, Memory: 20.00Mb
 +
 +
OK, but incomplete, skipped, or risky tests!
 +
Tests: 354, Assertions: 718, Skipped: 95.
 +
 +
 
 +
====Running Tests In A Specific Folder====
 +
You can run unit tests one at a time or by folder. The following example runs all of the tests in the <code>libraries/feed</code> folder:
 +
 
 +
MyMacbook:joomla-cms sniper$ phpunit tests/unit/suites/libraries/joomla/feed
 +
PHPUnit 4.3.2 by Sebastian Bergmann.
 +
 +
Configuration read from /Users/myself/joomla-cms/phpunit.xml
 +
 +
................S.S............................................  63 / 101 ( 62%)
 +
......................................
 +
 +
Time: 335 ms, Memory: 8.50Mb
 +
 +
OK, but incomplete, skipped, or risky tests!
 +
Tests: 101, Assertions: 201, Skipped: 2.
 +
 
 +
You can also specify a single test simply by specifying it's full path name in the command.
 +
 
 +
 
 +
====Running Tests Filtered By Name====
 +
You can run all unit tests which names are matching a specific naming pattern by appending the --filter parameter. The following example runs all tests starting with JModel like:
 +
* JModelBaseTest
 +
* JModelDatabaseTest
 +
* JModelLegacyTest
 +
* ...
 +
 
 +
MyMacbook:joomla-cms sniper$ phpunit --filter JModel
 +
PHPUnit 4.3.2 by Sebastian Bergmann.
 +
 +
Configuration read from /Users/myself/joomla-cms/phpunit.xml
 +
 +
................................................................. 65 / 95 ( 68%)
 +
..............................
 +
 +
Time: 4.58 seconds, Memory: 95.00Mb
 +
 +
OK (95 tests, 140 assertions)
 +
 
 +
Running a single test
 +
* JModelLegacyTest::testConstructorSetsCorrectStateObject
  
−
For example, on XAMPP version 1.7.3 on Windows, you would do the following commands:
+
===Running the Database Testsuites===
 +
By default, only the tests for Sqlite are run in the database testsuite, because all other tests for database systems like MySQL, PostgreSQL and MSSQL require a working database, valid credentials and some preparations. This example documents the necessary steps to get the MySQL tests running:
  
−
* <code>cd c:\xampp\php</code>
+
# create a new, empty database
−
* <code>install phpunit/PHPUnit</code>
+
# create a user that is allowed to access the created database
 +
# import the default dataset, dumped in tests/unit/schema/mysql.sql, into the database
 +
# copy the file <code>phpunit.xml.dist</code> to <code>phpunit.xml</code>
 +
# uncomment and update the database dsn constants in the <php> block of your new phpunit.xml:
  
−
More detailed instructions can be found here: [http://www.phpunit.de/manual/3.0/en/installation.html http://www.phpunit.de/manual/3.0/en/installation.html].
+
<?xml version="1.0" encoding="UTF-8"?>
 +
<phpunit bootstrap="tests/unit/bootstrap.php" colors="false">
 +
    <php>
 +
        <const name="JTEST_DATABASE_MYSQL_DSN" value="host=YOURHOST;dbname=YOURDBNAME;user=YOURUSER;pass=YOURPASSWORD" />
 +
        <const name="JTEST_DATABASE_MYSQLI_DSN" value="host=YOURHOST;dbname=YOURDBNAME;user=YOURUSER;pass=YOURPASSWORD" />
 +
        <!-- These constants help setup environment configurations for running optional tests.
 +
        <const name="JTEST_DATABASE_POSTGRESQL_DSN" value="host=localhost;port=5432;dbname=joomla_ut;user=utuser;pass=ut1234" />
 +
        <const name="JTEST_DATABASE_SQLSRV_DSN" value="host=localhost;dbname=joomla_ut;user=utuser;pass=ut1234" />
 +
        -->
 +
    </php>
 +
...
  
−
== Install Selenium RC ==
+
== Selenium RC System Tests ==
−
Selenium RC is the package that allows you to run Selenium tests from PHP or other programming languages. To install it, just go to the Selenium site [http://seleniumhq.org/projects/remote-control http://seleniumhq.org/projects/remote-control] and download the package. Then unzip the file into a folder.  
+
The older Selenium RC system tests are in the folder tests/system/suite. Before you can run the system tests, you need to install and download the Selenium Server program and configure your test environment, as shown below.
  
−
For example, in Windows if you create a folder called <code>C:\selenium</code> and unzip this file there, it will create a folder called selenium-server-1.0.1. In that folder, create a Windows bat file or Linux shell script that runs the following command:
+
=== Download Selenium Server ===
 +
Selenium Server (formerly Selenium RC) is the package that allows us to run Selenium tests from PHP (instead of Java). To download it, just go to the Selenium site [http://seleniumhq.org/download/ http://seleniumhq.org/download/] and download the Selenium Server file (for example, selenium-server-standalone-2.25.0.jar) to a folder.
  
−
<code>java -jar selenium-server.jar -browserSessionReuse</code>
+
For example, in Windows you can create a folder called <code>C:\selenium</code> and copy this file there. In that folder, create a Windows bat file (such as selenium.bat though the name does not matter) or Linux shell script that runs the following command:
 +
 
 +
<code>java -Xms40m -Xmx256m -jar selenium-server-2.25.0.jar</code>  
 +
 
 +
(Obviously you will need to use the exact name of the .jar file for the version you downloaded.) The -Xms and -Xmx arguments run the server program allocating more memory to Java than the default. That seems to help prevent intermittent errors when running a long suite of system tests.
  
 
If the Java executable is not on your path, then you will need to indicate the full path to it, like the following:
 
If the Java executable is not on your path, then you will need to indicate the full path to it, like the following:
  
−
<code>c:\program files (x86)\Java\jre6\bin\java.exe" -jar selenium-server.jar -browserSessionReuse</code>  
+
<code>"c:\program files (x86)\Java\jre6\bin\java.exe" -Xms40m -Xmx256m -jar selenium-server-2.25.0.jar</code>  
  
−
Note the argument <code>browserSessionReuse</code> is used to allow you to run multiple tests without closing and re-opening the browser each time. Save this file so you can easily find and execute it when needed.
+
This program needs to be running in the background before you can run any Selenium functional tests. So just run this program from a Bat file and it will continue to run in the background in a console window until you close it (for example, with Ctrl+C).
  
−
This program needs to be running in the background before you can run any Selenium functional tests.
+
=== Create a Selenium Configuration File ===
 +
To run the Selenium tests, we have to tell Selenium how to navigate and login to our local Joomla! installation. This is done by creating a PHP file called <code>tests/system/servers/configdef.php</code>. The Joomla! download includes a file called <code>tests/system/servers/config-def.php-dist</code>. This is a sample file that you can use to create the real file. Copy this file to a file called <code>tests/system/servers/configdef.php</code> and edit it to reflect your test systems configuration. There are comments in the file that tell you how to do this.
  
−
== Create a Selenium Configuration File ==
+
=== Run the System Test Suite ===
−
To run the Selenium tests, we have to tell Selenium how to navigate and login to your local Joomla! installation. This is done by creating a PHP file called <code>configdef.php</code>. The Joomla! download includes a file called <code>tests/system/servers/config-def.php-dist</code>. This is a sample file that you can use to create the real file. Copy this file to a file called <code>tests/system/servers/configdef.php</code> and edit it to reflect your test systems configuration. There are comments in the file that tell you how to do this.
+
At this point, we are ready to actually run the tests. There are two steps to running a test. First, you need to make sure the Selenium Server process is running in the background. To do this, just execute the command (bat file or shell script) you created when you installed Selenium. This will continue to run (in a console window) until you cancel it. You do not need to stop and start this for each test. Just run it once and let it run in the background.
  
−
== Run the Test Suite ==
+
Once Selenium is running, you need to execute the system tests. These are executed the same way we did the unit tests, except for our starting directory.
−
At this point, we are ready to actually run the tests. There are two steps to running a test. First, you need to make sure the Selenium RC process is running in the background. To do this, just execute the command (bat file or shell script) you created when you installed Selenium RC. This will continue to run until you cancel it.
 
  
−
Once Selenium RC is running, you need to execute the functional tests. There are several ways you can do this.
+
To run all tests from the command line in Windows, change to the <code>tests/system</code> folder and run the following command
  
−
To run all tests from the command line, change to the <code>tests/system</code> folder and run the following command:
+
<code>phpunit</code>
  
−
<code>phpunit.bat --bootstrap servers\configdef.php suite\TestSuite.php </code>
+
By default, this will use the <code>tests/system/phpunit.xml.dist</code> file that is included with the Joomla checkout. This will run all of the tests listed in the phpunit.xml.dist file. You should see two browser windows open. One will display Selenium commands that are being executed. The other will show the Joomla! website and the various screens that are being opened and closed as the tests are run. As each test is completed, you will see comments in the console window describing each step in the test.
  
−
This will run all of the tests in the TestSuite.php file. You should see a series of messages display in the console telling you what tests are being run and what the tests are doing. You should also see two browser windows open. One will display Selenium commands that are being executed. The other will show the Joomla! website and the various screens that are being opened and closed as the tests are run.  
+
Note that the entire suite of tests takes about one hour to run. When they are done, you will get a summary display showing how many tests were run and whether there were errors or failures. If there are errors or failures, the line of code from the test program that generated the error or failure will also show. An error occurs when the test encounters an actual PHP error. A failure occurs when the test gets a result that is different than expected (when one of the assert statements in the test is not as expected).  
  
−
The tests will run for a few minutes, depending on the speed of your system. When they are done, you will get a summary display showing how many tests were run and whether there were errors or failures. If there are errors or failures, the line of code from the test program that generated the error or failure will also show.
+
If you use the default phpunit.xml.dist file, a file <code>tests/system/suite/logs/junit.xml</code> will be created at the conclusion of the test. This file can be interpreted by Eclipse and any other program that works with JUnit unit tests. It provides a graphical way to see the test results.
  
−
An error occurs when the test encounters an actual PHP error. A failure occurs when the test gets a result that is different than expected.
+
===Run Selected Tests===
 +
As with the unit tests, you can run selected system tests by folder or file. For example, the following command will run all of the tests in the acl folder:
 +
 
 +
<code>phpunit suite/acl</code>
 +
 
 +
To run a the article0001Test.php tests:
 +
 
 +
<code>phpunit suite/articles/article0001Test.php</code>
 +
 
 +
==Webdriver Tests==
 +
Webdriver is the newer system test program from Selenium. In general, all new Joomla system tests should be written with Webdriver.
 +
 
 +
The Webdriver tests are in the folder <code>tests/system/webdriver</code>. This folder has the following subfolders:
 +
* '''Pages:''' Contains the page class files for the CMS.
 +
* '''SeleniumClient:''' Contains the Nearsoft library files. These are files that allow us to write the Webdriver tests in PHP (instead of Java). They are maintained on Gihub at [https://github.com/Nearsoft/PHP-SeleniumClient https://github.com/Nearsoft/PHP-SeleniumClient].
 +
* '''tests:''' Contains the folders with the test programs. These use the Pages files.
 +
 
 +
There is also a file called <code>bootstrap.php</code> in the webdriver folder. This is used to auto-load the required classes. Inside the tests folder we have a file called <code>JoomlaWebdriverTestCase.php</code>. This file is the parent class for all Webdriver tests and has a number of useful methods.
 +
 
 +
===Run All Webdriver Tests===
 +
Running the Webdriver tests is exactly the same as running the old system tests except for the starting directory. The steps are:
 +
* Make sure the Selenium Server is running in the background.
 +
* Change directory to the <code>tests/system/webdriver/tests</code> folder.
 +
* Execute the command: <code>phpunit</code>
 +
 
 +
This will by default use the configuration file <code>tests/system/webdriver/tests/phpunit.xml.dist</code>, which is included with the CMS checkout. You can customize this by copying it to phpunit.xml and editing as desired. You do not need to delete the <code>phpunit.xml.dist</code> file because the <code>phpunit.xml</code> file takes priority if both are found.
 +
 
 +
Webdriver tests only open one browser window. Like the Selenium RC system tests, Webdriver tests are relatively slow -- similar to a very fast data entry person using the application.
 +
 
 +
===Run Selected Webdriver Tests===
 +
You can run selected Webdriver tests by folder or by file just as you do for the other system tests or for the unit tests. The only difference is the starting folder.
  
 
== Tips ==
 
== Tips ==
−
* Make sure you run the tests on a clean database that has been installed with sample data. If you have made database changes, you should re-install Joomla! or otherwise put the database back to it's original post-installed state.
+
* Make sure you run the tests on a clean database that has been installed with sample data. If you have made database changes, you should re-install Joomla! or otherwise put the database back to it's original post-installed state. When you run the entire system test suite, the first test does a clean re-install for you automatically. This tests the installation and also makes sure the database is in an expected state.
−
* If you find errors or failures when you run the tests, you can run the tests against the Joomla! trunk to see if the problems are in trunk or just in your branch.
+
* If you find errors or failures when you run the tests, you can run the tests against the Joomla! master branch to see if the problems are in master or just in your branch.
−
* If you maintain more than one local Joomla! project (for example, one for trunk, another for a branch), you will need to make sure to have a configdef.php file for each that has the right path and login information. You can watch the browser window while the tests are running to make sure you are testing the URL that you expect.
 
−
* If you use Eclipse, you can use the External Tools Configurations option to create launch configurations to run the tests. For example, to create a launch configuration to run the test suite of the currently-selected Eclipse project, you would enter the location that points to your phpunit.bat file, set the Working Directory to "${project_loc}\tests\system", and set the arguments to <code>--bootstrap servers\configdef.php suite\TestSuite.php</code>. This is shown in the screenshot below.
 
−
 
 
−
[[Image:Selenium_tutorial_screenshot_20100205.png]]
 
  
−
: Then you can run this from inside Eclipse and the console output will show in the Eclipse console. Note that you still need to have the Selenium RC program running in the background first, before running the suite. Note that you need to select a file in the current project before running this command so the <code>{project_loc}</code> variable is set correctly.
+
== Eclipse Users ==
 +
In Eclipse, you can set up Debug and External Tools launch configurations that make it easy to debug or run unit and system tests. See [[Running Automated Tests from Eclipse|Running Automated Tests from Eclipse]].
  
−
[[Category:Bug Squad]] [[Category:Development]]
+
[[Category:Bug Squad]] [[Category:Development]] [[Category:Testing]] [[Category:Automated Testing]] [[Category:Joomla! 2.5]][[Category:Joomla! 3.x]]

Revision as of 03:38, 18 October 2014

Introduction[edit]

This article has been updated during the Testing Sprint in October 2014 to reflect the latest information for running unit and system tests for Joomla version 3.x

When you checkout the staging branch of Joomla from Github.com (https://github.com/joomla/joomla-cms) you will see a folder called "tests". This folder contains unit and two types of system tests for the CMS. The unit tests use PHPUnit and the system tests use PHPUnit and Selenium. The unit tests perform tests on the framework and cms library files (libraries/cms and libraries/joomla) and on parts of com_finder. The Webdriver system tests run Joomla! from a browser and test it as a user would.

Before you can run the tests, you need to install some programs on your local workstation, as documented below. This document explains how to run those tests from your local workstation.

PHP Requirements[edit]

You may need to modify your PHP configuration. This is done by editing your php.ini file and then restarting your Apache service.

CMS Unit Tests[edit]

Some of the CMS unit tests rely on the PHP extension Sqlite3. To run these tests, make sure that the following line in your php.ini file is uncommented:

  • For Windows: extension=php_sqlite3.dll
  • For Linux: extension=php_sqlite3.so

On top of that, it might be necessary to increase your PHP memory limit, as some tests are consuming a lot of resources: 

memory_limit=512M

Webdriver System Tests[edit]

The Webdriver system tests require that the Curl extension is installed. Make sure the following line in your php.ini file is uncommented:

  • For Windows: extension=php_curl.dll
  • For Linux: extension=php_curl.so

Install PHPUnit[edit]

Both the unit and system tests rely on PHPUnit. PHPUnit is a testing framework that requires PHP to be installed on the local workstation. Please visit http://phpunit.de/ and follow the instructions to install the PHPUnit PHAR Archive.

Windows Users[edit]

The instructions at http://phpunit.de/ may not work on Windows. Most likely, Windows users will not have the `wget` command used in the instructions. However, if msysgit is installed, curl should be available. If it is, then the simplest way to install PHPUnit on Windows is to just use this command: 

   curl https://phar.phpunit.de/phpunit.phar > _some_directory_in_your_path_/phpunit

This will download the phar file and store it without the phar extension so that you can run the command simply by running: 

   phpunit

Running Unit Tests[edit]

Run Suite from XML File[edit]

Once PHPUnit is installed, it's easy to run the unit tests. The command that runs the tests is called phpunit. This file is found in your PHP folder. For example, in Windows with Xampp, it would be c:/xampp/php/phpunit. In Linux, with Xampp, it might be /opt/lampp/bin/phpunit. If you add this to your operating system path, you can execute it from any folder without using the full path name.

When you run phpunit it looks for a PHPUnit configuration XML file (either phpunit.xml or phpunit.xml.dist). The CMS unit tests are run from the Joomla root folder, where you will find the phpunit.xml.dist file. This file is included in the Git repository and can be used as is or customized (by making a copy called phpunit.xml).

To run all of the unit tests from the command line:

  1. Change Joomla root folder
  2. Execute the command phpunit.

The following example runs the entire unit test suite on OS X. 

MyMacbook:joomla-cms sniper$ phpunit
PHPUnit 4.3.2 by Sebastian Bergmann.

Configuration read from /Users/myself/joomla-cms/phpunit.xml

.....S.......................................................   61 / 5373 (  1%)
............................................................. 2745 / 5373 ( 51%)
SSSSSSSSSSSSSSSSSSSSSSSS..................................... 5368 / 5373 ( 99%)
.....

Time: 57.29 seconds, Memory: 186.75Mb

OK, but incomplete, skipped, or risky tests!
Tests: 5373, Assertions: 9914, Skipped: 157.

Generating code coverage report in Clover XML format ... done

Generating code coverage report in HTML format ... done

The dots indicate a successful test. If you have errors or failures, they will show as "E" or "F" letters and a detailed message for each will show. If you are generating code coverage or other logs, you can see the folders where these are generated in the XML file. In the default file, all of the logs are generated in build/logs, with coverage information in a folder called build/coverage.

You can create your own phpunit.xml file by copying the phpunit.xml.dist file and making the desired changes. For example, if you don't want to create the coverage information, remove the log type="coverage-html" element.

Run Selected Unit Tests[edit]

Running A Selected Suite[edit]

Joomla's unit tests are grouped into a number of different suites:

  • libraries-cms
  • libraries-platform
  • libraries-legacy
  • database
  • administrator
  • FinderIndexer

You can run unit tests grouped in a specific folder by appending the --testsuite parameter. The following example runs all of the tests in the database suite: 

MyMacbook:joomla-cms sniper$ phpunit --testsuite database
PHPUnit 4.3.2 by Sebastian Bergmann.

Configuration read from /Users/myself/joomla-cms/phpunit.xml

...............................................................  63 / 354 ( 17%)
............................................................... 126 / 354 ( 35%)
..............................SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS 189 / 354 ( 53%)
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS................................ 252 / 354 ( 71%)
..................SSSSSS....................................... 315 / 354 ( 88%)
...........SSSSSSSSSSSSSSSSSSSSSSSSS...

Time: 2.51 seconds, Memory: 20.00Mb

OK, but incomplete, skipped, or risky tests!
Tests: 354, Assertions: 718, Skipped: 95.

Running Tests In A Specific Folder[edit]

You can run unit tests one at a time or by folder. The following example runs all of the tests in the libraries/feed folder: 

MyMacbook:joomla-cms sniper$ phpunit tests/unit/suites/libraries/joomla/feed
PHPUnit 4.3.2 by Sebastian Bergmann.

Configuration read from /Users/myself/joomla-cms/phpunit.xml

................S.S............................................  63 / 101 ( 62%)
......................................

Time: 335 ms, Memory: 8.50Mb

OK, but incomplete, skipped, or risky tests!
Tests: 101, Assertions: 201, Skipped: 2.

You can also specify a single test simply by specifying it's full path name in the command.


Running Tests Filtered By Name[edit]

You can run all unit tests which names are matching a specific naming pattern by appending the --filter parameter. The following example runs all tests starting with JModel like:

  • JModelBaseTest
  • JModelDatabaseTest
  • JModelLegacyTest
  • ...
MyMacbook:joomla-cms sniper$ phpunit --filter JModel
PHPUnit 4.3.2 by Sebastian Bergmann.

Configuration read from /Users/myself/joomla-cms/phpunit.xml

................................................................. 65 / 95 ( 68%)
..............................

Time: 4.58 seconds, Memory: 95.00Mb

OK (95 tests, 140 assertions)

Running a single test

  • JModelLegacyTest::testConstructorSetsCorrectStateObject

Running the Database Testsuites[edit]

By default, only the tests for Sqlite are run in the database testsuite, because all other tests for database systems like MySQL, PostgreSQL and MSSQL require a working database, valid credentials and some preparations. This example documents the necessary steps to get the MySQL tests running:

  1. create a new, empty database
  2. create a user that is allowed to access the created database
  3. import the default dataset, dumped in tests/unit/schema/mysql.sql, into the database
  4. copy the file phpunit.xml.dist to phpunit.xml
  5. uncomment and update the database dsn constants in the <php> block of your new phpunit.xml:
<?xml version="1.0" encoding="UTF-8"?>
<phpunit bootstrap="tests/unit/bootstrap.php" colors="false">
    <php>
        <const name="JTEST_DATABASE_MYSQL_DSN" value="host=YOURHOST;dbname=YOURDBNAME;user=YOURUSER;pass=YOURPASSWORD" />
        <const name="JTEST_DATABASE_MYSQLI_DSN" value="host=YOURHOST;dbname=YOURDBNAME;user=YOURUSER;pass=YOURPASSWORD" />
    </php>
...

Selenium RC System Tests[edit]

The older Selenium RC system tests are in the folder tests/system/suite. Before you can run the system tests, you need to install and download the Selenium Server program and configure your test environment, as shown below.

Download Selenium Server[edit]

Selenium Server (formerly Selenium RC) is the package that allows us to run Selenium tests from PHP (instead of Java). To download it, just go to the Selenium site http://seleniumhq.org/download/ and download the Selenium Server file (for example, selenium-server-standalone-2.25.0.jar) to a folder.

For example, in Windows you can create a folder called C:\selenium and copy this file there. In that folder, create a Windows bat file (such as selenium.bat though the name does not matter) or Linux shell script that runs the following command:

java -Xms40m -Xmx256m -jar selenium-server-2.25.0.jar

(Obviously you will need to use the exact name of the .jar file for the version you downloaded.) The -Xms and -Xmx arguments run the server program allocating more memory to Java than the default. That seems to help prevent intermittent errors when running a long suite of system tests.

If the Java executable is not on your path, then you will need to indicate the full path to it, like the following:

"c:\program files (x86)\Java\jre6\bin\java.exe" -Xms40m -Xmx256m -jar selenium-server-2.25.0.jar

This program needs to be running in the background before you can run any Selenium functional tests. So just run this program from a Bat file and it will continue to run in the background in a console window until you close it (for example, with Ctrl+C).

Create a Selenium Configuration File[edit]

To run the Selenium tests, we have to tell Selenium how to navigate and login to our local Joomla! installation. This is done by creating a PHP file called tests/system/servers/configdef.php. The Joomla! download includes a file called tests/system/servers/config-def.php-dist. This is a sample file that you can use to create the real file. Copy this file to a file called tests/system/servers/configdef.php and edit it to reflect your test systems configuration. There are comments in the file that tell you how to do this.

Run the System Test Suite[edit]

At this point, we are ready to actually run the tests. There are two steps to running a test. First, you need to make sure the Selenium Server process is running in the background. To do this, just execute the command (bat file or shell script) you created when you installed Selenium. This will continue to run (in a console window) until you cancel it. You do not need to stop and start this for each test. Just run it once and let it run in the background.

Once Selenium is running, you need to execute the system tests. These are executed the same way we did the unit tests, except for our starting directory.

To run all tests from the command line in Windows, change to the tests/system folder and run the following command

phpunit

By default, this will use the tests/system/phpunit.xml.dist file that is included with the Joomla checkout. This will run all of the tests listed in the phpunit.xml.dist file. You should see two browser windows open. One will display Selenium commands that are being executed. The other will show the Joomla! website and the various screens that are being opened and closed as the tests are run. As each test is completed, you will see comments in the console window describing each step in the test.

Note that the entire suite of tests takes about one hour to run. When they are done, you will get a summary display showing how many tests were run and whether there were errors or failures. If there are errors or failures, the line of code from the test program that generated the error or failure will also show. An error occurs when the test encounters an actual PHP error. A failure occurs when the test gets a result that is different than expected (when one of the assert statements in the test is not as expected).

If you use the default phpunit.xml.dist file, a file tests/system/suite/logs/junit.xml will be created at the conclusion of the test. This file can be interpreted by Eclipse and any other program that works with JUnit unit tests. It provides a graphical way to see the test results.

Run Selected Tests[edit]

As with the unit tests, you can run selected system tests by folder or file. For example, the following command will run all of the tests in the acl folder:

phpunit suite/acl

To run a the article0001Test.php tests:

phpunit suite/articles/article0001Test.php

Webdriver Tests[edit]

Webdriver is the newer system test program from Selenium. In general, all new Joomla system tests should be written with Webdriver.

The Webdriver tests are in the folder tests/system/webdriver. This folder has the following subfolders:

  • Pages: Contains the page class files for the CMS.
  • SeleniumClient: Contains the Nearsoft library files. These are files that allow us to write the Webdriver tests in PHP (instead of Java). They are maintained on Gihub at https://github.com/Nearsoft/PHP-SeleniumClient.
  • tests: Contains the folders with the test programs. These use the Pages files.

There is also a file called bootstrap.php in the webdriver folder. This is used to auto-load the required classes. Inside the tests folder we have a file called JoomlaWebdriverTestCase.php. This file is the parent class for all Webdriver tests and has a number of useful methods.

Run All Webdriver Tests[edit]

Running the Webdriver tests is exactly the same as running the old system tests except for the starting directory. The steps are:

  • Make sure the Selenium Server is running in the background.
  • Change directory to the tests/system/webdriver/tests folder.
  • Execute the command: phpunit

This will by default use the configuration file tests/system/webdriver/tests/phpunit.xml.dist, which is included with the CMS checkout. You can customize this by copying it to phpunit.xml and editing as desired. You do not need to delete the phpunit.xml.dist file because the phpunit.xml file takes priority if both are found.

Webdriver tests only open one browser window. Like the Selenium RC system tests, Webdriver tests are relatively slow -- similar to a very fast data entry person using the application.

Run Selected Webdriver Tests[edit]

You can run selected Webdriver tests by folder or by file just as you do for the other system tests or for the unit tests. The only difference is the starting folder.

Tips[edit]

  • Make sure you run the tests on a clean database that has been installed with sample data. If you have made database changes, you should re-install Joomla! or otherwise put the database back to it's original post-installed state. When you run the entire system test suite, the first test does a clean re-install for you automatically. This tests the installation and also makes sure the database is in an expected state.
  • If you find errors or failures when you run the tests, you can run the tests against the Joomla! master branch to see if the problems are in master or just in your branch.

Eclipse Users[edit]

In Eclipse, you can set up Debug and External Tools launch configurations that make it easy to debug or run unit and system tests. See Running Automated Tests from Eclipse.

Retrieved from "https://docs.joomla.org/index.php?title=Running_Automated_Tests_for_the_Joomla_CMS&oldid=127978"