Joomla! Documentation - User contributions [en]

Working with git and github

2011-10-10T06:28:48Z

PtrNrs: /* Eclipse */

This document will provide a brief overview of working with the Joomla Platform repository on github.com for people who are interested in making code contributions and using eclipse as an IDE. Much will also apply for people who just want to follow development, but that is much simpler.

Some preliminary information.

== What is Git? ==

Git is distributed version control software. Such software (another example is Mercurial while subversion and CVS are non distributed version control systems) allow many people to contribute code to a single project and also allow for well defined tracking of code changes and provide mechanisms for recording commit by commit records of changes.

== What is Github? ==

Github is a host for git repositories. It is located at [https://github.com github.com]

== What is the Joomla! Platform? ==

The Joomla! Platform also known as the Joomla! Framework is the set of libraries that are used to build the Joomla! CMS and other applications.

The platform is managed separately from the CMS and has its own release cycle; each release of the CMS uses one specific version of the platform.

The platform repository is located at: [https://github.com/joomla/joomla-platform github.com/joomla/joomla-platform]

== First steps: Github account ==

First, you will need to register at git hub.

Once registered, you will probably want to go to [https://github.com/joomla/joomla-platform github.com/joomla/joomla-platform ] and click follow. Then whenever you log in you will see the latest things that have happened in the repository.

If you are going to code, you will also want to click on fork. This will give you your own copy of the platform to work with. You'll probably want to follow that too.

== Second steps: Install git ==

Now you will want to install git on your local workstation. Github provides excellent instructions on how to do this that will detect your operating system. Simply click on the Set Up Git button.

You will need to set up SSH. As it says on the Github instructions " Setting them up is fairly easy, but does involve a number of steps." Some will be specific to your operating system, so follow the instructions at github.

You will also need to tell Git your user name and password so that it can connect to your repositories on github.

== Third steps ==

=== Command Line ===
If you like using the command line, git by itself provides commands to create a local copy of your fork at github. There are a number of tutorials and reference sites for git including:
* [http://git-scm.com/documentation git-scm.com/documentation]
* [http://gitimmersion.com/ gitimmersion]

Github itself has many documents about how to use git on its help site
*[http://help.github.com/ help.github.com/]

=== Eclipse ===

Git can also be used with Eclipse, a popular integrated development environment (IDE).

Setting up Eclipse to work with git and github involves a number of steps.

Important references are:
[http://wiki.eclipse.org/EGit/User_Guide wiki.eclipse.org/EGit/User_Guide]
and
[http://wiki.eclipse.org/EGit/GitHub/UserGuide wiki.eclipse.org/EGit/GitHub/UserGuide]

First, you will need to install eGit and Mylyn. Mylyn is probably not really necessary but it will let you access other features of github. Note that Mylyn has dependencies and you will need to install them first (see the user's guide).

To install eGit from eclipse, go to Help>Eclipse Marketplace. Search for git and click install.

Follow the instructions to fill in your github account information to identify yourself, defaults and other settings.

Once installed, if you click File>Import you should see Git listed as an option and projects from Git as a sub option.

Note the following owes a lot to a number of sites including [http://blog.opsb.co.uk/getting-started-with-git-github-and-eclipse-p http://blog.opsb.co.uk/getting-started-with-git-github-and-eclipse-p].

One important thing to note before starting is that we will be working with the fork you made in Step 1 (If you didn't make a fork then, do it now). Thus we will not be making a new repository. When reading help materials make sure not to follow instructions to create a new remote repository.

Your fork on github will have a set of three links (ssh, http, git read-only) . You will need the http link.

Click File>Import.
Choose Projects from Git, click next.
On the next screen, click Clone and add your http link. The other fields except your password will autofill. (If you haven't set up your username previously you will need this too).

Click Next, select master (that is all you will have if this is your first time).
Set a directory.
Click finish and the files from git will be cloned which means they will be downloaded to your folder.

Next Eclipse will want to create a project. Do not do it!! Instead, in a way that works for your operating system create a hidden file called .project.

In the file put:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
<name>joomla-platform</name>
<comment></comment>
<projects>
</projects>
<buildSpec>
<buildCommand>
<name>org.eclipse.wst.validation.validationbuilder</name>
<arguments>
</arguments>
</buildCommand>
</buildSpec>
<natures>
<nature>org.eclipse.php.core.PHPNature</nature>
</natures>
</projectDescription>
</syntaxhighlight>

But change joomla-platform to the name of your folder.

Now your folder should appear on the list of projects. Select it and finish.

You should now have a git local repository.

== Getting to Work ==

Once you have your repository you are ready to start working on code.
Whenever you have some code that you are happy with, you should commit it locally. Note that unless you commit, your local changes will not enter into version control.
To commit, you click Team>commit.

=== Creating patches ===
The most painless method seems to be the command line as described on the [http://git-scm.com git home page] as a quick start "Cloning and Creating a Patch"

<pre>
$ git clone git://github.com/joomla/joomla-platform.git
$ cd joomla-platform
$ (edit files)
$ git add (files)
$ git commit -m 'Explain what I changed'
$ git format-patch origin/master
</pre>

It seems also possible to create patches in eclipse eGit

You can also use git-diff to create patches, to create a diff with the latest commit
<pre>
$ git diff --no-prefix ^HEAD
</pre>

To be continued ...

== Trouble Shooting ==

If you get a message about unpacking try adding .git to the end of the remote repository url.

== Reference ==

* [http://progit.org/book/ Pro Git]
* [http://www.ndpsoftware.com/git-cheatsheet.html Git Cheatsheet]

Running Automated Tests for the Joomla CMS

2010-07-04T08:25:21Z

PtrNrs: /* Tips */

{{RightTOC}}
== 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 system (or functional) tests. The unit tests use PHPUnit and the system tests use PHPUnit and Selenium. The unit tests perform tests primarily on the Joomla! framework. The Selenium system tests actually 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 the these tests from your local workstation.

== Install PHPUnit ==
Both the unit and functional tests rely on PHPUnit. PHPUnit is a testing framework that requires PHP to be installed on the local workstation. XAMP / WAMP users can use the PHP installation that comes with them. Otherwise, you may need to install PHP, and the PEAR package, on your local workstation. More detailed instructions can be found at [http://www.php.net/manual/en/install.php http://www.php.net/manual/en/install.php].

On most PHP installations, PNPUnit can be installed using the standard PEAR installation process.

For example, on XAMPP version 1.7.3 on Windows, you would do the following commands:

* <code>cd c:\xampp\php</code>
* <code>pear channel-discover pear.phpunit.de</code>
* <code>pear channel-discover pear.symfony-project.com</code>
* <code>pear install phpunit/PHPUnit</code>

If you get error about PEAR version too low, run:

* <code>pear upgrade pear</code>

and repeat <code>pear install phpunit/PHPUnit</code>
.
Windows users not using WAMP or XAMPP can use the same procedure, with substituting the location of your PHP installation for <code>cd c:\xampp\php</code>.

In Ubuntu Linux, use the following commands to install PHPUnit:

* <code>$sudo pear channel-discover pear.phpunit.de</code>
* <code>$sudo pear channel-discover pear.symfony-project.com</code>
* <code>$sudo pear install phpunit/PHPUnit</code>

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].

== Set Up Configuration File ==
Many unit tests can run independent of an actual Joomla! instance or database. Other tests require a connection to a Joomla! database. For these tests to run correctly, you need to create a test config.php file.

If you don't have a correct configuration file, you will see a message similar to the one below when you try to run certain unit tests:

PHP Fatal error: Class 'JElement' not found in
/local/www/joomla_trunk/libraries/joomla/html/parameter/element/list.php on line 22

To create a configuration file:

# Copy the file <code>tests/unit/config.php-dist</code> to the name <code>tests/unit/config.php</code>.
# Edit the <code>config.php<code> file to match your test configuration. The configuration must point to a valid Joomla! 1.6 database. You can use any installed Joomla! 1.6 database.
# The values you oneed to edit are as follows:
::'''$user''': database user id (for example, 'root' or whatever login needed to connect to the db)
::'''$password''': database user password
::'''$db''': database name
::'''$tmp_path''': <Joomla! root>/tmp
::'''$log_path''': <Joomla! root>/log
: You can use your <code>configuration.php</code> file as a guide for these entries, if needed.

When you run unit tests that use the database, the database will become unusable for a normal Joomla! instance. There are two ways to fix this.
# Re-install Joomla! after the unit tests have run. This recreates the database and fixes any problems.
# Use a different database for the unit tests. For example, you can run the installation of Joomla! and give it a different database name and use this database name in the <code>tests/unit/config.php</code> file.

== Running Unit Tests ==
Once PHPUnit is installed, you can run the unit tests. To run a unit test from the command line:
# Change to the folder <code><joomla root>/tests/unit</code>
# Execute the command <code>phpunit <test name or folder></code>
For example, to execute the test called "suite\libraries\joomla\utilities\JStringTest.php", you would type the command
* <code>phpunit suite\libraries\joomla\utilities\JStringTest.php</code>

When you run this, you will see output similar to the following:
<pre>
C:\xampp\htdocs\joomla_development\j16_trunk\tests\unit>phpunit suite\libraries\
joomla\utilities\jstringtest.php
PHPUnit 3.4.11 by Sebastian Bergmann.

............................................................ 60 / 89
.............................

Time: 26 seconds, Memory: 7.00Mb

OK (89 tests, 89 assertions)
</pre>
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.

You can execute all of the tests in a folder by specifying a folder instead of a file. For example, to run all of the tests in the folder "suite\libraries\joomla\utilities", you would enter
* <code>phpunit suite\libraries\joomla\utilities</code>

This command will produce output similar to that shown below:
<pre>
C:\xampp\htdocs\joomla_development\j16_trunk\tests\unit>phpunit suite\libraries\
joomla\utilities
PHPUnit 3.4.11 by Sebastian Bergmann.

............................................................ 60 / 317
............................................................ 120 / 317
............................................................ 180 / 317
............................................................ 240 / 317
............................................................ 300 / 317
...FFFF..........

Time: 27 seconds, Memory: 11.00Mb

There were 4 failures:

1) JUtilityTest::testGetHash
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-ce114e4501d2f4e2dcea3e17b546f339
+0cbc6611f5540bd0809a388dc95a615b

2) JUtilityTest::testGetToken with data set "default" (NULL, false)
Failed asserting that <string:adca734617ce829cc979492d6d037416> matches expected
<boolean:false>.

3) JUtilityTest::testGetToken with data set "false" (false, false)
Failed asserting that <string:adca734617ce829cc979492d6d037416> matches expected
<boolean:false>.

4) JUtilityTest::testGetToken with data set "true" (true, true)
Expectation failed for method name is equal to <string:getFormToken> when invoke
d 1 time(s).
Method was expected to be called 1 times, actually called 0 times.

FAILURES!
Tests: 317, Assertions: 361, Failures: 4.</pre>
In this case, we have 4 test failures with details about each.

== System Tests ==
Before you can run the system tests, you need to install and set up the Selenium RC package and configure your test environment, as shown below.

=== Install Selenium RC ===
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.

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 (such as selenium.bat though the name does not matter) or Linux shell script that runs the following command:

<code>java -jar selenium-server.jar -browserSessionReuse</code>

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>

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.

If You are using Firefox 3.6.x, be sure to install Selenium RC version 1.0.3 (released February 2010) or later. Earlier versions of Selenium RC have problems running in Firefox 3.6.x.

=== Create a Selenium Configuration File ===
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.

=== Run the System Test Suite ===
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 (the phpunit.bat file comes from the PHPUnit installation):

<code>phpunit.bat --bootstrap servers\configdef.php suite\TestSuite.php </code>

In Linux, the command is:

<code>phpunit --bootstrap servers/configdef.php suite/TestSuite.php </code>

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.

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.

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.

== 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.
* 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 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 TestSuite fails with a red Error message when importing sample data (a Joomla install is the first step in TestSuite), you may need to increase the time allowed for the sample data import in the following line 57 of tests/system/suite/doInstall.php.
if ($second >= 15) $this->fail("timeout");

== 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.

=== Run a Unit Test ===
You can create an External Tools launch configuration that lets you run any unit test simply by pointing to the test file and pressing the Run button. Here are the steps:
* Open the Run→External Tools→External Tools Configuration menu and press the button labeled "New Launch Configuration".
* Enter a descriptive name, such as "Run Selected Unit Test".
* Enter the location that points to your phpunit.bat file (for example, <code>c:\xampp\php\phpunit.bat</code>).
* Set the Working Directory to <code>${project_loc}\tests\unit</code>
* Set the arguments to <code>c:\xampp\php\phpunit --verbose "${resource_loc}"</code>.
This is shown in the screenshot below.

[[Image:unit_test_tutorial_screenshot_20100405-01.png]]

To run a unit test:
# Select a unit test, either by selecting it in the PHP Explorer view or in the edit area of Eclipse.
# Run the External Launch configuration by selecting it from the drop-down list next to the External Launch Configuration button in the toolbar (shown below).

[[Image:unit_test_tutorial_screenshot_20100406-01.png]]

Note that a test might normally take a 30-60 seconds to run. The output of the test will show in the Eclipse console.

==== Run All Tests in a Folder ====
You can run all of the unit tests in a folder using this same launch configuration. Just select a folder instead of a test file and all of the unit tests in that folder will run.

=== Setting Up For Debugging ===

==== Make Sure XDebug is Installed ====
As you would expect, XDebug must be installed and configured for use with Eclipse. See [[Setting_up_your_workstation_for_Joomla!_development#Edit_PHP.INI_File]] for detailed instructions.

==== Add PEAR Library to Workspace ====
Before you can debug a unit or system test, you have to add the PEAR library to your project or workspace. In this example, we will add PEAR to our workspace. That way, all projects will automatically have access to PHPUnit.

Here are the steps:

* Select Window→Preferences→PHP→PHP Libraries.
* Press the New button and add PEAR as shown below. Be sure to press the checkbox labeled "Add to environment".

[[Image:unit_test_tutorial_screenshot_20100406-01a.png]]

* Press OK, then press the Add External folder button and browse to your PEAR folder, as shown below. In this example, the folder is in <code>c:\xampp\php\PEAR</code>.

[[Image:unit_test_tutorial_screenshot_20100406-01b.png]]

* Press OK and the screen should show the external folder, as shown below, with the correct file path for your workstation.

[[Image:unit_test_tutorial_screenshot_20100406-01c.png]]

After this is completed go to project preferences - > Properties -> PHP Include path -> Libraries tab -> Add library. Select User library in popup, click Next and mark Pear[enviroment] as checked.

Also make sure your project folder is added in Source tab of your project's PHP Include path.

==== Configure the PHP Executable ====
Normally, you will want to debug unit and system tests as PHP scripts (as opposed to web pages). Before you can do this, you need to configure a PHP Executable in Eclipse. This is done as follows:
* Select Window→Preferences→PHP→PHP Executables. The screen below will show.

[[Image:unit_test_tutorial_screenshot_20100406-05.png]]

* Press Add and complete the screen as shown below, substituting the correct file paths for your workstation.

[[Image:unit_test_tutorial_screenshot_20100406-06.png]]

At this point, your workstation is set up for PHPUnit debugging. Now you just have to create the debug configurations as shown in the next section.

=== Debug a Single Unit Test ===
Once you have PEAR added to your libraries, it is easy to set up a debug configuration that allows you to debug any unit test. Here are the steps:
* Press the drop-down arrow next to the Debug button and select Debug Configurations from the menu, as shown below.

[[Image:unit_test_tutorial_screenshot_20100406-02.png]]

* In the Debug Configurations window, make sure that PHP Script is selected and press the New Launch configuration button as shown below.

[[Image:unit_test_tutorial_screenshot_20100406-17.png]]

* Fill out the PHP Script tab of the Debug Configurations as shown below.
** Name: a descriptive name like "Debug Selected Unit Test"
** PHP Debugger: XDebug
** PHP Executable: The one you set up earlier (there will only be one)
** PHP File: Use the Browse button to browse to the phpunit.php file in your <code>tests/system</code> folder.

[[Image:unit_test_tutorial_screenshot_20100406-10.png]]

* Select the PHP Script Arguments tab and enter --verbose ${selected_resource_loc} as shown below.
** The "--verbose" option allows you to see more details when the tests are run.
** The "${selected_resource_loc}" passes the currently selected file at runtime, so you can use this configuration just by selecting the desired file and then running it.

[[Image:unit_test_tutorial_screenshot_20100406-11.png]]

* Finally, select the Common tab and check the Debug checkbox under "Display in favorites menu", as shown below.

[[Image:unit_test_tutorial_screenshot_20100406-09a.png]]

At this point, you are ready to debug any unit test. All you need to do is:
# Select the desired test file either in the PHP Explorer view or in the editor.
# Select Debug Configurations from the Debug drop-down button and select the "Debug Selected Unit Test" option. Once you have run this once, it will show on your Debug favorites menu.

=== Run a Single System Test ===
You can create a configuration to make it easy to run any single test in your project. To do this:
* Open the Run→External Tools→External Tools Configuration menu and press the button labeled "New Launch Configuration"
* Enter the location that points to your phpunit.bat file (for example, <code>c:\xampp\php\phpunit.bat</code>). On Linux systems, this might be called "phpunit".
* Set the Working Directory to <code>${project_loc}/tests/system</code>
* Set the arguments to <code>--bootstrap servers/configdef.php ${selected_resource_loc}</code>.
This is shown in the screenshot below.

[[Image:unit_test_tutorial_screenshot_20100406-14.png]]

To use this configuration,
# Make sure the Selenium RC process is running (for example, by running the "selenium.bat" file you created when you installed Selenium RC earlier)
# Select the desired test file by clicking on it in the PHP Explorer view or in the edit area
# Start this launch configuration
The selected test file will be run and you will see the browser session open and run the test script. The test results will be reported in the Eclipse console.

=== Debug a Single System Test ===
The steps for creating a Debug Configuration for a Selenium system test are similar to those for the unit test.
* Open Debug Configurations from the drop-down menu next to the Debug Button on the toolbar, as shown below.

[[Image:unit_test_tutorial_screenshot_20100406-02.png]]

* In the Debug Configurations window, make sure that PHP Script is selected and press the New Launch configuration button as shown below.

[[Image:unit_test_tutorial_screenshot_20100406-17.png]]

* Fill out the Debug Configurations dialog box as shown below:
** Name: A descriptive name for the configuration, like "Debug Selected System Test".
** PHP Debugger: XDebug
** PHP Executable: The one you defined earlier (there probably is only one).
** PHP File: Browse to the phpunit.php file in your <code>tests/system</code> folder.

[[Image:unit_test_tutorial_screenshot_20100406-12.png]]

* Select the PHP Script arguments and fill this out as shown below.
** --bootstrap servers/configdef.php points to the configuration file that passes the login information to Selenium.
** "${selected_resource_loc}" passes the location of the currently selected file in Eclipse to the command line.

[[Image:unit_test_tutorial_screenshot_20100406-13.png]]

* Finally, select the Common tab and check the Debug option in the Display in favorites menu. This will add this configuration to your favorites.

[[Image:unit_test_tutorial_screenshot_20100406-09a.png]]

At this point, you can debug any system test. To do so:
# Make sure the Selenium RC program is running in the background.
# Select the desired test by selecting it in the PHP Explorer or in the editor.
# Run this Debug Configuration by selecting the drop-down arrow next to the Debug button, then Debug Configurations, then the "Debug Selected System Test" configuration created above.

=== Run the System Test Suite ===
To create a launch configuration to run the Test Suite of the currently-selected Eclipse project:
* Enter the location that points to your phpunit.bat file. If you are running Linux, this file might be called phpunit.
* Set the Working Directory to <code>${project_loc}/tests\system</code>
* Set the arguments to <code>--bootstrap servers/configdef.php suite/TestSuite.php</code>.
This is shown in the screenshot below.

[[Image:unit_test_tutorial_screenshot_20100406-15.png]]

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.

[[Category:Bug Squad]] [[Category:Development]] [[Category:Testing]] [[Category:Automated Testing]] [[Category:Joomla! 1.6]]

Running Automated Tests for the Joomla CMS

2010-07-04T08:23:12Z

PtrNrs: /* Tips */

{{RightTOC}}
== 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 system (or functional) tests. The unit tests use PHPUnit and the system tests use PHPUnit and Selenium. The unit tests perform tests primarily on the Joomla! framework. The Selenium system tests actually 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 the these tests from your local workstation.

== Install PHPUnit ==
Both the unit and functional tests rely on PHPUnit. PHPUnit is a testing framework that requires PHP to be installed on the local workstation. XAMP / WAMP users can use the PHP installation that comes with them. Otherwise, you may need to install PHP, and the PEAR package, on your local workstation. More detailed instructions can be found at [http://www.php.net/manual/en/install.php http://www.php.net/manual/en/install.php].

On most PHP installations, PNPUnit can be installed using the standard PEAR installation process.

For example, on XAMPP version 1.7.3 on Windows, you would do the following commands:

* <code>cd c:\xampp\php</code>
* <code>pear channel-discover pear.phpunit.de</code>
* <code>pear channel-discover pear.symfony-project.com</code>
* <code>pear install phpunit/PHPUnit</code>

If you get error about PEAR version too low, run:

* <code>pear upgrade pear</code>

and repeat <code>pear install phpunit/PHPUnit</code>
.
Windows users not using WAMP or XAMPP can use the same procedure, with substituting the location of your PHP installation for <code>cd c:\xampp\php</code>.

In Ubuntu Linux, use the following commands to install PHPUnit:

* <code>$sudo pear channel-discover pear.phpunit.de</code>
* <code>$sudo pear channel-discover pear.symfony-project.com</code>
* <code>$sudo pear install phpunit/PHPUnit</code>

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].

== Set Up Configuration File ==
Many unit tests can run independent of an actual Joomla! instance or database. Other tests require a connection to a Joomla! database. For these tests to run correctly, you need to create a test config.php file.

If you don't have a correct configuration file, you will see a message similar to the one below when you try to run certain unit tests:

PHP Fatal error: Class 'JElement' not found in
/local/www/joomla_trunk/libraries/joomla/html/parameter/element/list.php on line 22

To create a configuration file:

# Copy the file <code>tests/unit/config.php-dist</code> to the name <code>tests/unit/config.php</code>.
# Edit the <code>config.php<code> file to match your test configuration. The configuration must point to a valid Joomla! 1.6 database. You can use any installed Joomla! 1.6 database.
# The values you oneed to edit are as follows:
::'''$user''': database user id (for example, 'root' or whatever login needed to connect to the db)
::'''$password''': database user password
::'''$db''': database name
::'''$tmp_path''': <Joomla! root>/tmp
::'''$log_path''': <Joomla! root>/log
: You can use your <code>configuration.php</code> file as a guide for these entries, if needed.

When you run unit tests that use the database, the database will become unusable for a normal Joomla! instance. There are two ways to fix this.
# Re-install Joomla! after the unit tests have run. This recreates the database and fixes any problems.
# Use a different database for the unit tests. For example, you can run the installation of Joomla! and give it a different database name and use this database name in the <code>tests/unit/config.php</code> file.

== Running Unit Tests ==
Once PHPUnit is installed, you can run the unit tests. To run a unit test from the command line:
# Change to the folder <code><joomla root>/tests/unit</code>
# Execute the command <code>phpunit <test name or folder></code>
For example, to execute the test called "suite\libraries\joomla\utilities\JStringTest.php", you would type the command
* <code>phpunit suite\libraries\joomla\utilities\JStringTest.php</code>

When you run this, you will see output similar to the following:
<pre>
C:\xampp\htdocs\joomla_development\j16_trunk\tests\unit>phpunit suite\libraries\
joomla\utilities\jstringtest.php
PHPUnit 3.4.11 by Sebastian Bergmann.

............................................................ 60 / 89
.............................

Time: 26 seconds, Memory: 7.00Mb

OK (89 tests, 89 assertions)
</pre>
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.

You can execute all of the tests in a folder by specifying a folder instead of a file. For example, to run all of the tests in the folder "suite\libraries\joomla\utilities", you would enter
* <code>phpunit suite\libraries\joomla\utilities</code>

This command will produce output similar to that shown below:
<pre>
C:\xampp\htdocs\joomla_development\j16_trunk\tests\unit>phpunit suite\libraries\
joomla\utilities
PHPUnit 3.4.11 by Sebastian Bergmann.

............................................................ 60 / 317
............................................................ 120 / 317
............................................................ 180 / 317
............................................................ 240 / 317
............................................................ 300 / 317
...FFFF..........

Time: 27 seconds, Memory: 11.00Mb

There were 4 failures:

1) JUtilityTest::testGetHash
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-ce114e4501d2f4e2dcea3e17b546f339
+0cbc6611f5540bd0809a388dc95a615b

2) JUtilityTest::testGetToken with data set "default" (NULL, false)
Failed asserting that <string:adca734617ce829cc979492d6d037416> matches expected
<boolean:false>.

3) JUtilityTest::testGetToken with data set "false" (false, false)
Failed asserting that <string:adca734617ce829cc979492d6d037416> matches expected
<boolean:false>.

4) JUtilityTest::testGetToken with data set "true" (true, true)
Expectation failed for method name is equal to <string:getFormToken> when invoke
d 1 time(s).
Method was expected to be called 1 times, actually called 0 times.

FAILURES!
Tests: 317, Assertions: 361, Failures: 4.</pre>
In this case, we have 4 test failures with details about each.

== System Tests ==
Before you can run the system tests, you need to install and set up the Selenium RC package and configure your test environment, as shown below.

=== Install Selenium RC ===
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.

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 (such as selenium.bat though the name does not matter) or Linux shell script that runs the following command:

<code>java -jar selenium-server.jar -browserSessionReuse</code>

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>

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.

If You are using Firefox 3.6.x, be sure to install Selenium RC version 1.0.3 (released February 2010) or later. Earlier versions of Selenium RC have problems running in Firefox 3.6.x.

=== Create a Selenium Configuration File ===
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.

=== Run the System Test Suite ===
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 (the phpunit.bat file comes from the PHPUnit installation):

<code>phpunit.bat --bootstrap servers\configdef.php suite\TestSuite.php </code>

In Linux, the command is:

<code>phpunit --bootstrap servers/configdef.php suite/TestSuite.php </code>

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.

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.

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.

== 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.
* 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 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 TestSuite fails with a red Error message when importing sample data (a Joomla install is the first step in TestSuite), you may need to increase the time allowed for the sample data import in the following line 57 of tests/system/suite/doInstall.php.

== 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.

=== Run a Unit Test ===
You can create an External Tools launch configuration that lets you run any unit test simply by pointing to the test file and pressing the Run button. Here are the steps:
* Open the Run→External Tools→External Tools Configuration menu and press the button labeled "New Launch Configuration".
* Enter a descriptive name, such as "Run Selected Unit Test".
* Enter the location that points to your phpunit.bat file (for example, <code>c:\xampp\php\phpunit.bat</code>).
* Set the Working Directory to <code>${project_loc}\tests\unit</code>
* Set the arguments to <code>c:\xampp\php\phpunit --verbose "${resource_loc}"</code>.
This is shown in the screenshot below.

[[Image:unit_test_tutorial_screenshot_20100405-01.png]]

To run a unit test:
# Select a unit test, either by selecting it in the PHP Explorer view or in the edit area of Eclipse.
# Run the External Launch configuration by selecting it from the drop-down list next to the External Launch Configuration button in the toolbar (shown below).

[[Image:unit_test_tutorial_screenshot_20100406-01.png]]

Note that a test might normally take a 30-60 seconds to run. The output of the test will show in the Eclipse console.

==== Run All Tests in a Folder ====
You can run all of the unit tests in a folder using this same launch configuration. Just select a folder instead of a test file and all of the unit tests in that folder will run.

=== Setting Up For Debugging ===

==== Make Sure XDebug is Installed ====
As you would expect, XDebug must be installed and configured for use with Eclipse. See [[Setting_up_your_workstation_for_Joomla!_development#Edit_PHP.INI_File]] for detailed instructions.

==== Add PEAR Library to Workspace ====
Before you can debug a unit or system test, you have to add the PEAR library to your project or workspace. In this example, we will add PEAR to our workspace. That way, all projects will automatically have access to PHPUnit.

Here are the steps:

* Select Window→Preferences→PHP→PHP Libraries.
* Press the New button and add PEAR as shown below. Be sure to press the checkbox labeled "Add to environment".

[[Image:unit_test_tutorial_screenshot_20100406-01a.png]]

* Press OK, then press the Add External folder button and browse to your PEAR folder, as shown below. In this example, the folder is in <code>c:\xampp\php\PEAR</code>.

[[Image:unit_test_tutorial_screenshot_20100406-01b.png]]

* Press OK and the screen should show the external folder, as shown below, with the correct file path for your workstation.

[[Image:unit_test_tutorial_screenshot_20100406-01c.png]]

After this is completed go to project preferences - > Properties -> PHP Include path -> Libraries tab -> Add library. Select User library in popup, click Next and mark Pear[enviroment] as checked.

Also make sure your project folder is added in Source tab of your project's PHP Include path.

==== Configure the PHP Executable ====
Normally, you will want to debug unit and system tests as PHP scripts (as opposed to web pages). Before you can do this, you need to configure a PHP Executable in Eclipse. This is done as follows:
* Select Window→Preferences→PHP→PHP Executables. The screen below will show.

[[Image:unit_test_tutorial_screenshot_20100406-05.png]]

* Press Add and complete the screen as shown below, substituting the correct file paths for your workstation.

[[Image:unit_test_tutorial_screenshot_20100406-06.png]]

At this point, your workstation is set up for PHPUnit debugging. Now you just have to create the debug configurations as shown in the next section.

=== Debug a Single Unit Test ===
Once you have PEAR added to your libraries, it is easy to set up a debug configuration that allows you to debug any unit test. Here are the steps:
* Press the drop-down arrow next to the Debug button and select Debug Configurations from the menu, as shown below.

[[Image:unit_test_tutorial_screenshot_20100406-02.png]]

* In the Debug Configurations window, make sure that PHP Script is selected and press the New Launch configuration button as shown below.

[[Image:unit_test_tutorial_screenshot_20100406-17.png]]

* Fill out the PHP Script tab of the Debug Configurations as shown below.
** Name: a descriptive name like "Debug Selected Unit Test"
** PHP Debugger: XDebug
** PHP Executable: The one you set up earlier (there will only be one)
** PHP File: Use the Browse button to browse to the phpunit.php file in your <code>tests/system</code> folder.

[[Image:unit_test_tutorial_screenshot_20100406-10.png]]

* Select the PHP Script Arguments tab and enter --verbose ${selected_resource_loc} as shown below.
** The "--verbose" option allows you to see more details when the tests are run.
** The "${selected_resource_loc}" passes the currently selected file at runtime, so you can use this configuration just by selecting the desired file and then running it.

[[Image:unit_test_tutorial_screenshot_20100406-11.png]]

* Finally, select the Common tab and check the Debug checkbox under "Display in favorites menu", as shown below.

[[Image:unit_test_tutorial_screenshot_20100406-09a.png]]

At this point, you are ready to debug any unit test. All you need to do is:
# Select the desired test file either in the PHP Explorer view or in the editor.
# Select Debug Configurations from the Debug drop-down button and select the "Debug Selected Unit Test" option. Once you have run this once, it will show on your Debug favorites menu.

=== Run a Single System Test ===
You can create a configuration to make it easy to run any single test in your project. To do this:
* Open the Run→External Tools→External Tools Configuration menu and press the button labeled "New Launch Configuration"
* Enter the location that points to your phpunit.bat file (for example, <code>c:\xampp\php\phpunit.bat</code>). On Linux systems, this might be called "phpunit".
* Set the Working Directory to <code>${project_loc}/tests/system</code>
* Set the arguments to <code>--bootstrap servers/configdef.php ${selected_resource_loc}</code>.
This is shown in the screenshot below.

[[Image:unit_test_tutorial_screenshot_20100406-14.png]]

To use this configuration,
# Make sure the Selenium RC process is running (for example, by running the "selenium.bat" file you created when you installed Selenium RC earlier)
# Select the desired test file by clicking on it in the PHP Explorer view or in the edit area
# Start this launch configuration
The selected test file will be run and you will see the browser session open and run the test script. The test results will be reported in the Eclipse console.

=== Debug a Single System Test ===
The steps for creating a Debug Configuration for a Selenium system test are similar to those for the unit test.
* Open Debug Configurations from the drop-down menu next to the Debug Button on the toolbar, as shown below.

[[Image:unit_test_tutorial_screenshot_20100406-02.png]]

* In the Debug Configurations window, make sure that PHP Script is selected and press the New Launch configuration button as shown below.

[[Image:unit_test_tutorial_screenshot_20100406-17.png]]

* Fill out the Debug Configurations dialog box as shown below:
** Name: A descriptive name for the configuration, like "Debug Selected System Test".
** PHP Debugger: XDebug
** PHP Executable: The one you defined earlier (there probably is only one).
** PHP File: Browse to the phpunit.php file in your <code>tests/system</code> folder.

[[Image:unit_test_tutorial_screenshot_20100406-12.png]]

* Select the PHP Script arguments and fill this out as shown below.
** --bootstrap servers/configdef.php points to the configuration file that passes the login information to Selenium.
** "${selected_resource_loc}" passes the location of the currently selected file in Eclipse to the command line.

[[Image:unit_test_tutorial_screenshot_20100406-13.png]]

* Finally, select the Common tab and check the Debug option in the Display in favorites menu. This will add this configuration to your favorites.

[[Image:unit_test_tutorial_screenshot_20100406-09a.png]]

At this point, you can debug any system test. To do so:
# Make sure the Selenium RC program is running in the background.
# Select the desired test by selecting it in the PHP Explorer or in the editor.
# Run this Debug Configuration by selecting the drop-down arrow next to the Debug button, then Debug Configurations, then the "Debug Selected System Test" configuration created above.

=== Run the System Test Suite ===
To create a launch configuration to run the Test Suite of the currently-selected Eclipse project:
* Enter the location that points to your phpunit.bat file. If you are running Linux, this file might be called phpunit.
* Set the Working Directory to <code>${project_loc}/tests\system</code>
* Set the arguments to <code>--bootstrap servers/configdef.php suite/TestSuite.php</code>.
This is shown in the screenshot below.

[[Image:unit_test_tutorial_screenshot_20100406-15.png]]

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.

[[Category:Bug Squad]] [[Category:Development]] [[Category:Testing]] [[Category:Automated Testing]] [[Category:Joomla! 1.6]]

Talk:Running Automated Tests for the Joomla CMS

2010-06-30T07:20:56Z

PtrNrs: /* Re: Run the System Test Suite */

== Re: Run the System Test Suite ==
I am trying to run the system test suite in the normal SVN configuration with the installation folder still present. TestSuite calls doInstall which reruns the Joomla install and then reinstalls the sample data which, by the way, failed due to a bug (http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=21250).

When I rename (or delete) the installation folder, TestSuite skips doInstall and then runs OK.

The first Tip, though, says
* 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.
This seems to indicate that we shouldn't have the installation folder, as its presence will cause the sample data to be reinstalled anyway.

But then, evry SVN update will reinstate the installation folder anyway.

What is the required configuration is for running TestSuite?

== Create a Selenium Configuration File ==

Would var $baseURI of in be the same as public $live_site?

It could be, but we don't have access to Joomla! variables when running the tests. We are running them from a browser, outside the Joomla! framework. [[User:Dextercowley|Mark Dexter]] 22:01, 6 February 2010 (UTC)

== Run the Test Suite ==
Where is / how do we create phpunit.bat?

phpunit.bat is created when you install PHPUnit (in Windows). In Linux I would guess that it is just phpunit. [[User:Dextercowley|Mark Dexter]] 22:02, 6 February 2010 (UTC)

== Failed to start new browser session, shutdown browser and ==
clear all session data... Lock file still present!

Hi All,

I installed all, how it is written on [[Running_Automated_Tests_for_Version_1.6]], i see my Firefox(3.6, WinXPSP3)-processes(new) in the taskbar started, but the second browser window was not opened! After that I see another try the FF to start, without success and so on.

----
Start of Tests:

C:\Dokumente und Einstellungen\fpolyak>cd c:\xampp\htdocs\joomla\tests\system\
C:\xampp\htdocs\joomla\tests\system>c:\xampp\php\phpunit.bat --bootstrap servers
\configdef.php suite\TestSuite.php
PHPUnit 3.4.10 by Sebastian Bergmann.
Starting ControlPanelMenu.
E^CBatchvorgang abbrechen (J/N)? j
C:\xampp\htdocs\joomla\tests\system>

----
Selenium messages (with errors messages) :

C:\selenium\selenium-remote-control-1.0.1>c:\Programme\Java\jre1.6.0_07\bin\java
.exe -jar selenium-server-1.0.1\selenium-server.jar -browserSessionReuse
11:51:38.614 INFO - Java: Sun Microsystems Inc. 10.0-b23
11:51:38.614 INFO - OS: Windows XP 5.1 x86
11:51:38.614 INFO - v1.0.1 [2696], with Core v@VERSION@ [@REVISION@]
11:51:38.614 INFO - Will recycle browser sessions when possible.
11:51:38.755 INFO - Version Jetty/5.1.x
11:51:38.755 INFO - Started HttpContext[/selenium-server/driver,/selenium-server
/driver]
11:51:38.755 INFO - Started HttpContext[/selenium-server,/selenium-server]
11:51:38.755 INFO - Started HttpContext[/,/]
11:51:38.771 INFO - Started SocketListener on 0.0.0.0:4444
11:51:38.771 INFO - Started org.mortbay.jetty.Server@1e0cf70
11:54:55.060 INFO - Checking Resource aliases
11:54:55.075 INFO - Command request: getNewBrowserSession[*chrome, http://joomla
] on session null
11:54:55.075 INFO - grabbing available session...
11:54:55.075 INFO - creating new remote session
11:54:55.544 INFO - Allocated session df59775d37ca4e77bbdb4d0f7b97d63c for http:
//joomla, launching...
11:54:55.794 INFO - Preparing Firefox profile...
11:55:19.052 ERROR - Failed to start new browser session, shutdown browser and c
lear all session data
java.lang.RuntimeException: Firefox refused shutdown while preparing a profile
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:311)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.pop
ulateCustomProfileDirectory(FirefoxChromeLauncher.java:106)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nch(FirefoxChromeLauncher.java:83)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nchRemoteSession(FirefoxChromeLauncher.java:350)
at org.openqa.selenium.server.BrowserSessionFactory.createNewRemoteSessi
on(BrowserSessionFactory.java:357)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
( BrowserSessionFactory.java:122)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
(BrowserSessionFactory.java:84)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.getNewBrowse
rSession(SeleniumDriverResourceHandler.java:699)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.doCommand(Se
leniumDriverResourceHandler.java:393)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handleComman
dRequest(SeleniumDriverResourceHandler.java:364)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handle(Selen
iumDriverResourceHandler.java:125)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
at org.mortbay.http.HttpServer.service(HttpServer.java:909)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:820)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:
245)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
Caused by: org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher$Fil
eLockRemainedException: Lock file still present! C:\DOKUME~1\fpolyak\LOKALE~1\Te
mp\customProfileDirdf59775d37ca4e77bbdb4d0f7b97d63c\parent.lock
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFileLockToGoAway(FirefoxChromeLauncher.java:269)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:309)
... 19 more
11:55:31.806 INFO - Got result: Failed to start new browser session: Unable to d
elete file C:\DOKUME~1\fpolyak\LOKALE~1\Temp\customProfileDirdf59775d37ca4e77bbd
b4d0f7b97d63c\parent.lock on session null
11:55:31.884 INFO - Command request: getNewBrowserSession[*chrome, http://joomla
] on session null
11:55:31.884 INFO - grabbing available session...
11:55:31.884 INFO - creating new remote session
11:55:31.884 INFO - Allocated session e782589f459f4d9c8c0164e05c1f8cf6 for http:
//joomla, launching...
11:55:32.040 INFO - Preparing Firefox profile...
11:55:53.719 ERROR - Failed to start new browser session, shutdown browser and c
lear all session data
java.lang.RuntimeException: Firefox refused shutdown while preparing a profile
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:311)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.pop
ulateCustomProfileDirectory(FirefoxChromeLauncher.java:106)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nch(FirefoxChromeLauncher.java:83)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nchRemoteSession(FirefoxChromeLauncher.java:350)
at org.openqa.selenium.server.BrowserSessionFactory.createNewRemoteSessi
on(BrowserSessionFactory.java:357)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
(BrowserSessionFactory.java:122)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
(BrowserSessionFactory.java:84)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.getNewBrowse
rSession(SeleniumDriverResourceHandler.java:699)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.doCommand(Se
leniumDriverResourceHandler.java:393)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handleComman
dRequest(SeleniumDriverResourceHandler.java:364)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handle(Selen
iumDriverResourceHandler.java:125)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
at org.mortbay.http.HttpServer.service(HttpServer.java:909)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:820)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837)
at org.mortbay.http.SocketListener.handleConnection(SocketListener .java:
245)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
Caused by: org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher$Fil
eLockRemainedException: Lock file still present! C:\DOKUME~1\fpolyak\LOKALE~1\Te
mp\customProfileDire782589f459f4d9c8c0164e05c1f8cf6\parent.lock
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFileLockToGoAway(FirefoxChromeLauncher.java:269)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:309)
... 19 more
11:56:06.379 INFO - Got result: Failed to start new browser session: Unable to d
elete file C:\DOKUME~1\fpolyak\LOKALE~1\Temp\customProfileDire782589f459f4d9c8c0
164e05c1f8cf6\parent.lock on session null

-----

configdef.php:

class SeleniumConfig { var $host = 'http://joomla';
var $path = '';#'/j1513/';
var $username = 'admin';
var $password = 'admin';
var $browser = '*chrome';
var $baseURI = "c:/xampp/htdocs/joomla/";}

-----

Can anybody help me please?

Thanks

This might help: [http://clearspace.openqa.org/thread/15596 http://clearspace.openqa.org/thread/15596] [[User:Dextercowley|Mark Dexter]]

Talk:Running Automated Tests for the Joomla CMS

2010-06-30T07:19:30Z

PtrNrs: /* Re: Run the System Test Suite */

== Re: Run the System Test Suite ==
I am trying to run the system test suite in the normal SVN configuration with the installation folder still present. TestSuite calls doInstall which reruns the Joomla install and then reinstalls the sample data which, by the way, failed due to a bug (http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=21250).

When I rename (or delete) the installation folder, TestSuite skips doInstall and then runs OK.

The first Tip, though, says
* 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.
This seems to indicate that we shouldn't have the installation folder, as its presence will cause the sample data to be reinstalled anyway. Remember that an SVN update will reinstate the installation folder anyway.

What is the required configuration is for running TestSuite?

== Create a Selenium Configuration File ==

Would var $baseURI of in be the same as public $live_site?

It could be, but we don't have access to Joomla! variables when running the tests. We are running them from a browser, outside the Joomla! framework. [[User:Dextercowley|Mark Dexter]] 22:01, 6 February 2010 (UTC)

== Run the Test Suite ==
Where is / how do we create phpunit.bat?

phpunit.bat is created when you install PHPUnit (in Windows). In Linux I would guess that it is just phpunit. [[User:Dextercowley|Mark Dexter]] 22:02, 6 February 2010 (UTC)

== Failed to start new browser session, shutdown browser and ==
clear all session data... Lock file still present!

Hi All,

I installed all, how it is written on [[Running_Automated_Tests_for_Version_1.6]], i see my Firefox(3.6, WinXPSP3)-processes(new) in the taskbar started, but the second browser window was not opened! After that I see another try the FF to start, without success and so on.

----
Start of Tests:

C:\Dokumente und Einstellungen\fpolyak>cd c:\xampp\htdocs\joomla\tests\system\
C:\xampp\htdocs\joomla\tests\system>c:\xampp\php\phpunit.bat --bootstrap servers
\configdef.php suite\TestSuite.php
PHPUnit 3.4.10 by Sebastian Bergmann.
Starting ControlPanelMenu.
E^CBatchvorgang abbrechen (J/N)? j
C:\xampp\htdocs\joomla\tests\system>

----
Selenium messages (with errors messages) :

C:\selenium\selenium-remote-control-1.0.1>c:\Programme\Java\jre1.6.0_07\bin\java
.exe -jar selenium-server-1.0.1\selenium-server.jar -browserSessionReuse
11:51:38.614 INFO - Java: Sun Microsystems Inc. 10.0-b23
11:51:38.614 INFO - OS: Windows XP 5.1 x86
11:51:38.614 INFO - v1.0.1 [2696], with Core v@VERSION@ [@REVISION@]
11:51:38.614 INFO - Will recycle browser sessions when possible.
11:51:38.755 INFO - Version Jetty/5.1.x
11:51:38.755 INFO - Started HttpContext[/selenium-server/driver,/selenium-server
/driver]
11:51:38.755 INFO - Started HttpContext[/selenium-server,/selenium-server]
11:51:38.755 INFO - Started HttpContext[/,/]
11:51:38.771 INFO - Started SocketListener on 0.0.0.0:4444
11:51:38.771 INFO - Started org.mortbay.jetty.Server@1e0cf70
11:54:55.060 INFO - Checking Resource aliases
11:54:55.075 INFO - Command request: getNewBrowserSession[*chrome, http://joomla
] on session null
11:54:55.075 INFO - grabbing available session...
11:54:55.075 INFO - creating new remote session
11:54:55.544 INFO - Allocated session df59775d37ca4e77bbdb4d0f7b97d63c for http:
//joomla, launching...
11:54:55.794 INFO - Preparing Firefox profile...
11:55:19.052 ERROR - Failed to start new browser session, shutdown browser and c
lear all session data
java.lang.RuntimeException: Firefox refused shutdown while preparing a profile
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:311)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.pop
ulateCustomProfileDirectory(FirefoxChromeLauncher.java:106)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nch(FirefoxChromeLauncher.java:83)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nchRemoteSession(FirefoxChromeLauncher.java:350)
at org.openqa.selenium.server.BrowserSessionFactory.createNewRemoteSessi
on(BrowserSessionFactory.java:357)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
( BrowserSessionFactory.java:122)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
(BrowserSessionFactory.java:84)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.getNewBrowse
rSession(SeleniumDriverResourceHandler.java:699)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.doCommand(Se
leniumDriverResourceHandler.java:393)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handleComman
dRequest(SeleniumDriverResourceHandler.java:364)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handle(Selen
iumDriverResourceHandler.java:125)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
at org.mortbay.http.HttpServer.service(HttpServer.java:909)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:820)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:
245)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
Caused by: org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher$Fil
eLockRemainedException: Lock file still present! C:\DOKUME~1\fpolyak\LOKALE~1\Te
mp\customProfileDirdf59775d37ca4e77bbdb4d0f7b97d63c\parent.lock
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFileLockToGoAway(FirefoxChromeLauncher.java:269)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:309)
... 19 more
11:55:31.806 INFO - Got result: Failed to start new browser session: Unable to d
elete file C:\DOKUME~1\fpolyak\LOKALE~1\Temp\customProfileDirdf59775d37ca4e77bbd
b4d0f7b97d63c\parent.lock on session null
11:55:31.884 INFO - Command request: getNewBrowserSession[*chrome, http://joomla
] on session null
11:55:31.884 INFO - grabbing available session...
11:55:31.884 INFO - creating new remote session
11:55:31.884 INFO - Allocated session e782589f459f4d9c8c0164e05c1f8cf6 for http:
//joomla, launching...
11:55:32.040 INFO - Preparing Firefox profile...
11:55:53.719 ERROR - Failed to start new browser session, shutdown browser and c
lear all session data
java.lang.RuntimeException: Firefox refused shutdown while preparing a profile
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:311)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.pop
ulateCustomProfileDirectory(FirefoxChromeLauncher.java:106)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nch(FirefoxChromeLauncher.java:83)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nchRemoteSession(FirefoxChromeLauncher.java:350)
at org.openqa.selenium.server.BrowserSessionFactory.createNewRemoteSessi
on(BrowserSessionFactory.java:357)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
(BrowserSessionFactory.java:122)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
(BrowserSessionFactory.java:84)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.getNewBrowse
rSession(SeleniumDriverResourceHandler.java:699)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.doCommand(Se
leniumDriverResourceHandler.java:393)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handleComman
dRequest(SeleniumDriverResourceHandler.java:364)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handle(Selen
iumDriverResourceHandler.java:125)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
at org.mortbay.http.HttpServer.service(HttpServer.java:909)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:820)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837)
at org.mortbay.http.SocketListener.handleConnection(SocketListener .java:
245)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
Caused by: org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher$Fil
eLockRemainedException: Lock file still present! C:\DOKUME~1\fpolyak\LOKALE~1\Te
mp\customProfileDire782589f459f4d9c8c0164e05c1f8cf6\parent.lock
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFileLockToGoAway(FirefoxChromeLauncher.java:269)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:309)
... 19 more
11:56:06.379 INFO - Got result: Failed to start new browser session: Unable to d
elete file C:\DOKUME~1\fpolyak\LOKALE~1\Temp\customProfileDire782589f459f4d9c8c0
164e05c1f8cf6\parent.lock on session null

-----

configdef.php:

class SeleniumConfig { var $host = 'http://joomla';
var $path = '';#'/j1513/';
var $username = 'admin';
var $password = 'admin';
var $browser = '*chrome';
var $baseURI = "c:/xampp/htdocs/joomla/";}

-----

Can anybody help me please?

Thanks

This might help: [http://clearspace.openqa.org/thread/15596 http://clearspace.openqa.org/thread/15596] [[User:Dextercowley|Mark Dexter]]

Talk:Running Automated Tests for the Joomla CMS

2010-06-30T07:17:12Z

PtrNrs: /* Re: Run the System Test Suite */

== Re: Run the System Test Suite ==
I am trying to run the system test suite in the normal SVN configuration with the installation folder still present. TestSuite calls doInstall which reruns the Joomla install and then reinstalls the sample data which, by the way, failed due to a bug (http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=21250).

When I rename (or delete) the installation folder, TestSuite runs OK.

The first Tip, though, says
* 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.
This seems to indicate that we shouldn't have the installation folder, as its presence will cause the sample data to be reinstalled anyway. Remember that an SVN update will reinstate the installation folder anyway.

What is the required configuration is for running TestSuite?

== Create a Selenium Configuration File ==

Would var $baseURI of in be the same as public $live_site?

It could be, but we don't have access to Joomla! variables when running the tests. We are running them from a browser, outside the Joomla! framework. [[User:Dextercowley|Mark Dexter]] 22:01, 6 February 2010 (UTC)

== Run the Test Suite ==
Where is / how do we create phpunit.bat?

phpunit.bat is created when you install PHPUnit (in Windows). In Linux I would guess that it is just phpunit. [[User:Dextercowley|Mark Dexter]] 22:02, 6 February 2010 (UTC)

== Failed to start new browser session, shutdown browser and ==
clear all session data... Lock file still present!

Hi All,

I installed all, how it is written on [[Running_Automated_Tests_for_Version_1.6]], i see my Firefox(3.6, WinXPSP3)-processes(new) in the taskbar started, but the second browser window was not opened! After that I see another try the FF to start, without success and so on.

----
Start of Tests:

C:\Dokumente und Einstellungen\fpolyak>cd c:\xampp\htdocs\joomla\tests\system\
C:\xampp\htdocs\joomla\tests\system>c:\xampp\php\phpunit.bat --bootstrap servers
\configdef.php suite\TestSuite.php
PHPUnit 3.4.10 by Sebastian Bergmann.
Starting ControlPanelMenu.
E^CBatchvorgang abbrechen (J/N)? j
C:\xampp\htdocs\joomla\tests\system>

----
Selenium messages (with errors messages) :

C:\selenium\selenium-remote-control-1.0.1>c:\Programme\Java\jre1.6.0_07\bin\java
.exe -jar selenium-server-1.0.1\selenium-server.jar -browserSessionReuse
11:51:38.614 INFO - Java: Sun Microsystems Inc. 10.0-b23
11:51:38.614 INFO - OS: Windows XP 5.1 x86
11:51:38.614 INFO - v1.0.1 [2696], with Core v@VERSION@ [@REVISION@]
11:51:38.614 INFO - Will recycle browser sessions when possible.
11:51:38.755 INFO - Version Jetty/5.1.x
11:51:38.755 INFO - Started HttpContext[/selenium-server/driver,/selenium-server
/driver]
11:51:38.755 INFO - Started HttpContext[/selenium-server,/selenium-server]
11:51:38.755 INFO - Started HttpContext[/,/]
11:51:38.771 INFO - Started SocketListener on 0.0.0.0:4444
11:51:38.771 INFO - Started org.mortbay.jetty.Server@1e0cf70
11:54:55.060 INFO - Checking Resource aliases
11:54:55.075 INFO - Command request: getNewBrowserSession[*chrome, http://joomla
] on session null
11:54:55.075 INFO - grabbing available session...
11:54:55.075 INFO - creating new remote session
11:54:55.544 INFO - Allocated session df59775d37ca4e77bbdb4d0f7b97d63c for http:
//joomla, launching...
11:54:55.794 INFO - Preparing Firefox profile...
11:55:19.052 ERROR - Failed to start new browser session, shutdown browser and c
lear all session data
java.lang.RuntimeException: Firefox refused shutdown while preparing a profile
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:311)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.pop
ulateCustomProfileDirectory(FirefoxChromeLauncher.java:106)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nch(FirefoxChromeLauncher.java:83)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nchRemoteSession(FirefoxChromeLauncher.java:350)
at org.openqa.selenium.server.BrowserSessionFactory.createNewRemoteSessi
on(BrowserSessionFactory.java:357)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
( BrowserSessionFactory.java:122)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
(BrowserSessionFactory.java:84)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.getNewBrowse
rSession(SeleniumDriverResourceHandler.java:699)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.doCommand(Se
leniumDriverResourceHandler.java:393)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handleComman
dRequest(SeleniumDriverResourceHandler.java:364)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handle(Selen
iumDriverResourceHandler.java:125)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
at org.mortbay.http.HttpServer.service(HttpServer.java:909)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:820)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:
245)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
Caused by: org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher$Fil
eLockRemainedException: Lock file still present! C:\DOKUME~1\fpolyak\LOKALE~1\Te
mp\customProfileDirdf59775d37ca4e77bbdb4d0f7b97d63c\parent.lock
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFileLockToGoAway(FirefoxChromeLauncher.java:269)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:309)
... 19 more
11:55:31.806 INFO - Got result: Failed to start new browser session: Unable to d
elete file C:\DOKUME~1\fpolyak\LOKALE~1\Temp\customProfileDirdf59775d37ca4e77bbd
b4d0f7b97d63c\parent.lock on session null
11:55:31.884 INFO - Command request: getNewBrowserSession[*chrome, http://joomla
] on session null
11:55:31.884 INFO - grabbing available session...
11:55:31.884 INFO - creating new remote session
11:55:31.884 INFO - Allocated session e782589f459f4d9c8c0164e05c1f8cf6 for http:
//joomla, launching...
11:55:32.040 INFO - Preparing Firefox profile...
11:55:53.719 ERROR - Failed to start new browser session, shutdown browser and c
lear all session data
java.lang.RuntimeException: Firefox refused shutdown while preparing a profile
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:311)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.pop
ulateCustomProfileDirectory(FirefoxChromeLauncher.java:106)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nch(FirefoxChromeLauncher.java:83)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nchRemoteSession(FirefoxChromeLauncher.java:350)
at org.openqa.selenium.server.BrowserSessionFactory.createNewRemoteSessi
on(BrowserSessionFactory.java:357)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
(BrowserSessionFactory.java:122)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
(BrowserSessionFactory.java:84)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.getNewBrowse
rSession(SeleniumDriverResourceHandler.java:699)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.doCommand(Se
leniumDriverResourceHandler.java:393)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handleComman
dRequest(SeleniumDriverResourceHandler.java:364)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handle(Selen
iumDriverResourceHandler.java:125)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
at org.mortbay.http.HttpServer.service(HttpServer.java:909)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:820)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837)
at org.mortbay.http.SocketListener.handleConnection(SocketListener .java:
245)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
Caused by: org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher$Fil
eLockRemainedException: Lock file still present! C:\DOKUME~1\fpolyak\LOKALE~1\Te
mp\customProfileDire782589f459f4d9c8c0164e05c1f8cf6\parent.lock
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFileLockToGoAway(FirefoxChromeLauncher.java:269)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:309)
... 19 more
11:56:06.379 INFO - Got result: Failed to start new browser session: Unable to d
elete file C:\DOKUME~1\fpolyak\LOKALE~1\Temp\customProfileDire782589f459f4d9c8c0
164e05c1f8cf6\parent.lock on session null

-----

configdef.php:

class SeleniumConfig { var $host = 'http://joomla';
var $path = '';#'/j1513/';
var $username = 'admin';
var $password = 'admin';
var $browser = '*chrome';
var $baseURI = "c:/xampp/htdocs/joomla/";}

-----

Can anybody help me please?

Thanks

This might help: [http://clearspace.openqa.org/thread/15596 http://clearspace.openqa.org/thread/15596] [[User:Dextercowley|Mark Dexter]]

Talk:Running Automated Tests for the Joomla CMS

2010-06-30T07:16:40Z

PtrNrs: /* Re: Run the System Test Suite */

== Re: Run the System Test Suite ==
I am trying to run the system test suite in the normal SVN configuration with the installation folder still present. TestSuite calls doInstall which reruns the Joomla install and then reinstalls the sample data which, by the way, failed due to a bug (http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=21250).

When I rename (or delete) the installation folder, TestSuite runs OK.

The first tip says
* 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.
This seems to indicate that we shouldn't have the installation folder, as its presence will cause the sample data to be reinstalled anyway. Remember that an SVN update will reinstate the installation folder anyway.

What is the required configuration is for running TestSuite?

== Create a Selenium Configuration File ==

Would var $baseURI of in be the same as public $live_site?

It could be, but we don't have access to Joomla! variables when running the tests. We are running them from a browser, outside the Joomla! framework. [[User:Dextercowley|Mark Dexter]] 22:01, 6 February 2010 (UTC)

== Run the Test Suite ==
Where is / how do we create phpunit.bat?

phpunit.bat is created when you install PHPUnit (in Windows). In Linux I would guess that it is just phpunit. [[User:Dextercowley|Mark Dexter]] 22:02, 6 February 2010 (UTC)

== Failed to start new browser session, shutdown browser and ==
clear all session data... Lock file still present!

Hi All,

I installed all, how it is written on [[Running_Automated_Tests_for_Version_1.6]], i see my Firefox(3.6, WinXPSP3)-processes(new) in the taskbar started, but the second browser window was not opened! After that I see another try the FF to start, without success and so on.

----
Start of Tests:

C:\Dokumente und Einstellungen\fpolyak>cd c:\xampp\htdocs\joomla\tests\system\
C:\xampp\htdocs\joomla\tests\system>c:\xampp\php\phpunit.bat --bootstrap servers
\configdef.php suite\TestSuite.php
PHPUnit 3.4.10 by Sebastian Bergmann.
Starting ControlPanelMenu.
E^CBatchvorgang abbrechen (J/N)? j
C:\xampp\htdocs\joomla\tests\system>

----
Selenium messages (with errors messages) :

C:\selenium\selenium-remote-control-1.0.1>c:\Programme\Java\jre1.6.0_07\bin\java
.exe -jar selenium-server-1.0.1\selenium-server.jar -browserSessionReuse
11:51:38.614 INFO - Java: Sun Microsystems Inc. 10.0-b23
11:51:38.614 INFO - OS: Windows XP 5.1 x86
11:51:38.614 INFO - v1.0.1 [2696], with Core v@VERSION@ [@REVISION@]
11:51:38.614 INFO - Will recycle browser sessions when possible.
11:51:38.755 INFO - Version Jetty/5.1.x
11:51:38.755 INFO - Started HttpContext[/selenium-server/driver,/selenium-server
/driver]
11:51:38.755 INFO - Started HttpContext[/selenium-server,/selenium-server]
11:51:38.755 INFO - Started HttpContext[/,/]
11:51:38.771 INFO - Started SocketListener on 0.0.0.0:4444
11:51:38.771 INFO - Started org.mortbay.jetty.Server@1e0cf70
11:54:55.060 INFO - Checking Resource aliases
11:54:55.075 INFO - Command request: getNewBrowserSession[*chrome, http://joomla
] on session null
11:54:55.075 INFO - grabbing available session...
11:54:55.075 INFO - creating new remote session
11:54:55.544 INFO - Allocated session df59775d37ca4e77bbdb4d0f7b97d63c for http:
//joomla, launching...
11:54:55.794 INFO - Preparing Firefox profile...
11:55:19.052 ERROR - Failed to start new browser session, shutdown browser and c
lear all session data
java.lang.RuntimeException: Firefox refused shutdown while preparing a profile
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:311)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.pop
ulateCustomProfileDirectory(FirefoxChromeLauncher.java:106)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nch(FirefoxChromeLauncher.java:83)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nchRemoteSession(FirefoxChromeLauncher.java:350)
at org.openqa.selenium.server.BrowserSessionFactory.createNewRemoteSessi
on(BrowserSessionFactory.java:357)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
( BrowserSessionFactory.java:122)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
(BrowserSessionFactory.java:84)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.getNewBrowse
rSession(SeleniumDriverResourceHandler.java:699)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.doCommand(Se
leniumDriverResourceHandler.java:393)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handleComman
dRequest(SeleniumDriverResourceHandler.java:364)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handle(Selen
iumDriverResourceHandler.java:125)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
at org.mortbay.http.HttpServer.service(HttpServer.java:909)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:820)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:
245)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
Caused by: org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher$Fil
eLockRemainedException: Lock file still present! C:\DOKUME~1\fpolyak\LOKALE~1\Te
mp\customProfileDirdf59775d37ca4e77bbdb4d0f7b97d63c\parent.lock
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFileLockToGoAway(FirefoxChromeLauncher.java:269)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:309)
... 19 more
11:55:31.806 INFO - Got result: Failed to start new browser session: Unable to d
elete file C:\DOKUME~1\fpolyak\LOKALE~1\Temp\customProfileDirdf59775d37ca4e77bbd
b4d0f7b97d63c\parent.lock on session null
11:55:31.884 INFO - Command request: getNewBrowserSession[*chrome, http://joomla
] on session null
11:55:31.884 INFO - grabbing available session...
11:55:31.884 INFO - creating new remote session
11:55:31.884 INFO - Allocated session e782589f459f4d9c8c0164e05c1f8cf6 for http:
//joomla, launching...
11:55:32.040 INFO - Preparing Firefox profile...
11:55:53.719 ERROR - Failed to start new browser session, shutdown browser and c
lear all session data
java.lang.RuntimeException: Firefox refused shutdown while preparing a profile
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:311)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.pop
ulateCustomProfileDirectory(FirefoxChromeLauncher.java:106)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nch(FirefoxChromeLauncher.java:83)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nchRemoteSession(FirefoxChromeLauncher.java:350)
at org.openqa.selenium.server.BrowserSessionFactory.createNewRemoteSessi
on(BrowserSessionFactory.java:357)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
(BrowserSessionFactory.java:122)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
(BrowserSessionFactory.java:84)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.getNewBrowse
rSession(SeleniumDriverResourceHandler.java:699)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.doCommand(Se
leniumDriverResourceHandler.java:393)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handleComman
dRequest(SeleniumDriverResourceHandler.java:364)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handle(Selen
iumDriverResourceHandler.java:125)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
at org.mortbay.http.HttpServer.service(HttpServer.java:909)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:820)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837)
at org.mortbay.http.SocketListener.handleConnection(SocketListener .java:
245)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
Caused by: org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher$Fil
eLockRemainedException: Lock file still present! C:\DOKUME~1\fpolyak\LOKALE~1\Te
mp\customProfileDire782589f459f4d9c8c0164e05c1f8cf6\parent.lock
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFileLockToGoAway(FirefoxChromeLauncher.java:269)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:309)
... 19 more
11:56:06.379 INFO - Got result: Failed to start new browser session: Unable to d
elete file C:\DOKUME~1\fpolyak\LOKALE~1\Temp\customProfileDire782589f459f4d9c8c0
164e05c1f8cf6\parent.lock on session null

-----

configdef.php:

class SeleniumConfig { var $host = 'http://joomla';
var $path = '';#'/j1513/';
var $username = 'admin';
var $password = 'admin';
var $browser = '*chrome';
var $baseURI = "c:/xampp/htdocs/joomla/";}

-----

Can anybody help me please?

Thanks

This might help: [http://clearspace.openqa.org/thread/15596 http://clearspace.openqa.org/thread/15596] [[User:Dextercowley|Mark Dexter]]

Talk:Running Automated Tests for the Joomla CMS

2010-06-30T07:08:14Z

PtrNrs: /* Re: Run the System Test Suite */

== Re: Run the System Test Suite ==
I am trying to run the system test suite in the normal SVN configuration with the installation folder still present. TestSuite calls doInstall which reruns the Joomla install and then reinstalls the sample data which, by the way, failed due to a bug (http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=21250).

When I rename (or delete) the installation folder, TestSuite runs OK.

The first tip says
* 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.
This seems to indicate that we shouldn't have the installation folder, as its presence will cause the sample data to be reinstalled anyway.

Could someone please clarify this.

== Create a Selenium Configuration File ==

Would var $baseURI of in be the same as public $live_site?

It could be, but we don't have access to Joomla! variables when running the tests. We are running them from a browser, outside the Joomla! framework. [[User:Dextercowley|Mark Dexter]] 22:01, 6 February 2010 (UTC)

== Run the Test Suite ==
Where is / how do we create phpunit.bat?

phpunit.bat is created when you install PHPUnit (in Windows). In Linux I would guess that it is just phpunit. [[User:Dextercowley|Mark Dexter]] 22:02, 6 February 2010 (UTC)

== Failed to start new browser session, shutdown browser and ==
clear all session data... Lock file still present!

Hi All,

I installed all, how it is written on [[Running_Automated_Tests_for_Version_1.6]], i see my Firefox(3.6, WinXPSP3)-processes(new) in the taskbar started, but the second browser window was not opened! After that I see another try the FF to start, without success and so on.

----
Start of Tests:

C:\Dokumente und Einstellungen\fpolyak>cd c:\xampp\htdocs\joomla\tests\system\
C:\xampp\htdocs\joomla\tests\system>c:\xampp\php\phpunit.bat --bootstrap servers
\configdef.php suite\TestSuite.php
PHPUnit 3.4.10 by Sebastian Bergmann.
Starting ControlPanelMenu.
E^CBatchvorgang abbrechen (J/N)? j
C:\xampp\htdocs\joomla\tests\system>

----
Selenium messages (with errors messages) :

C:\selenium\selenium-remote-control-1.0.1>c:\Programme\Java\jre1.6.0_07\bin\java
.exe -jar selenium-server-1.0.1\selenium-server.jar -browserSessionReuse
11:51:38.614 INFO - Java: Sun Microsystems Inc. 10.0-b23
11:51:38.614 INFO - OS: Windows XP 5.1 x86
11:51:38.614 INFO - v1.0.1 [2696], with Core v@VERSION@ [@REVISION@]
11:51:38.614 INFO - Will recycle browser sessions when possible.
11:51:38.755 INFO - Version Jetty/5.1.x
11:51:38.755 INFO - Started HttpContext[/selenium-server/driver,/selenium-server
/driver]
11:51:38.755 INFO - Started HttpContext[/selenium-server,/selenium-server]
11:51:38.755 INFO - Started HttpContext[/,/]
11:51:38.771 INFO - Started SocketListener on 0.0.0.0:4444
11:51:38.771 INFO - Started org.mortbay.jetty.Server@1e0cf70
11:54:55.060 INFO - Checking Resource aliases
11:54:55.075 INFO - Command request: getNewBrowserSession[*chrome, http://joomla
] on session null
11:54:55.075 INFO - grabbing available session...
11:54:55.075 INFO - creating new remote session
11:54:55.544 INFO - Allocated session df59775d37ca4e77bbdb4d0f7b97d63c for http:
//joomla, launching...
11:54:55.794 INFO - Preparing Firefox profile...
11:55:19.052 ERROR - Failed to start new browser session, shutdown browser and c
lear all session data
java.lang.RuntimeException: Firefox refused shutdown while preparing a profile
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:311)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.pop
ulateCustomProfileDirectory(FirefoxChromeLauncher.java:106)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nch(FirefoxChromeLauncher.java:83)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nchRemoteSession(FirefoxChromeLauncher.java:350)
at org.openqa.selenium.server.BrowserSessionFactory.createNewRemoteSessi
on(BrowserSessionFactory.java:357)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
( BrowserSessionFactory.java:122)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
(BrowserSessionFactory.java:84)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.getNewBrowse
rSession(SeleniumDriverResourceHandler.java:699)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.doCommand(Se
leniumDriverResourceHandler.java:393)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handleComman
dRequest(SeleniumDriverResourceHandler.java:364)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handle(Selen
iumDriverResourceHandler.java:125)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
at org.mortbay.http.HttpServer.service(HttpServer.java:909)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:820)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:
245)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
Caused by: org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher$Fil
eLockRemainedException: Lock file still present! C:\DOKUME~1\fpolyak\LOKALE~1\Te
mp\customProfileDirdf59775d37ca4e77bbdb4d0f7b97d63c\parent.lock
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFileLockToGoAway(FirefoxChromeLauncher.java:269)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:309)
... 19 more
11:55:31.806 INFO - Got result: Failed to start new browser session: Unable to d
elete file C:\DOKUME~1\fpolyak\LOKALE~1\Temp\customProfileDirdf59775d37ca4e77bbd
b4d0f7b97d63c\parent.lock on session null
11:55:31.884 INFO - Command request: getNewBrowserSession[*chrome, http://joomla
] on session null
11:55:31.884 INFO - grabbing available session...
11:55:31.884 INFO - creating new remote session
11:55:31.884 INFO - Allocated session e782589f459f4d9c8c0164e05c1f8cf6 for http:
//joomla, launching...
11:55:32.040 INFO - Preparing Firefox profile...
11:55:53.719 ERROR - Failed to start new browser session, shutdown browser and c
lear all session data
java.lang.RuntimeException: Firefox refused shutdown while preparing a profile
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:311)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.pop
ulateCustomProfileDirectory(FirefoxChromeLauncher.java:106)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nch(FirefoxChromeLauncher.java:83)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nchRemoteSession(FirefoxChromeLauncher.java:350)
at org.openqa.selenium.server.BrowserSessionFactory.createNewRemoteSessi
on(BrowserSessionFactory.java:357)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
(BrowserSessionFactory.java:122)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
(BrowserSessionFactory.java:84)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.getNewBrowse
rSession(SeleniumDriverResourceHandler.java:699)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.doCommand(Se
leniumDriverResourceHandler.java:393)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handleComman
dRequest(SeleniumDriverResourceHandler.java:364)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handle(Selen
iumDriverResourceHandler.java:125)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
at org.mortbay.http.HttpServer.service(HttpServer.java:909)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:820)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837)
at org.mortbay.http.SocketListener.handleConnection(SocketListener .java:
245)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
Caused by: org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher$Fil
eLockRemainedException: Lock file still present! C:\DOKUME~1\fpolyak\LOKALE~1\Te
mp\customProfileDire782589f459f4d9c8c0164e05c1f8cf6\parent.lock
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFileLockToGoAway(FirefoxChromeLauncher.java:269)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:309)
... 19 more
11:56:06.379 INFO - Got result: Failed to start new browser session: Unable to d
elete file C:\DOKUME~1\fpolyak\LOKALE~1\Temp\customProfileDire782589f459f4d9c8c0
164e05c1f8cf6\parent.lock on session null

-----

configdef.php:

class SeleniumConfig { var $host = 'http://joomla';
var $path = '';#'/j1513/';
var $username = 'admin';
var $password = 'admin';
var $browser = '*chrome';
var $baseURI = "c:/xampp/htdocs/joomla/";}

-----

Can anybody help me please?

Thanks

This might help: [http://clearspace.openqa.org/thread/15596 http://clearspace.openqa.org/thread/15596] [[User:Dextercowley|Mark Dexter]]

Talk:Running Automated Tests for the Joomla CMS

2010-06-30T06:58:26Z

PtrNrs: /* Re: Run the System Test Suite */

== Re: Run the System Test Suite ==
I am trying to run the system test suite in the normal SVN configuration with the installation folder still present. TestSuite calls doInstall which reruns the Joomla install and then reinstalls the sample data. This, by the way, failed due to a bug (http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=21250).

When I rename (or delete) the installation folder, TestSuite runs OK.

The first tip says
* 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.
This seems to indicate that we shouldn't have the installation folder, as its presence will cause the sample data to be reinstalled anyway.

Could someone please clarify this.

== Create a Selenium Configuration File ==

Would var $baseURI of in be the same as public $live_site?

It could be, but we don't have access to Joomla! variables when running the tests. We are running them from a browser, outside the Joomla! framework. [[User:Dextercowley|Mark Dexter]] 22:01, 6 February 2010 (UTC)

== Run the Test Suite ==
Where is / how do we create phpunit.bat?

phpunit.bat is created when you install PHPUnit (in Windows). In Linux I would guess that it is just phpunit. [[User:Dextercowley|Mark Dexter]] 22:02, 6 February 2010 (UTC)

== Failed to start new browser session, shutdown browser and ==
clear all session data... Lock file still present!

Hi All,

I installed all, how it is written on [[Running_Automated_Tests_for_Version_1.6]], i see my Firefox(3.6, WinXPSP3)-processes(new) in the taskbar started, but the second browser window was not opened! After that I see another try the FF to start, without success and so on.

----
Start of Tests:

C:\Dokumente und Einstellungen\fpolyak>cd c:\xampp\htdocs\joomla\tests\system\
C:\xampp\htdocs\joomla\tests\system>c:\xampp\php\phpunit.bat --bootstrap servers
\configdef.php suite\TestSuite.php
PHPUnit 3.4.10 by Sebastian Bergmann.
Starting ControlPanelMenu.
E^CBatchvorgang abbrechen (J/N)? j
C:\xampp\htdocs\joomla\tests\system>

----
Selenium messages (with errors messages) :

C:\selenium\selenium-remote-control-1.0.1>c:\Programme\Java\jre1.6.0_07\bin\java
.exe -jar selenium-server-1.0.1\selenium-server.jar -browserSessionReuse
11:51:38.614 INFO - Java: Sun Microsystems Inc. 10.0-b23
11:51:38.614 INFO - OS: Windows XP 5.1 x86
11:51:38.614 INFO - v1.0.1 [2696], with Core v@VERSION@ [@REVISION@]
11:51:38.614 INFO - Will recycle browser sessions when possible.
11:51:38.755 INFO - Version Jetty/5.1.x
11:51:38.755 INFO - Started HttpContext[/selenium-server/driver,/selenium-server
/driver]
11:51:38.755 INFO - Started HttpContext[/selenium-server,/selenium-server]
11:51:38.755 INFO - Started HttpContext[/,/]
11:51:38.771 INFO - Started SocketListener on 0.0.0.0:4444
11:51:38.771 INFO - Started org.mortbay.jetty.Server@1e0cf70
11:54:55.060 INFO - Checking Resource aliases
11:54:55.075 INFO - Command request: getNewBrowserSession[*chrome, http://joomla
] on session null
11:54:55.075 INFO - grabbing available session...
11:54:55.075 INFO - creating new remote session
11:54:55.544 INFO - Allocated session df59775d37ca4e77bbdb4d0f7b97d63c for http:
//joomla, launching...
11:54:55.794 INFO - Preparing Firefox profile...
11:55:19.052 ERROR - Failed to start new browser session, shutdown browser and c
lear all session data
java.lang.RuntimeException: Firefox refused shutdown while preparing a profile
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:311)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.pop
ulateCustomProfileDirectory(FirefoxChromeLauncher.java:106)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nch(FirefoxChromeLauncher.java:83)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nchRemoteSession(FirefoxChromeLauncher.java:350)
at org.openqa.selenium.server.BrowserSessionFactory.createNewRemoteSessi
on(BrowserSessionFactory.java:357)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
( BrowserSessionFactory.java:122)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
(BrowserSessionFactory.java:84)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.getNewBrowse
rSession(SeleniumDriverResourceHandler.java:699)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.doCommand(Se
leniumDriverResourceHandler.java:393)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handleComman
dRequest(SeleniumDriverResourceHandler.java:364)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handle(Selen
iumDriverResourceHandler.java:125)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
at org.mortbay.http.HttpServer.service(HttpServer.java:909)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:820)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:
245)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
Caused by: org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher$Fil
eLockRemainedException: Lock file still present! C:\DOKUME~1\fpolyak\LOKALE~1\Te
mp\customProfileDirdf59775d37ca4e77bbdb4d0f7b97d63c\parent.lock
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFileLockToGoAway(FirefoxChromeLauncher.java:269)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:309)
... 19 more
11:55:31.806 INFO - Got result: Failed to start new browser session: Unable to d
elete file C:\DOKUME~1\fpolyak\LOKALE~1\Temp\customProfileDirdf59775d37ca4e77bbd
b4d0f7b97d63c\parent.lock on session null
11:55:31.884 INFO - Command request: getNewBrowserSession[*chrome, http://joomla
] on session null
11:55:31.884 INFO - grabbing available session...
11:55:31.884 INFO - creating new remote session
11:55:31.884 INFO - Allocated session e782589f459f4d9c8c0164e05c1f8cf6 for http:
//joomla, launching...
11:55:32.040 INFO - Preparing Firefox profile...
11:55:53.719 ERROR - Failed to start new browser session, shutdown browser and c
lear all session data
java.lang.RuntimeException: Firefox refused shutdown while preparing a profile
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:311)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.pop
ulateCustomProfileDirectory(FirefoxChromeLauncher.java:106)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nch(FirefoxChromeLauncher.java:83)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nchRemoteSession(FirefoxChromeLauncher.java:350)
at org.openqa.selenium.server.BrowserSessionFactory.createNewRemoteSessi
on(BrowserSessionFactory.java:357)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
(BrowserSessionFactory.java:122)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
(BrowserSessionFactory.java:84)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.getNewBrowse
rSession(SeleniumDriverResourceHandler.java:699)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.doCommand(Se
leniumDriverResourceHandler.java:393)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handleComman
dRequest(SeleniumDriverResourceHandler.java:364)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handle(Selen
iumDriverResourceHandler.java:125)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
at org.mortbay.http.HttpServer.service(HttpServer.java:909)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:820)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837)
at org.mortbay.http.SocketListener.handleConnection(SocketListener .java:
245)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
Caused by: org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher$Fil
eLockRemainedException: Lock file still present! C:\DOKUME~1\fpolyak\LOKALE~1\Te
mp\customProfileDire782589f459f4d9c8c0164e05c1f8cf6\parent.lock
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFileLockToGoAway(FirefoxChromeLauncher.java:269)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:309)
... 19 more
11:56:06.379 INFO - Got result: Failed to start new browser session: Unable to d
elete file C:\DOKUME~1\fpolyak\LOKALE~1\Temp\customProfileDire782589f459f4d9c8c0
164e05c1f8cf6\parent.lock on session null

-----

configdef.php:

class SeleniumConfig { var $host = 'http://joomla';
var $path = '';#'/j1513/';
var $username = 'admin';
var $password = 'admin';
var $browser = '*chrome';
var $baseURI = "c:/xampp/htdocs/joomla/";}

-----

Can anybody help me please?

Thanks

This might help: [http://clearspace.openqa.org/thread/15596 http://clearspace.openqa.org/thread/15596] [[User:Dextercowley|Mark Dexter]]

Talk:Running Automated Tests for the Joomla CMS

2010-06-30T06:57:42Z

PtrNrs: /* Re: Run the System Test Suite */

== Re: Run the System Test Suite ==
I am trying to run the system test suite in the normal SVN configuration with the installation folder still present. TestSuite calls doInstall which reruns the Joomla install and then reinstalls the sample data. This, by the way, failed due to a bug (http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=21250).

When I rename (or delete) the installation folder, TestSuite runs OK.

The first tip says
* 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.
This seems to indicate that we shouldn't have the installation folder, as its presence will cause the sample data to be reinstalled anyway.

Could someone please clarify this

== Create a Selenium Configuration File ==

Would var $baseURI of in be the same as public $live_site?

It could be, but we don't have access to Joomla! variables when running the tests. We are running them from a browser, outside the Joomla! framework. [[User:Dextercowley|Mark Dexter]] 22:01, 6 February 2010 (UTC)

== Run the Test Suite ==
Where is / how do we create phpunit.bat?

phpunit.bat is created when you install PHPUnit (in Windows). In Linux I would guess that it is just phpunit. [[User:Dextercowley|Mark Dexter]] 22:02, 6 February 2010 (UTC)

== Failed to start new browser session, shutdown browser and ==
clear all session data... Lock file still present!

Hi All,

I installed all, how it is written on [[Running_Automated_Tests_for_Version_1.6]], i see my Firefox(3.6, WinXPSP3)-processes(new) in the taskbar started, but the second browser window was not opened! After that I see another try the FF to start, without success and so on.

----
Start of Tests:

C:\Dokumente und Einstellungen\fpolyak>cd c:\xampp\htdocs\joomla\tests\system\
C:\xampp\htdocs\joomla\tests\system>c:\xampp\php\phpunit.bat --bootstrap servers
\configdef.php suite\TestSuite.php
PHPUnit 3.4.10 by Sebastian Bergmann.
Starting ControlPanelMenu.
E^CBatchvorgang abbrechen (J/N)? j
C:\xampp\htdocs\joomla\tests\system>

----
Selenium messages (with errors messages) :

C:\selenium\selenium-remote-control-1.0.1>c:\Programme\Java\jre1.6.0_07\bin\java
.exe -jar selenium-server-1.0.1\selenium-server.jar -browserSessionReuse
11:51:38.614 INFO - Java: Sun Microsystems Inc. 10.0-b23
11:51:38.614 INFO - OS: Windows XP 5.1 x86
11:51:38.614 INFO - v1.0.1 [2696], with Core v@VERSION@ [@REVISION@]
11:51:38.614 INFO - Will recycle browser sessions when possible.
11:51:38.755 INFO - Version Jetty/5.1.x
11:51:38.755 INFO - Started HttpContext[/selenium-server/driver,/selenium-server
/driver]
11:51:38.755 INFO - Started HttpContext[/selenium-server,/selenium-server]
11:51:38.755 INFO - Started HttpContext[/,/]
11:51:38.771 INFO - Started SocketListener on 0.0.0.0:4444
11:51:38.771 INFO - Started org.mortbay.jetty.Server@1e0cf70
11:54:55.060 INFO - Checking Resource aliases
11:54:55.075 INFO - Command request: getNewBrowserSession[*chrome, http://joomla
] on session null
11:54:55.075 INFO - grabbing available session...
11:54:55.075 INFO - creating new remote session
11:54:55.544 INFO - Allocated session df59775d37ca4e77bbdb4d0f7b97d63c for http:
//joomla, launching...
11:54:55.794 INFO - Preparing Firefox profile...
11:55:19.052 ERROR - Failed to start new browser session, shutdown browser and c
lear all session data
java.lang.RuntimeException: Firefox refused shutdown while preparing a profile
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:311)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.pop
ulateCustomProfileDirectory(FirefoxChromeLauncher.java:106)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nch(FirefoxChromeLauncher.java:83)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nchRemoteSession(FirefoxChromeLauncher.java:350)
at org.openqa.selenium.server.BrowserSessionFactory.createNewRemoteSessi
on(BrowserSessionFactory.java:357)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
( BrowserSessionFactory.java:122)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
(BrowserSessionFactory.java:84)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.getNewBrowse
rSession(SeleniumDriverResourceHandler.java:699)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.doCommand(Se
leniumDriverResourceHandler.java:393)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handleComman
dRequest(SeleniumDriverResourceHandler.java:364)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handle(Selen
iumDriverResourceHandler.java:125)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
at org.mortbay.http.HttpServer.service(HttpServer.java:909)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:820)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:
245)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
Caused by: org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher$Fil
eLockRemainedException: Lock file still present! C:\DOKUME~1\fpolyak\LOKALE~1\Te
mp\customProfileDirdf59775d37ca4e77bbdb4d0f7b97d63c\parent.lock
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFileLockToGoAway(FirefoxChromeLauncher.java:269)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:309)
... 19 more
11:55:31.806 INFO - Got result: Failed to start new browser session: Unable to d
elete file C:\DOKUME~1\fpolyak\LOKALE~1\Temp\customProfileDirdf59775d37ca4e77bbd
b4d0f7b97d63c\parent.lock on session null
11:55:31.884 INFO - Command request: getNewBrowserSession[*chrome, http://joomla
] on session null
11:55:31.884 INFO - grabbing available session...
11:55:31.884 INFO - creating new remote session
11:55:31.884 INFO - Allocated session e782589f459f4d9c8c0164e05c1f8cf6 for http:
//joomla, launching...
11:55:32.040 INFO - Preparing Firefox profile...
11:55:53.719 ERROR - Failed to start new browser session, shutdown browser and c
lear all session data
java.lang.RuntimeException: Firefox refused shutdown while preparing a profile
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:311)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.pop
ulateCustomProfileDirectory(FirefoxChromeLauncher.java:106)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nch(FirefoxChromeLauncher.java:83)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nchRemoteSession(FirefoxChromeLauncher.java:350)
at org.openqa.selenium.server.BrowserSessionFactory.createNewRemoteSessi
on(BrowserSessionFactory.java:357)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
(BrowserSessionFactory.java:122)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
(BrowserSessionFactory.java:84)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.getNewBrowse
rSession(SeleniumDriverResourceHandler.java:699)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.doCommand(Se
leniumDriverResourceHandler.java:393)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handleComman
dRequest(SeleniumDriverResourceHandler.java:364)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handle(Selen
iumDriverResourceHandler.java:125)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
at org.mortbay.http.HttpServer.service(HttpServer.java:909)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:820)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837)
at org.mortbay.http.SocketListener.handleConnection(SocketListener .java:
245)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
Caused by: org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher$Fil
eLockRemainedException: Lock file still present! C:\DOKUME~1\fpolyak\LOKALE~1\Te
mp\customProfileDire782589f459f4d9c8c0164e05c1f8cf6\parent.lock
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFileLockToGoAway(FirefoxChromeLauncher.java:269)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:309)
... 19 more
11:56:06.379 INFO - Got result: Failed to start new browser session: Unable to d
elete file C:\DOKUME~1\fpolyak\LOKALE~1\Temp\customProfileDire782589f459f4d9c8c0
164e05c1f8cf6\parent.lock on session null

-----

configdef.php:

class SeleniumConfig { var $host = 'http://joomla';
var $path = '';#'/j1513/';
var $username = 'admin';
var $password = 'admin';
var $browser = '*chrome';
var $baseURI = "c:/xampp/htdocs/joomla/";}

-----

Can anybody help me please?

Thanks

This might help: [http://clearspace.openqa.org/thread/15596 http://clearspace.openqa.org/thread/15596] [[User:Dextercowley|Mark Dexter]]

Talk:Running Automated Tests for the Joomla CMS

2010-06-30T06:57:07Z

PtrNrs:

== Re: Run the System Test Suite ==
I am trying to run the system test suite in the normal SVN configuration with the installation folder still present. TestSuite calls doInstall which reruns the Joomla install and then reinstalls the sample data. This, by the way, failed due to a bug (http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=21250).

When I rename (or delete) the installation folder, TestSuite runs OK.

The first tip says
* 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.
This seems to indicate that we shouldn't have the installation folder, as it's presence will cause the sample data to be reinstalled anyway.

Could someone please clarify this

== Create a Selenium Configuration File ==

Would var $baseURI of in be the same as public $live_site?

It could be, but we don't have access to Joomla! variables when running the tests. We are running them from a browser, outside the Joomla! framework. [[User:Dextercowley|Mark Dexter]] 22:01, 6 February 2010 (UTC)

== Run the Test Suite ==
Where is / how do we create phpunit.bat?

phpunit.bat is created when you install PHPUnit (in Windows). In Linux I would guess that it is just phpunit. [[User:Dextercowley|Mark Dexter]] 22:02, 6 February 2010 (UTC)

== Failed to start new browser session, shutdown browser and ==
clear all session data... Lock file still present!

Hi All,

I installed all, how it is written on [[Running_Automated_Tests_for_Version_1.6]], i see my Firefox(3.6, WinXPSP3)-processes(new) in the taskbar started, but the second browser window was not opened! After that I see another try the FF to start, without success and so on.

----
Start of Tests:

C:\Dokumente und Einstellungen\fpolyak>cd c:\xampp\htdocs\joomla\tests\system\
C:\xampp\htdocs\joomla\tests\system>c:\xampp\php\phpunit.bat --bootstrap servers
\configdef.php suite\TestSuite.php
PHPUnit 3.4.10 by Sebastian Bergmann.
Starting ControlPanelMenu.
E^CBatchvorgang abbrechen (J/N)? j
C:\xampp\htdocs\joomla\tests\system>

----
Selenium messages (with errors messages) :

C:\selenium\selenium-remote-control-1.0.1>c:\Programme\Java\jre1.6.0_07\bin\java
.exe -jar selenium-server-1.0.1\selenium-server.jar -browserSessionReuse
11:51:38.614 INFO - Java: Sun Microsystems Inc. 10.0-b23
11:51:38.614 INFO - OS: Windows XP 5.1 x86
11:51:38.614 INFO - v1.0.1 [2696], with Core v@VERSION@ [@REVISION@]
11:51:38.614 INFO - Will recycle browser sessions when possible.
11:51:38.755 INFO - Version Jetty/5.1.x
11:51:38.755 INFO - Started HttpContext[/selenium-server/driver,/selenium-server
/driver]
11:51:38.755 INFO - Started HttpContext[/selenium-server,/selenium-server]
11:51:38.755 INFO - Started HttpContext[/,/]
11:51:38.771 INFO - Started SocketListener on 0.0.0.0:4444
11:51:38.771 INFO - Started org.mortbay.jetty.Server@1e0cf70
11:54:55.060 INFO - Checking Resource aliases
11:54:55.075 INFO - Command request: getNewBrowserSession[*chrome, http://joomla
] on session null
11:54:55.075 INFO - grabbing available session...
11:54:55.075 INFO - creating new remote session
11:54:55.544 INFO - Allocated session df59775d37ca4e77bbdb4d0f7b97d63c for http:
//joomla, launching...
11:54:55.794 INFO - Preparing Firefox profile...
11:55:19.052 ERROR - Failed to start new browser session, shutdown browser and c
lear all session data
java.lang.RuntimeException: Firefox refused shutdown while preparing a profile
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:311)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.pop
ulateCustomProfileDirectory(FirefoxChromeLauncher.java:106)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nch(FirefoxChromeLauncher.java:83)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nchRemoteSession(FirefoxChromeLauncher.java:350)
at org.openqa.selenium.server.BrowserSessionFactory.createNewRemoteSessi
on(BrowserSessionFactory.java:357)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
( BrowserSessionFactory.java:122)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
(BrowserSessionFactory.java:84)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.getNewBrowse
rSession(SeleniumDriverResourceHandler.java:699)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.doCommand(Se
leniumDriverResourceHandler.java:393)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handleComman
dRequest(SeleniumDriverResourceHandler.java:364)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handle(Selen
iumDriverResourceHandler.java:125)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
at org.mortbay.http.HttpServer.service(HttpServer.java:909)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:820)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:
245)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
Caused by: org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher$Fil
eLockRemainedException: Lock file still present! C:\DOKUME~1\fpolyak\LOKALE~1\Te
mp\customProfileDirdf59775d37ca4e77bbdb4d0f7b97d63c\parent.lock
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFileLockToGoAway(FirefoxChromeLauncher.java:269)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:309)
... 19 more
11:55:31.806 INFO - Got result: Failed to start new browser session: Unable to d
elete file C:\DOKUME~1\fpolyak\LOKALE~1\Temp\customProfileDirdf59775d37ca4e77bbd
b4d0f7b97d63c\parent.lock on session null
11:55:31.884 INFO - Command request: getNewBrowserSession[*chrome, http://joomla
] on session null
11:55:31.884 INFO - grabbing available session...
11:55:31.884 INFO - creating new remote session
11:55:31.884 INFO - Allocated session e782589f459f4d9c8c0164e05c1f8cf6 for http:
//joomla, launching...
11:55:32.040 INFO - Preparing Firefox profile...
11:55:53.719 ERROR - Failed to start new browser session, shutdown browser and c
lear all session data
java.lang.RuntimeException: Firefox refused shutdown while preparing a profile
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:311)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.pop
ulateCustomProfileDirectory(FirefoxChromeLauncher.java:106)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nch(FirefoxChromeLauncher.java:83)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau
nchRemoteSession(FirefoxChromeLauncher.java:350)
at org.openqa.selenium.server.BrowserSessionFactory.createNewRemoteSessi
on(BrowserSessionFactory.java:357)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
(BrowserSessionFactory.java:122)
at org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
(BrowserSessionFactory.java:84)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.getNewBrowse
rSession(SeleniumDriverResourceHandler.java:699)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.doCommand(Se
leniumDriverResourceHandler.java:393)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handleComman
dRequest(SeleniumDriverResourceHandler.java:364)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handle(Selen
iumDriverResourceHandler.java:125)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
at org.mortbay.http.HttpServer.service(HttpServer.java:909)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:820)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837)
at org.mortbay.http.SocketListener.handleConnection(SocketListener .java:
245)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
Caused by: org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher$Fil
eLockRemainedException: Lock file still present! C:\DOKUME~1\fpolyak\LOKALE~1\Te
mp\customProfileDire782589f459f4d9c8c0164e05c1f8cf6\parent.lock
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFileLockToGoAway(FirefoxChromeLauncher.java:269)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai
tForFullProfileToBeCreated(FirefoxChromeLauncher.java:309)
... 19 more
11:56:06.379 INFO - Got result: Failed to start new browser session: Unable to d
elete file C:\DOKUME~1\fpolyak\LOKALE~1\Temp\customProfileDire782589f459f4d9c8c0
164e05c1f8cf6\parent.lock on session null

-----

configdef.php:

class SeleniumConfig { var $host = 'http://joomla';
var $path = '';#'/j1513/';
var $username = 'admin';
var $password = 'admin';
var $browser = '*chrome';
var $baseURI = "c:/xampp/htdocs/joomla/";}

-----

Can anybody help me please?

Thanks

This might help: [http://clearspace.openqa.org/thread/15596 http://clearspace.openqa.org/thread/15596] [[User:Dextercowley|Mark Dexter]]

Running Automated Tests for the Joomla CMS

2010-06-30T04:15:04Z

PtrNrs: /* Install Selenium RC */

{{RightTOC}}
== 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 system (or functional) tests. The unit tests use PHPUnit and the system tests use PHPUnit and Selenium. The unit tests perform tests primarily on the Joomla! framework. The Selenium system tests actually 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 the these tests from your local workstation.

== Install PHPUnit ==
Both the unit and functional tests rely on PHPUnit. PHPUnit is a testing framework that requires PHP to be installed on the local workstation. XAMP / WAMP users can use the PHP installation that comes with them. Otherwise, you may need to install PHP, and the PEAR package, on your local workstation. More detailed instructions can be found at [http://www.php.net/manual/en/install.php http://www.php.net/manual/en/install.php].

On most PHP installations, PNPUnit can be installed using the standard PEAR installation process.

For example, on XAMPP version 1.7.3 on Windows, you would do the following commands:

* <code>cd c:\xampp\php</code>
* <code>pear channel-discover pear.phpunit.de</code>
* <code>pear channel-discover pear.symfony-project.com</code>
* <code>pear install phpunit/PHPUnit</code>

If you get error about PEAR version too low, run:

* <code>pear upgrade pear</code>

and repeat <code>pear install phpunit/PHPUnit</code>
.
Windows users not using WAMP or XAMPP can use the same procedure, with substituting the location of your PHP installation for <code>cd c:\xampp\php</code>.

In Ubuntu Linux, use the following commands to install PHPUnit:

* <code>$sudo pear channel-discover pear.phpunit.de</code>
* <code>$sudo pear channel-discover pear.symfony-project.com</code>
* <code>$sudo pear install phpunit/PHPUnit</code>

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].

== Running Unit Tests ==
Once PHPUnit is installed, you can run the unit tests. To run a unit test from the command line:
# Change to the folder <code><joomla root>/tests/unit</code>
# Execute the command <code>phpunit <test name or folder></code>
For example, to execute the test called "suite\libraries\joomla\utilities\JStringTest.php", you would type the command
* <code>phpunit suite\libraries\joomla\utilities\JStringTest.php</code>

When you run this, you will see output similar to the following:
<pre>
C:\xampp\htdocs\joomla_development\j16_trunk\tests\unit>phpunit suite\libraries\
joomla\utilities\jstringtest.php
PHPUnit 3.4.11 by Sebastian Bergmann.

............................................................ 60 / 89
.............................

Time: 26 seconds, Memory: 7.00Mb

OK (89 tests, 89 assertions)
</pre>
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.

You can execute all of the tests in a folder by specifying a folder instead of a file. For example, to run all of the tests in the folder "suite\libraries\joomla\utilities", you would enter
* <code>phpunit suite\libraries\joomla\utilities</code>

This command will produce output similar to that shown below:
<pre>
C:\xampp\htdocs\joomla_development\j16_trunk\tests\unit>phpunit suite\libraries\
joomla\utilities
PHPUnit 3.4.11 by Sebastian Bergmann.

............................................................ 60 / 317
............................................................ 120 / 317
............................................................ 180 / 317
............................................................ 240 / 317
............................................................ 300 / 317
...FFFF..........

Time: 27 seconds, Memory: 11.00Mb

There were 4 failures:

1) JUtilityTest::testGetHash
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-ce114e4501d2f4e2dcea3e17b546f339
+0cbc6611f5540bd0809a388dc95a615b

2) JUtilityTest::testGetToken with data set "default" (NULL, false)
Failed asserting that <string:adca734617ce829cc979492d6d037416> matches expected
<boolean:false>.

3) JUtilityTest::testGetToken with data set "false" (false, false)
Failed asserting that <string:adca734617ce829cc979492d6d037416> matches expected
<boolean:false>.

4) JUtilityTest::testGetToken with data set "true" (true, true)
Expectation failed for method name is equal to <string:getFormToken> when invoke
d 1 time(s).
Method was expected to be called 1 times, actually called 0 times.

FAILURES!
Tests: 317, Assertions: 361, Failures: 4.</pre>
In this case, we have 4 test failures with details about each.

== System Tests ==
Before you can run the system tests, you need to install and set up the Selenium RC package and configure your test environment, as shown below.

=== Install Selenium RC ===
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.

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 (such as selenium.bat though the name does not matter) or Linux shell script that runs the following command:

<code>java -jar selenium-server.jar -browserSessionReuse</code>

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>

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.

If You are using Firefox 3.6.x, be sure to install Selenium RC version 1.0.3 (released February 2010) or later. Earlier versions of Selenium RC have problems running in Firefox 3.6.x.

=== Create a Selenium Configuration File ===
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.

=== Run the System Test Suite ===
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 (the phpunit.bat file comes from the PHPUnit installation):

<code>phpunit.bat --bootstrap servers\configdef.php suite\TestSuite.php </code>

In Linux, the command is:

<code>phpunit --bootstrap servers/configdef.php suite/TestSuite.php </code>

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.

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.

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.

== 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.
* 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 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.

== 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.

=== Run a Unit Test ===
You can create an External Tools launch configuration that lets you run any unit test simply by pointing to the test file and pressing the Run button. Here are the steps:
* Open the Run→External Tools→External Tools Configuration menu and press the button labeled "New Launch Configuration".
* Enter a descriptive name, such as "Run Selected Unit Test".
* Enter the location that points to your phpunit.bat file (for example, <code>c:\xampp\php\phpunit.bat</code>).
* Set the Working Directory to <code>${project_loc}\tests\unit</code>
* Set the arguments to <code>c:\xampp\php\phpunit --verbose "${resource_loc}"</code>.
This is shown in the screenshot below.

[[Image:unit_test_tutorial_screenshot_20100405-01.png]]

To run a unit test:
# Select a unit test, either by selecting it in the PHP Explorer view or in the edit area of Eclipse.
# Run the External Launch configuration by selecting it from the drop-down list next to the External Launch Configuration button in the toolbar (shown below).

[[Image:unit_test_tutorial_screenshot_20100406-01.png]]

Note that a test might normally take a 30-60 seconds to run. The output of the test will show in the Eclipse console.

==== Run All Tests in a Folder ====
You can run all of the unit tests in a folder using this same launch configuration. Just select a folder instead of a test file and all of the unit tests in that folder will run.

=== Setting Up For Debugging ===

==== Make Sure XDebug is Installed ====
As you would expect, XDebug must be installed and configured for use with Eclipse. See [[Setting_up_your_workstation_for_Joomla!_development#Edit_PHP.INI_File]] for detailed instructions.

==== Add PEAR Library to Workspace ====
Before you can debug a unit or system test, you have to add the PEAR library to your project or workspace. In this example, we will add PEAR to our workspace. That way, all projects will automatically have access to PHPUnit.

Here are the steps:

* Select Window→Preferences→PHP→PHP Libraries.
* Press the New button and add PEAR as shown below. Be sure to press the checkbox labeled "Add to environment".

[[Image:unit_test_tutorial_screenshot_20100406-01a.png]]

* Press OK, then press the Add External folder button and browse to your PEAR folder, as shown below. In this example, the folder is in <code>c:\xampp\php\PEAR</code>.

[[Image:unit_test_tutorial_screenshot_20100406-01b.png]]

* Press OK and the screen should show the external folder, as shown below, with the correct file path for your workstation.

[[Image:unit_test_tutorial_screenshot_20100406-01c.png]]

After this is completed go to project preferences - > Properties -> PHP Include path -> Libraries tab -> Add library. Select User library in popup, click Next and mark Pear[enviroment] as checked.

Also make sure your project folder is added in Source tab of your project's PHP Include path.

==== Configure the PHP Executable ====
Normally, you will want to debug unit and system tests as PHP scripts (as opposed to web pages). Before you can do this, you need to configure a PHP Executable in Eclipse. This is done as follows:
* Select Window→Preferences→PHP→PHP Executables. The screen below will show.

[[Image:unit_test_tutorial_screenshot_20100406-05.png]]

* Press Add and complete the screen as shown below, substituting the correct file paths for your workstation.

[[Image:unit_test_tutorial_screenshot_20100406-06.png]]

At this point, your workstation is set up for PHPUnit debugging. Now you just have to create the debug configurations as shown in the next section.

=== Debug a Single Unit Test ===
Once you have PEAR added to your libraries, it is easy to set up a debug configuration that allows you to debug any unit test. Here are the steps:
* Press the drop-down arrow next to the Debug button and select Debug Configurations from the menu, as shown below.

[[Image:unit_test_tutorial_screenshot_20100406-02.png]]

* In the Debug Configurations window, make sure that PHP Script is selected and press the New Launch configuration button as shown below.

[[Image:unit_test_tutorial_screenshot_20100406-17.png]]

* Fill out the PHP Script tab of the Debug Configurations as shown below.
** Name: a descriptive name like "Debug Selected Unit Test"
** PHP Debugger: XDebug
** PHP Executable: The one you set up earlier (there will only be one)
** PHP File: Use the Browse button to browse to the phpunit.php file in your <code>tests/system</code> folder.

[[Image:unit_test_tutorial_screenshot_20100406-10.png]]

* Select the PHP Script Arguments tab and enter --verbose ${selected_resource_loc} as shown below.
** The "--verbose" option allows you to see more details when the tests are run.
** The "${selected_resource_loc}" passes the currently selected file at runtime, so you can use this configuration just by selecting the desired file and then running it.

[[Image:unit_test_tutorial_screenshot_20100406-11.png]]

* Finally, select the Common tab and check the Debug checkbox under "Display in favorites menu", as shown below.

[[Image:unit_test_tutorial_screenshot_20100406-09a.png]]

At this point, you are ready to debug any unit test. All you need to do is:
# Select the desired test file either in the PHP Explorer view or in the editor.
# Select Debug Configurations from the Debug drop-down button and select the "Debug Selected Unit Test" option. Once you have run this once, it will show on your Debug favorites menu.

=== Run a Single System Test ===
You can create a configuration to make it easy to run any single test in your project. To do this:
* Open the Run→External Tools→External Tools Configuration menu and press the button labeled "New Launch Configuration"
* Enter the location that points to your phpunit.bat file (for example, <code>c:\xampp\php\phpunit.bat</code>). On Linux systems, this might be called "phpunit".
* Set the Working Directory to <code>${project_loc}/tests/system</code>
* Set the arguments to <code>--bootstrap servers/configdef.php ${selected_resource_loc}</code>.
This is shown in the screenshot below.

[[Image:unit_test_tutorial_screenshot_20100406-14.png]]

To use this configuration,
# Make sure the Selenium RC process is running (for example, by running the "selenium.bat" file you created when you installed Selenium RC earlier)
# Select the desired test file by clicking on it in the PHP Explorer view or in the edit area
# Start this launch configuration
The selected test file will be run and you will see the browser session open and run the test script. The test results will be reported in the Eclipse console.

=== Debug a Single System Test ===
The steps for creating a Debug Configuration for a Selenium system test are similar to those for the unit test.
* Open Debug Configurations from the drop-down menu next to the Debug Button on the toolbar, as shown below.

[[Image:unit_test_tutorial_screenshot_20100406-02.png]]

* In the Debug Configurations window, make sure that PHP Script is selected and press the New Launch configuration button as shown below.

[[Image:unit_test_tutorial_screenshot_20100406-17.png]]

* Fill out the Debug Configurations dialog box as shown below:
** Name: A descriptive name for the configuration, like "Debug Selected System Test".
** PHP Debugger: XDebug
** PHP Executable: The one you defined earlier (there probably is only one).
** PHP File: Browse to the phpunit.php file in your <code>tests/system</code> folder.

[[Image:unit_test_tutorial_screenshot_20100406-12.png]]

* Select the PHP Script arguments and fill this out as shown below.
** --bootstrap servers/configdef.php points to the configuration file that passes the login information to Selenium.
** "${selected_resource_loc}" passes the location of the currently selected file in Eclipse to the command line.

[[Image:unit_test_tutorial_screenshot_20100406-13.png]]

* Finally, select the Common tab and check the Debug option in the Display in favorites menu. This will add this configuration to your favorites.

[[Image:unit_test_tutorial_screenshot_20100406-09a.png]]

At this point, you can debug any system test. To do so:
# Make sure the Selenium RC program is running in the background.
# Select the desired test by selecting it in the PHP Explorer or in the editor.
# Run this Debug Configuration by selecting the drop-down arrow next to the Debug button, then Debug Configurations, then the "Debug Selected System Test" configuration created above.

=== Run the System Test Suite ===
To create a launch configuration to run the Test Suite of the currently-selected Eclipse project:
* Enter the location that points to your phpunit.bat file. If you are running Linux, this file might be called phpunit.
* Set the Working Directory to <code>${project_loc}/tests\system</code>
* Set the arguments to <code>--bootstrap servers/configdef.php suite/TestSuite.php</code>.
This is shown in the screenshot below.

[[Image:unit_test_tutorial_screenshot_20100406-15.png]]

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.

[[Category:Bug Squad]] [[Category:Development]] [[Category:Testing]] [[Category:Automated Testing]] [[Category:Joomla! 1.6]]

Running Automated Tests for the Joomla CMS

2010-06-30T03:48:55Z

PtrNrs: /* Running Unit Tests */

{{RightTOC}}
== 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 system (or functional) tests. The unit tests use PHPUnit and the system tests use PHPUnit and Selenium. The unit tests perform tests primarily on the Joomla! framework. The Selenium system tests actually 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 the these tests from your local workstation.

== Install PHPUnit ==
Both the unit and functional tests rely on PHPUnit. PHPUnit is a testing framework that requires PHP to be installed on the local workstation. XAMP / WAMP users can use the PHP installation that comes with them. Otherwise, you may need to install PHP, and the PEAR package, on your local workstation. More detailed instructions can be found at [http://www.php.net/manual/en/install.php http://www.php.net/manual/en/install.php].

On most PHP installations, PNPUnit can be installed using the standard PEAR installation process.

For example, on XAMPP version 1.7.3 on Windows, you would do the following commands:

* <code>cd c:\xampp\php</code>
* <code>pear channel-discover pear.phpunit.de</code>
* <code>pear channel-discover pear.symfony-project.com</code>
* <code>pear install phpunit/PHPUnit</code>

If you get error about PEAR version too low, run:

* <code>pear upgrade pear</code>

and repeat <code>pear install phpunit/PHPUnit</code>
.
Windows users not using WAMP or XAMPP can use the same procedure, with substituting the location of your PHP installation for <code>cd c:\xampp\php</code>.

In Ubuntu Linux, use the following commands to install PHPUnit:

* <code>$sudo pear channel-discover pear.phpunit.de</code>
* <code>$sudo pear channel-discover pear.symfony-project.com</code>
* <code>$sudo pear install phpunit/PHPUnit</code>

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].

== Running Unit Tests ==
Once PHPUnit is installed, you can run the unit tests. To run a unit test from the command line:
# Change to the folder <code><joomla root>/tests/unit</code>
# Execute the command <code>phpunit <test name or folder></code>
For example, to execute the test called "suite\libraries\joomla\utilities\JStringTest.php", you would type the command
* <code>phpunit suite\libraries\joomla\utilities\JStringTest.php</code>

When you run this, you will see output similar to the following:
<pre>
C:\xampp\htdocs\joomla_development\j16_trunk\tests\unit>phpunit suite\libraries\
joomla\utilities\jstringtest.php
PHPUnit 3.4.11 by Sebastian Bergmann.

............................................................ 60 / 89
.............................

Time: 26 seconds, Memory: 7.00Mb

OK (89 tests, 89 assertions)
</pre>
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.

You can execute all of the tests in a folder by specifying a folder instead of a file. For example, to run all of the tests in the folder "suite\libraries\joomla\utilities", you would enter
* <code>phpunit suite\libraries\joomla\utilities</code>

This command will produce output similar to that shown below:
<pre>
C:\xampp\htdocs\joomla_development\j16_trunk\tests\unit>phpunit suite\libraries\
joomla\utilities
PHPUnit 3.4.11 by Sebastian Bergmann.

............................................................ 60 / 317
............................................................ 120 / 317
............................................................ 180 / 317
............................................................ 240 / 317
............................................................ 300 / 317
...FFFF..........

Time: 27 seconds, Memory: 11.00Mb

There were 4 failures:

1) JUtilityTest::testGetHash
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-ce114e4501d2f4e2dcea3e17b546f339
+0cbc6611f5540bd0809a388dc95a615b

2) JUtilityTest::testGetToken with data set "default" (NULL, false)
Failed asserting that <string:adca734617ce829cc979492d6d037416> matches expected
<boolean:false>.

3) JUtilityTest::testGetToken with data set "false" (false, false)
Failed asserting that <string:adca734617ce829cc979492d6d037416> matches expected
<boolean:false>.

4) JUtilityTest::testGetToken with data set "true" (true, true)
Expectation failed for method name is equal to <string:getFormToken> when invoke
d 1 time(s).
Method was expected to be called 1 times, actually called 0 times.

FAILURES!
Tests: 317, Assertions: 361, Failures: 4.</pre>
In this case, we have 4 test failures with details about each.

== System Tests ==
Before you can run the system tests, you need to install and set up the Selenium RC package and configure your test environment, as shown below.

=== Install Selenium RC ===
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.

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 (such as selenium.bat though the name does not matter) or Linux shell script that runs the following command:

<code>java -jar selenium-server.jar -browserSessionReuse</code>

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>

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.

If You are using Firefox 3.6.x, be sure to install Selenium RC version 1.0.3 (released February 2010) or later. Earlier versions of Selenium RC have problems running in Firefox 3.6.x.

=== Create a Selenium Configuration File ===
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.

=== Run the System Test Suite ===
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 (the phpunit.bat file comes from the PHPUnit installation):

<code>phpunit.bat --bootstrap servers\configdef.php suite\TestSuite.php </code>

In Linux, the command is:

<code>phpunit --bootstrap servers/configdef.php suite/TestSuite.php </code>

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.

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.

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.

== 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.
* 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 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.

== 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.

=== Run a Unit Test ===
You can create an External Tools launch configuration that lets you run any unit test simply by pointing to the test file and pressing the Run button. Here are the steps:
* Open the Run→External Tools→External Tools Configuration menu and press the button labeled "New Launch Configuration".
* Enter a descriptive name, such as "Run Selected Unit Test".
* Enter the location that points to your phpunit.bat file (for example, <code>c:\xampp\php\phpunit.bat</code>).
* Set the Working Directory to <code>${project_loc}\tests\unit</code>
* Set the arguments to <code>c:\xampp\php\phpunit --verbose "${resource_loc}"</code>.
This is shown in the screenshot below.

[[Image:unit_test_tutorial_screenshot_20100405-01.png]]

To run a unit test:
# Select a unit test, either by selecting it in the PHP Explorer view or in the edit area of Eclipse.
# Run the External Launch configuration by selecting it from the drop-down list next to the External Launch Configuration button in the toolbar (shown below).

[[Image:unit_test_tutorial_screenshot_20100406-01.png]]

Note that a test might normally take a 30-60 seconds to run. The output of the test will show in the Eclipse console.

==== Run All Tests in a Folder ====
You can run all of the unit tests in a folder using this same launch configuration. Just select a folder instead of a test file and all of the unit tests in that folder will run.

=== Setting Up For Debugging ===

==== Make Sure XDebug is Installed ====
As you would expect, XDebug must be installed and configured for use with Eclipse. See [[Setting_up_your_workstation_for_Joomla!_development#Edit_PHP.INI_File]] for detailed instructions.

==== Add PEAR Library to Workspace ====
Before you can debug a unit or system test, you have to add the PEAR library to your project or workspace. In this example, we will add PEAR to our workspace. That way, all projects will automatically have access to PHPUnit.

Here are the steps:

* Select Window→Preferences→PHP→PHP Libraries.
* Press the New button and add PEAR as shown below. Be sure to press the checkbox labeled "Add to environment".

[[Image:unit_test_tutorial_screenshot_20100406-01a.png]]

* Press OK, then press the Add External folder button and browse to your PEAR folder, as shown below. In this example, the folder is in <code>c:\xampp\php\PEAR</code>.

[[Image:unit_test_tutorial_screenshot_20100406-01b.png]]

* Press OK and the screen should show the external folder, as shown below, with the correct file path for your workstation.

[[Image:unit_test_tutorial_screenshot_20100406-01c.png]]

After this is completed go to project preferences - > Properties -> PHP Include path -> Libraries tab -> Add library. Select User library in popup, click Next and mark Pear[enviroment] as checked.

Also make sure your project folder is added in Source tab of your project's PHP Include path.

==== Configure the PHP Executable ====
Normally, you will want to debug unit and system tests as PHP scripts (as opposed to web pages). Before you can do this, you need to configure a PHP Executable in Eclipse. This is done as follows:
* Select Window→Preferences→PHP→PHP Executables. The screen below will show.

[[Image:unit_test_tutorial_screenshot_20100406-05.png]]

* Press Add and complete the screen as shown below, substituting the correct file paths for your workstation.

[[Image:unit_test_tutorial_screenshot_20100406-06.png]]

At this point, your workstation is set up for PHPUnit debugging. Now you just have to create the debug configurations as shown in the next section.

=== Debug a Single Unit Test ===
Once you have PEAR added to your libraries, it is easy to set up a debug configuration that allows you to debug any unit test. Here are the steps:
* Press the drop-down arrow next to the Debug button and select Debug Configurations from the menu, as shown below.

[[Image:unit_test_tutorial_screenshot_20100406-02.png]]

* In the Debug Configurations window, make sure that PHP Script is selected and press the New Launch configuration button as shown below.

[[Image:unit_test_tutorial_screenshot_20100406-17.png]]

* Fill out the PHP Script tab of the Debug Configurations as shown below.
** Name: a descriptive name like "Debug Selected Unit Test"
** PHP Debugger: XDebug
** PHP Executable: The one you set up earlier (there will only be one)
** PHP File: Use the Browse button to browse to the phpunit.php file in your <code>tests/system</code> folder.

[[Image:unit_test_tutorial_screenshot_20100406-10.png]]

* Select the PHP Script Arguments tab and enter --verbose ${selected_resource_loc} as shown below.
** The "--verbose" option allows you to see more details when the tests are run.
** The "${selected_resource_loc}" passes the currently selected file at runtime, so you can use this configuration just by selecting the desired file and then running it.

[[Image:unit_test_tutorial_screenshot_20100406-11.png]]

* Finally, select the Common tab and check the Debug checkbox under "Display in favorites menu", as shown below.

[[Image:unit_test_tutorial_screenshot_20100406-09a.png]]

At this point, you are ready to debug any unit test. All you need to do is:
# Select the desired test file either in the PHP Explorer view or in the editor.
# Select Debug Configurations from the Debug drop-down button and select the "Debug Selected Unit Test" option. Once you have run this once, it will show on your Debug favorites menu.

=== Run a Single System Test ===
You can create a configuration to make it easy to run any single test in your project. To do this:
* Open the Run→External Tools→External Tools Configuration menu and press the button labeled "New Launch Configuration"
* Enter the location that points to your phpunit.bat file (for example, <code>c:\xampp\php\phpunit.bat</code>). On Linux systems, this might be called "phpunit".
* Set the Working Directory to <code>${project_loc}/tests/system</code>
* Set the arguments to <code>--bootstrap servers/configdef.php ${selected_resource_loc}</code>.
This is shown in the screenshot below.

[[Image:unit_test_tutorial_screenshot_20100406-14.png]]

To use this configuration,
# Make sure the Selenium RC process is running (for example, by running the "selenium.bat" file you created when you installed Selenium RC earlier)
# Select the desired test file by clicking on it in the PHP Explorer view or in the edit area
# Start this launch configuration
The selected test file will be run and you will see the browser session open and run the test script. The test results will be reported in the Eclipse console.

=== Debug a Single System Test ===
The steps for creating a Debug Configuration for a Selenium system test are similar to those for the unit test.
* Open Debug Configurations from the drop-down menu next to the Debug Button on the toolbar, as shown below.

[[Image:unit_test_tutorial_screenshot_20100406-02.png]]

* In the Debug Configurations window, make sure that PHP Script is selected and press the New Launch configuration button as shown below.

[[Image:unit_test_tutorial_screenshot_20100406-17.png]]

* Fill out the Debug Configurations dialog box as shown below:
** Name: A descriptive name for the configuration, like "Debug Selected System Test".
** PHP Debugger: XDebug
** PHP Executable: The one you defined earlier (there probably is only one).
** PHP File: Browse to the phpunit.php file in your <code>tests/system</code> folder.

[[Image:unit_test_tutorial_screenshot_20100406-12.png]]

* Select the PHP Script arguments and fill this out as shown below.
** --bootstrap servers/configdef.php points to the configuration file that passes the login information to Selenium.
** "${selected_resource_loc}" passes the location of the currently selected file in Eclipse to the command line.

[[Image:unit_test_tutorial_screenshot_20100406-13.png]]

* Finally, select the Common tab and check the Debug option in the Display in favorites menu. This will add this configuration to your favorites.

[[Image:unit_test_tutorial_screenshot_20100406-09a.png]]

At this point, you can debug any system test. To do so:
# Make sure the Selenium RC program is running in the background.
# Select the desired test by selecting it in the PHP Explorer or in the editor.
# Run this Debug Configuration by selecting the drop-down arrow next to the Debug button, then Debug Configurations, then the "Debug Selected System Test" configuration created above.

=== Run the System Test Suite ===
To create a launch configuration to run the Test Suite of the currently-selected Eclipse project:
* Enter the location that points to your phpunit.bat file. If you are running Linux, this file might be called phpunit.
* Set the Working Directory to <code>${project_loc}/tests\system</code>
* Set the arguments to <code>--bootstrap servers/configdef.php suite/TestSuite.php</code>.
This is shown in the screenshot below.

[[Image:unit_test_tutorial_screenshot_20100406-15.png]]

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.

[[Category:Bug Squad]] [[Category:Development]] [[Category:Testing]] [[Category:Automated Testing]] [[Category:Joomla! 1.6]]

Setting up Apache, PHP and MySQL manually

2010-05-29T01:59:31Z

PtrNrs: /* MySQL setup */

==Overview==
Here follows a brief overview of the steps to setup a Apache, PHP, MySQL in a Windows environment and also refer to various related tools to maintain and work with most of the tasks related to Joomla!.

In order to make the instruction clear and succinct, we will assume that wherever we are not stating any explicit instruction, you will let the default setup paths apply without modification.

===Warning===
If you already have any of the prepackaged AMP stacks installed on your machine:
* going back to your AMP stack afterwards will be difficult. This is since the various installations we will do below will overwrite registry values and general environment changes (this applies at least for the PC/Windows environment).
* if you need to maintain any configuration (Apache, MySQL or PHP configuration) or data (your existing websites and related databases), before making attempts of following through this instruction, make proper backup of those
(needs to be expanded with specific advice on how to achieve the aboves...)

===Resources===
* http://docs.joomla.org/Setting_up_your_workstation_for_Joomla!_development resource on all things related to the topic of this document and more. Geared towards using prepackaged AMP stacks.

==MySQL setup==
# Download the appropriate MySQL installer option for your platform (commonly x86, 32-bit) from http://www.mysql.com/downloads/mysql/
# Start the installation and choose Custom installation path
# Click through the whole installation process and click Finish
# You will now be presented with the "MySQL Server Instance Configuration Wizard"
## Make sure that the "Standard Configuration" is selected and go to Next
## If you already have MySQL installed you may get the message "A Windows service with the name MySQL already exists. Please uninstall this service correctly or choose a different name for the new service." If so, choose an alternative service name. --[[User:PtrNrs|Pete Nurse]] 01:57, 29 May 2010 (UTC)
## In the next window Check for "Include Bin Directory in Windows PATH". By doing this you will be able to access the various MySQL utilities from the command line.
## In the next window you will be able to create password for your root MySQL user, the user with highest access level on your server.
## In the next and final window all the changes you have configured until now will be saved when you press the Execute button, and the windows service for this instance will be started.

===Notes===
# In order to make the instruction as accessible as possible we skipped a number of configuration scenarios of your MySQL instance, such as being able to relocate your database files etc. This and more is outlined in http://dev.mysql.com/doc/refman/5.1/en/mysql-config-wizard.html
# MySQL installs as default with a STRICT mode which might give rise to some errors when using extensions or applications that haven't considered this. Refer to this resource for more on this: http://dev.mysql.com/doc/refman/5.0/en/server-sql-mode.html

===Resources===
* HeidiSQL: http://www.heidisql.com/ easy to use and extensible full-client replacement of phpMyAdmin under constant development
* MySQL Workbench (version 5.2 and above): http://dev.mysql.com/downloads/workbench/ consists of various tools among which you will appreciate the Administrator, which helps you to configure your MySQL instance. Requires .Net framework http://www.microsoft.com/net/
* phpMyAdmin: http://www.phpmyadmin.net/ , powerful web based MySQL client for administrating anything related to MySQL
* MySQL documentation http://dev.mysql.com/doc/ available in different formats

==Apache setup==
# Download the installer of your preference. Currently you should aim for version 2.2.*, Win32 Binary without crypto applies) from http://httpd.apache.org/download.cgi
# Run the installer wizard and click through each step until you reach the Server Information window and give the options below respectively and in the given order in each of the fields, unless you have any specific requirements as to how your web server is setup:
## localhost,
## localhost and
## admin@localhost
# Click through the wizard which will install and start the apache web server as a windows service.
# In the windows status bar you will now see a pink colored feather with a green colored play button indicating Apache is up and running. Point your browser to http://localhost/ and you should get a page indicating its working.
# Let us now go to the location where Apache is installed which commonly is at C:\Program Files\Apache Software Foundation\Apache2.2 and go through the various directories
## bin - contains the various binary files some of which are listed below. In order to access these applications, most of which are command based, we would need to add the path to the bin directory in our global PATH variable. To do that right click on My Computer > Properties > Advanced > Environments Variables and in the System Variables list locate and select the Variable PATH and click on Edit and add a trailing a semi-colon, if not already there, followed by the absolute path to your bin directory. And click out from the System Properties dialogue by accepting.
### httpd.exe which is the Apache webserver itself, which is spawned to several child processes while serving as many simultaneous incoming clients requests as required by MaxClients directive;
### ab.exe is a benchmarking tool that comes with Apache allowing you to see how well your application can perform per time unit
## conf - folder where various configuration files are located of which the following are of most interest in our case
### httpd.conf - most of the server directives are located in this file and for easy access you should associate the .conf file type with a user friendly editor, i.e. anything other than the default Notepad.
### extra\httpd-vhosts.conf - contains directives that would allow you use your local server as virtual host, i.e. able to run several servers on your PC. One usage scenario is that during a development phase if you want to map the actual domain you are working for to your local copy, you would be able to do so by making minor tweaks in this file. We will discuss this in more detail below.
## htdocs - the default web server root, this is where the http://localhost/ is mapped, i.e. if you don't reconfigure it in httpd.conf above.
## logs - access and error logs, when trying to address various issues related to your server or even your application
===Virtual hosting===

===Resources===
* http://httpd.apache.org/docs/2.2/ reference documentation

==PHP setup==
# Download PHP from http://windows.php.net/download/ and choose commonly VC6 x86 Thread Safe in Zip format. The various options have to do with how the PHP code base was compiled to binary and is probably nothing you should worry about for now.
# Create a folder under your C:\Program Files\ (or wherever your program directory is located) a folder called PHP.
# Locate your downloaded Zip file and move it to the newly created folder and unpack it directly into the folder.
# Let us now add the PHP path to our global PATH variable by following the instruction above

===Configuring PHP===
The configuration amounts to editing the php.ini file. A sample file for different scenarios are already in your PHP folder. Let us rename php.ini-development to php.ini and open it in your favorite text editor. The common values to tweak are as follows and all of these variables are well documented in the php.ini file (please note that this is a server wide setting applying to all your projects):
* max_execution_time - whenever you have scripts that run for too long and the server returns various unexpected results which you think is due to not being able to run through the whole process
* memory_limit
* error_reporting
* display_errors
* log_errors - a variable you would need to take note of in production scenarios
* upload_tmp_dir
* upload_max_filesize
* extension_dir - in order to avoid complications we will point out the directory where the following extensions are located by uncommenting this variable and assign the absolute location of the folder, and the complete line should read as follows
<pre>
extension_dir = "C:\Program Files\PHP\ext"
</pre>
* Dynamic extensions section contains various additional modules that you want to be loaded with, and the commented once are those that comes prepackaged with PHP and can be found in the ext directory in your PHP folder. If you want to activate any just remove the commenting as you should do with the following extensions:
** php_curl.dll
** php_gd2.dll
** php_mbstring.dll
** php_mysql.dll
** php_mysqli.dll
** php_pdo.dll
** php_pdo_mysql.dll
** php_xsl.dll
* session.save_path

===Configuring Apache to work with PHP===
Now that we have configured PHP to work as we want it, lets go to Apache and do the same.
* Open httpd.conf. and in the "Dynamic Shared Object (DSO) Support" section add the following directives (if you have located your PHP folder differently do make corresponding change for php5apache2_2.dll below):
<pre>
LoadModule php5_module "C:/Program Files/PHP/php5apache2_2.dll"
AddType application/x-httpd-php .php
</pre>
* In the DirectoryIndex add index.php and index.htm as possible files to serve when directory is requested as follows
<pre>
DirectoryIndex index.html index.htm index.php
</pre>.
* At the end of the file add the following line which will point out where the php.ini file is located
<pre>
PHPIniDir "C:/Program Files/PHP"
</pre>

===Restart and test PHP===
As soon as you make any change to any of php.ini or httpd.conf or any other configuration files you need to restart Apache to see the actual effect of the changes. So lets now restart Apache by using the Apache Monitor tool you can find in your Windows status bar. Hopefully you are not prompted with any dialogues and the Apache Monitor continues to run green.

We will now make a test that PHP is working. Go to your web servers document root (in the default case C:\Program Files\Apache Software Foundation\Apache2.2\htdocs) and add a file called phpinfo.php with the following content:

<pre>
<?php
phpinfo();
phpinfo(INFO_MODULES);
?>
</pre>

This will render a page containing information about your PHP setup and about the various modules/extensions that are currently loaded. Point now your browser to http://localhost/phpinfo.php.

===Installing and configuring xdebug===
# Point your browser to http://www.xdebug.org/find-binary.php. This page will assist you to find the latest suitable version of xdebug.
# Copy the entire page of the phpinfo page we ran above and paste it into the textarea and follow the instructions provided to install
===Resources===
* http://www.php.net/docs.php excellent and up to date documentation with valuable additional comments from users. Also a downloadable versions are available.
* http://devzone.zend.com/article/2803 excellent and in depth tutorial on debugging with xdebug
* http://xdebug.org/docs/ xdebug reference documentation

[[Category:Bug Squad]]

Setting up Apache, PHP and MySQL manually

2010-05-29T01:57:01Z

PtrNrs: /* MySQL setup */

==Overview==
Here follows a brief overview of the steps to setup a Apache, PHP, MySQL in a Windows environment and also refer to various related tools to maintain and work with most of the tasks related to Joomla!.

In order to make the instruction clear and succinct, we will assume that wherever we are not stating any explicit instruction, you will let the default setup paths apply without modification.

===Warning===
If you already have any of the prepackaged AMP stacks installed on your machine:
* going back to your AMP stack afterwards will be difficult. This is since the various installations we will do below will overwrite registry values and general environment changes (this applies at least for the PC/Windows environment).
* if you need to maintain any configuration (Apache, MySQL or PHP configuration) or data (your existing websites and related databases), before making attempts of following through this instruction, make proper backup of those
(needs to be expanded with specific advice on how to achieve the aboves...)

===Resources===
* http://docs.joomla.org/Setting_up_your_workstation_for_Joomla!_development resource on all things related to the topic of this document and more. Geared towards using prepackaged AMP stacks.

==MySQL setup==
# Download the appropriate MySQL installer option for your platform (commonly x86, 32-bit) from http://www.mysql.com/downloads/mysql/
# Start the installation and choose Custom installation path
# Click through the whole installation process and click Finish
# You will now be presented with the "MySQL Server Instance Configuration Wizard"
## Make sure that the "Standard Configuration" is selected and go to Next
## If you already have MySQL installed you may get the message "A Windows service with the name MySQL already exists. Please uninstall this service correctly or choose a different name for the new service." If so, choose an alternative service name.--[[User:PtrNrs|Pete Nurse]] 01:57, 29 May 2010 (UTC)
## In the next window Check for "Include Bin Directory in Windows PATH". By doing this you will be able to access the various MySQL utilities from the command line.
## In the next window you will be able to create password for your root MySQL user, the user with highest access level on your server.
## In the next and final window all the changes you have configured until now will be saved when you press the Execute button, and the windows service for this instance will be started.

===Notes===
# In order to make the instruction as accessible as possible we skipped a number of configuration scenarios of your MySQL instance, such as being able to relocate your database files etc. This and more is outlined in http://dev.mysql.com/doc/refman/5.1/en/mysql-config-wizard.html
# MySQL installs as default with a STRICT mode which might give rise to some errors when using extensions or applications that haven't considered this. Refer to this resource for more on this: http://dev.mysql.com/doc/refman/5.0/en/server-sql-mode.html

===Resources===
* HeidiSQL: http://www.heidisql.com/ easy to use and extensible full-client replacement of phpMyAdmin under constant development
* MySQL Workbench (version 5.2 and above): http://dev.mysql.com/downloads/workbench/ consists of various tools among which you will appreciate the Administrator, which helps you to configure your MySQL instance. Requires .Net framework http://www.microsoft.com/net/
* phpMyAdmin: http://www.phpmyadmin.net/ , powerful web based MySQL client for administrating anything related to MySQL
* MySQL documentation http://dev.mysql.com/doc/ available in different formats

==Apache setup==
# Download the installer of your preference. Currently you should aim for version 2.2.*, Win32 Binary without crypto applies) from http://httpd.apache.org/download.cgi
# Run the installer wizard and click through each step until you reach the Server Information window and give the options below respectively and in the given order in each of the fields, unless you have any specific requirements as to how your web server is setup:
## localhost,
## localhost and
## admin@localhost
# Click through the wizard which will install and start the apache web server as a windows service.
# In the windows status bar you will now see a pink colored feather with a green colored play button indicating Apache is up and running. Point your browser to http://localhost/ and you should get a page indicating its working.
# Let us now go to the location where Apache is installed which commonly is at C:\Program Files\Apache Software Foundation\Apache2.2 and go through the various directories
## bin - contains the various binary files some of which are listed below. In order to access these applications, most of which are command based, we would need to add the path to the bin directory in our global PATH variable. To do that right click on My Computer > Properties > Advanced > Environments Variables and in the System Variables list locate and select the Variable PATH and click on Edit and add a trailing a semi-colon, if not already there, followed by the absolute path to your bin directory. And click out from the System Properties dialogue by accepting.
### httpd.exe which is the Apache webserver itself, which is spawned to several child processes while serving as many simultaneous incoming clients requests as required by MaxClients directive;
### ab.exe is a benchmarking tool that comes with Apache allowing you to see how well your application can perform per time unit
## conf - folder where various configuration files are located of which the following are of most interest in our case
### httpd.conf - most of the server directives are located in this file and for easy access you should associate the .conf file type with a user friendly editor, i.e. anything other than the default Notepad.
### extra\httpd-vhosts.conf - contains directives that would allow you use your local server as virtual host, i.e. able to run several servers on your PC. One usage scenario is that during a development phase if you want to map the actual domain you are working for to your local copy, you would be able to do so by making minor tweaks in this file. We will discuss this in more detail below.
## htdocs - the default web server root, this is where the http://localhost/ is mapped, i.e. if you don't reconfigure it in httpd.conf above.
## logs - access and error logs, when trying to address various issues related to your server or even your application
===Virtual hosting===

===Resources===
* http://httpd.apache.org/docs/2.2/ reference documentation

==PHP setup==
# Download PHP from http://windows.php.net/download/ and choose commonly VC6 x86 Thread Safe in Zip format. The various options have to do with how the PHP code base was compiled to binary and is probably nothing you should worry about for now.
# Create a folder under your C:\Program Files\ (or wherever your program directory is located) a folder called PHP.
# Locate your downloaded Zip file and move it to the newly created folder and unpack it directly into the folder.
# Let us now add the PHP path to our global PATH variable by following the instruction above

===Configuring PHP===
The configuration amounts to editing the php.ini file. A sample file for different scenarios are already in your PHP folder. Let us rename php.ini-development to php.ini and open it in your favorite text editor. The common values to tweak are as follows and all of these variables are well documented in the php.ini file (please note that this is a server wide setting applying to all your projects):
* max_execution_time - whenever you have scripts that run for too long and the server returns various unexpected results which you think is due to not being able to run through the whole process
* memory_limit
* error_reporting
* display_errors
* log_errors - a variable you would need to take note of in production scenarios
* upload_tmp_dir
* upload_max_filesize
* extension_dir - in order to avoid complications we will point out the directory where the following extensions are located by uncommenting this variable and assign the absolute location of the folder, and the complete line should read as follows
<pre>
extension_dir = "C:\Program Files\PHP\ext"
</pre>
* Dynamic extensions section contains various additional modules that you want to be loaded with, and the commented once are those that comes prepackaged with PHP and can be found in the ext directory in your PHP folder. If you want to activate any just remove the commenting as you should do with the following extensions:
** php_curl.dll
** php_gd2.dll
** php_mbstring.dll
** php_mysql.dll
** php_mysqli.dll
** php_pdo.dll
** php_pdo_mysql.dll
** php_xsl.dll
* session.save_path

===Configuring Apache to work with PHP===
Now that we have configured PHP to work as we want it, lets go to Apache and do the same.
* Open httpd.conf. and in the "Dynamic Shared Object (DSO) Support" section add the following directives (if you have located your PHP folder differently do make corresponding change for php5apache2_2.dll below):
<pre>
LoadModule php5_module "C:/Program Files/PHP/php5apache2_2.dll"
AddType application/x-httpd-php .php
</pre>
* In the DirectoryIndex add index.php and index.htm as possible files to serve when directory is requested as follows
<pre>
DirectoryIndex index.html index.htm index.php
</pre>.
* At the end of the file add the following line which will point out where the php.ini file is located
<pre>
PHPIniDir "C:/Program Files/PHP"
</pre>

===Restart and test PHP===
As soon as you make any change to any of php.ini or httpd.conf or any other configuration files you need to restart Apache to see the actual effect of the changes. So lets now restart Apache by using the Apache Monitor tool you can find in your Windows status bar. Hopefully you are not prompted with any dialogues and the Apache Monitor continues to run green.

We will now make a test that PHP is working. Go to your web servers document root (in the default case C:\Program Files\Apache Software Foundation\Apache2.2\htdocs) and add a file called phpinfo.php with the following content:

<pre>
<?php
phpinfo();
phpinfo(INFO_MODULES);
?>
</pre>

This will render a page containing information about your PHP setup and about the various modules/extensions that are currently loaded. Point now your browser to http://localhost/phpinfo.php.

===Installing and configuring xdebug===
# Point your browser to http://www.xdebug.org/find-binary.php. This page will assist you to find the latest suitable version of xdebug.
# Copy the entire page of the phpinfo page we ran above and paste it into the textarea and follow the instructions provided to install
===Resources===
* http://www.php.net/docs.php excellent and up to date documentation with valuable additional comments from users. Also a downloadable versions are available.
* http://devzone.zend.com/article/2803 excellent and in depth tutorial on debugging with xdebug
* http://xdebug.org/docs/ xdebug reference documentation

[[Category:Bug Squad]]

Setting up Apache, PHP and MySQL manually

2010-05-27T22:44:37Z

PtrNrs: /* Notes */

WIP
==Overview==
Here follows a brief overview of the steps to setup a Apache, PHP, MySQL in a Windows environment and also refer to various related tools to maintain and work with most of the tasks related to Joomla!.

In order to make the instruction clear and succinct, we will assume that wherever we are not stating any explicit instruction, you will let the default setup paths apply without modification.

===Warning===
* If you already have any of the prepackaged AMP stacks installed, before making any attempts of following through the following instructions, please make sure to make proper backup of your sites and any eventual configurations you would like to maintain.
* Futhermore in the PC environment (at least), this procedure will overwrite one or more registry entries. It's strongly recommended that, your first attempt is on a computer with no AMP install whatsoever.
(needs to be expanded...)

===Resources===
* http://docs.joomla.org/Setting_up_your_workstation_for_Joomla!_development resource on all things related to the topic of this document and more. Geared towards using prepackaged AMP stacks.

==MySQL setup==
# Download the appropriate MySQL installer option for your platform (commonly x86, 32-bit) from http://www.mysql.com/downloads/mysql/
# Start the installation and choose Custom installation path
# Click through the whole installation process and click Finish
# You will now be presented with the "MySQL Server Instance Configuration Wizard"
## Make sure that the "Standard Configuration" is selected and go to Next
## In the next window Check for "Include Bin Directory in Windows PATH". By doing this you will be able to access the various MySQL utilities from the command line.
## In the next window you will be able to create password for your root MySQL user, the user with highest access level on your server.
## In the next and final window all the changes you have configured until now will be saved when you press the Execute button, and the windows service for this instance will be started.

===Notes===
# In order to make the instruction as accessible as possible we skipped a number of configuration scenarios of your MySQL instance, such as being able to relocate your database files etc. This and more is outlined in http://dev.mysql.com/doc/refman/5.1/en/mysql-config-wizard.html
# MySQL installs as default with a STRICT mode which might give rise to some errors when using extensions or applications that haven't considered this. Refer to this resource for more on this: http://dev.mysql.com/doc/refman/5.0/en/server-sql-mode.html

===Resources===
* HeidiSQL: http://www.heidisql.com/ easy to use and extensible full-client replacement of phpMyAdmin under constant development
* MySQL Workbench (version 5.2 and above): http://dev.mysql.com/downloads/workbench/ consists of various tools among which you will appreciate the Administrator, which helps you to configure your MySQL instance. Requires .Net framework http://www.microsoft.com/net/
* phpMyAdmin: http://www.phpmyadmin.net/ , powerful web based MySQL client for administrating anything related to MySQL
* MySQL documentation http://dev.mysql.com/doc/ available in different formats

==Apache setup==
# Download the installer of your preference. Currently you should aim for version 2.2.*, Win32 Binary without crypto applies) from http://httpd.apache.org/download.cgi
# Run the installer wizard and click through each step until you reach the Server Information window and give the options below respectively and in the given order in each of the fields, unless you have any specific requirements as to how your web server is setup:
## localhost,
## localhost and
## admin@localhost
# Click through the wizard which will install and start the apache web server as a windows service.
# In the windows status bar you will now see a pink colored feather with a green colored play button indicating Apache is up and running. Point your browser to http://localhost/ and you should get a page indicating its working.
# Let us now go to the location where Apache is installed which commonly is at C:\Program Files\Apache Software Foundation\Apache2.2 and go through the various directories
## bin - contains the various binary files some of which are listed below. In order to access these applications, most of which are command based, we would need to add the path to the bin directory in our global PATH variable. To do that right click on My Computer > Properties > Advanced > Environments Variables and in the System Variables list locate and select the Variable PATH and click on Edit and add a trailing a semi-colon, if not already there, followed by the absolute path to your bin directory. And click out from the System Properties dialogue by accepting.
### httpd.exe which is the Apache webserver itself, which is spawned to several child processes while serving as many simultaneous incoming clients requests as required by MaxClients directive;
### ab.exe is a benchmarking tool that comes with Apache allowing you to see how well your application can perform per time unit
## conf - folder where various configuration files are located of which the following are of most interest in our case
### httpd.conf - most of the server directives are located in this file and for easy access you should associate the .conf file type with a user friendly editor, i.e. anything other than the default Notepad.
### extra\httpd-vhosts.conf - contains directives that would allow you use your local server as virtual host, i.e. able to run several servers on your PC. One usage scenario is that during a development phase if you want to map the actual domain you are working for to your local copy, you would be able to do so by making minor tweaks in this file. We will discuss this in more detail below.
## htdocs - the default web server root, this is where the http://localhost/ is mapped if you don't reconfigure it.
## logs - access and error logs, when trying to address various issues related to your server or even your application
===Virtual hosting===

===Resources===
* http://httpd.apache.org/docs/2.2/ reference documentation

==PHP setup==
# Download PHP from http://windows.php.net/download/ and choose commonly VC6 x86 Thread Safe in Zip format. The various options have to do with how the PHP code base was compiled to binary and is probably nothing you should worry about for now.
# Create a folder under your C:\Program Files\ (or wherever your program directory is located) a folder called PHP.
# Locate your downloaded Zip file and move it to the newly created folder and unpack it directly into the folder.
# Let us now add the PHP path to our global PATH variable by following the instruction above

===Configuring PHP===
The configuration amounts to editing the php.ini file. A sample file for different scenarios are already in your PHP folder. Let us rename php.ini-development to php.ini and open it in your favorite text editor. The common values to tweak are as follows and all of these variables are well documented in the php.ini file (please note that this is a server wide setting applying to all your projects):
* max_execution_time - whenever you have scripts that run for too long and the server returns various unexpected results which you think is due to not being able to run through the whole process
* memory_limit
* error_reporting
* display_errors
* log_errors - a variable you would need to take note of in production scenarios
* upload_tmp_dir
* upload_max_filesize
* extension_dir - in order to avoid complications we will point out the directory where the following extensions are located by uncommenting this variable and assign the absolute location of the folder, and the complete line should read as follows
<pre>
extension_dir = "C:\Program Files\PHP\ext"
</pre>
* Dynamic extensions section contains various additional modules that you want to be loaded with, and the commented once are those that comes prepackaged with PHP and can be found in the ext directory in your PHP folder. If you want to activate any just remove the commenting as you should do with the following extensions:
** php_curl.dll
** php_gd2.dll
** php_mbstring.dll
** php_mysql.dll
** php_mysqli.dll
** php_pdo.dll
** php_pdo_mysql.dll
** php_xsl.dll
* session.save_path

===Configuring Apache to work with PHP===
Now that we have configured PHP to work as we want it, lets go to Apache and do the same.
* Open httpd.conf. and in the "Dynamic Shared Object (DSO) Support" section add the following directives (if you have located your PHP folder differently do make corresponding change for php5apache2_2.dll below):
<pre>
LoadModule php5_module "C:/Program Files/PHP/php5apache2_2.dll"
AddType application/x-httpd-php .php
</pre>
* In the DirectoryIndex add index.php and index.htm as possible files to serve when directory is requested as follows
<pre>
DirectoryIndex index.html index.htm index.php
</pre>.
* At the end of the file add the following line which will point out where the php.ini file is located
<pre>
PHPIniDir "C:/Program Files/PHP"
</pre>

===Restart and test PHP===
As soon as you make any change to any of php.ini or httpd.conf or any other configuration files you need to restart Apache to see the actual effect of the changes. So lets now restart Apache by using the Apache Monitor tool you can find in your Windows status bar. Hopefully you are not prompted with any dialogues and the Apache Monitor continues to run green.

We will now make a test that PHP is working. Go to your web servers document root (in the default case C:\Program Files\Apache Software Foundation\Apache2.2\htdocs) and add a file called phpinfo.php with the following content:

<pre>
<?php
phpinfo();
phpinfo(INFO_MODULES);
?>
</pre>

This will render a page containing information about your PHP setup and about the various modules/extensions that are currently loaded. Point now your browser to http://localhost/phpinfo.php.

===Installing and configuring xdebug===
# Point your browser to http://www.xdebug.org/find-binary.php. This page will assist you to find the latest suitable version of xdebug.
# Copy the entire page of the phpinfo page we ran above and paste it into the textarea and follow the instructions provided to install
===Resources===
* http://www.php.net/docs.php excellent and up to date documentation with valuable additional comments from users. Also a downloadable versions are available.
* http://devzone.zend.com/article/2803 excellent and in depth tutorial on debugging with xdebug
* http://xdebug.org/docs/ xdebug reference documentation

Setting up Apache, PHP and MySQL manually

2010-05-27T01:07:40Z

PtrNrs: /* MySQL setup */

WIP
==Overview==
Here follows a brief overview of the steps to setup a Apache, PHP, MySQL in a Windows environment and also refer to various related tools to maintain and work with most of the tasks related to Joomla!.

In order to make the instruction clear and succinct, we will assume that wherever we are not stating any explicit instruction, you will let the default setup paths apply without modification.

===Resources===
* http://docs.joomla.org/Setting_up_your_workstation_for_Joomla!_development exhaustive resource on all things related to the topic of this document and more. Geared towards using packaged AMP stacks.

==MySQL setup==
# Download the appropriate MySQL installer option for your platform (commonly x86, 32-bit) from http://www.mysql.com/downloads/mysql/
# Start the installation and choose Custom installation path
# Click through the whole installation process and click Finish
# You will now be presented with the "MySQL Server Instance Configuration Wizard"
## Make sure that the "Standard Configuration" is selected and go to Next
## In the next window Check for "Include Bin Directory in Windows PATH". By doing this you will be able to access the various MySQL utilities from the command line.
## In the next window you will be able to create password for your root MySQL user, the user with highest access level on your server.
## In the next and final window all the changes you have configured until now will be saved when you press the Execute button, and the windows service for this instance will be started.

===Notes===
# In order to make the instruction as accessible as possible we skipped a number of configuration scenarios of your MySQL instance, such as being able to relocate your database files etc. This and more is outlined in http://dev.mysql.com/doc/refman/5.1/en/mysql-config-wizard.html
# MySQL installs as default with a STRICT mode which might give rise to some errors when using extensions or applications that haven't considered this. Refer to this resource for more on this: http://dev.mysql.com/doc/refman/5.0/en/server-sql-mode.html

===Resources===
* HeidiSQL: http://www.heidisql.com/ easy to use and extensible full-client replacement of phpMyAdmin under constant development
* MySQL Workbench: http://www.mysql.com/downloads/workbench/ consists of various tools among which you will appreciate the Administrator, which helps you to configure your MySQL instance and requires .Net framework http://www.microsoft.com/net/
* phpMyAdmin: http://www.phpmyadmin.net/ , powerful web based MySQL client for administrating anything related to MySQL
* MySQL documentation http://dev.mysql.com/doc/ available in different formats

==Apache setup==
# Download the installer of your preference. Currently you should aim for version 2.2.*, Win32 Binary without crypto applies) from http://httpd.apache.org/download.cgi
# Run the installer wizard and click through each step until you reach the Server Information window and give the options below respectively and in the given order in each of the fields, unless you have any specific requirements as to how your web server is setup:
## localhost,
## localhost and
## admin@localhost
# Click through the wizard which will install and start the apache web server as a windows service.
# In the windows status bar you will now see a pink colored feather with a green colored play button indicating Apache is up and running. Point your browser to http://localhost/ and you should get a page indicating its working.
# Let us now go to the location where Apache is installed which commonly is at C:\Program Files\Apache Software Foundation\Apache2.2 and go through the various directories
## bin - contains the various binary files some of which are listed below. In order to access these applications, most of which are command based, we would need to add the path to the bin directory in our global PATH variable. To do that right click on My Computer > Properties > Advanced > Environments Variables and in the System Variables list locate and select the Variable PATH and click on Edit and add a trailing a semi-colon, if not already there, followed by the absolute path to your bin directory. And click out from the System Properties dialogue by accepting.
### httpd.exe which is the Apache webserver itself, which is spawned to several child processes while serving as many simultaneous incoming clients requests as required by MaxClients directive;
### ab.exe is a benchmarking tool that comes with Apache allowing you to see how well your application can perform per time unit
## conf - folder where various configuration files are located of which the following are of most interest in our case
### httpd.conf - most of the server directives are located in this file and for easy access you should associate the .conf file type with a user friendly editor, i.e. anything other than the default Notepad.
### extra\httpd-vhosts.conf - contains directives that would allow you use your local server as virtual host, i.e. able to run several servers on your PC. One usage scenario is that during a development phase if you want to map the actual domain you are working for to your local copy, you would be able to do so by making minor tweaks in this file. We will discuss this in more detail below.
## htdocs - the default web server root, this is where the http://localhost/ is mapped if you don't reconfigure it.
## logs - access and error logs, when trying to address various issues related to your server or even your application
===Virtual hosting===

===Resources===
* http://httpd.apache.org/docs/2.2/ reference documentation

==PHP setup==
# Download PHP from http://windows.php.net/download/ and choose commonly VC6 x86 Thread Safe in Zip format. The various options have to do with how the PHP code base was compiled to binary and is probably nothing you should worry about for now.
# Create a folder under your C:\Program Files\ (or wherever your program directory is located) a folder called PHP.
# Locate your downloaded Zip file and move it to the newly created folder and unpack it directly into the folder.
# Let us now add the PHP path to our global PATH variable by following the instruction above

===Configuring PHP===
The configuration amounts to editing the php.ini file. A sample file for different scenarios are already in your PHP folder. Let us rename php.ini-development to php.ini and open it in your favorite text editor. The common values to tweak are as follows and all of these variables are well documented in the php.ini file (please note that this is a server wide setting applying to all your projects):
* max_execution_time - whenever you have scripts that run for too long and the server returns various unexpected results which you think is due to not being able to run through the whole process
* memory_limit
* error_reporting
* display_errors
* log_errors - a variable you would need to take note of in production scenarios
* upload_tmp_dir
* upload_max_filesize
* extension_dir - in order to avoid complications we will point out the directory where the following extensions are located by uncommenting this variable and assign the absolute location of the folder, and the complete line should read as follows
<pre>
extension_dir = "C:\Program Files\PHP\ext"
</pre>
* Dynamic extensions section contains various additional modules that you want to be loaded with, and the commented once are those that comes prepackaged with PHP and can be found in the ext directory in your PHP folder. If you want to activate any just remove the commenting as you should do with the following extensions:
** php_curl.dll
** php_gd2.dll
** php_mbstring.dll
** php_mysql.dll
** php_mysqli.dll
** php_pdo.dll
** php_pdo_mysql.dll
** php_xsl.dll
* session.save_path

===Configuring Apache to work with PHP===
Now that we have configured PHP to work as we want it, lets go to Apache and do the same.
* Open httpd.conf. and in the "Dynamic Shared Object (DSO) Support" section add the following directives (if you have located your PHP folder differently do make corresponding change for php5apache2_2.dll below):
<pre>
LoadModule php5_module "C:/Program Files/PHP/php5apache2_2.dll"
AddType application/x-httpd-php .php
</pre>
* In the DirectoryIndex add index.php as possible file to serve when directory is requested as follows
<pre>
DirectoryIndex index.html index.htm index.php
</pre>.
* At the end of the file add the following line which will point out where the php.ini file is located
<pre>
PHPIniDir "C:/Program Files/PHP"
</pre>

===Restart and test PHP===
As soon as you make any change to any of php.ini or httpd.conf or any other configuration files you need to restart Apache to see the actual effect of the changes. So lets now restart Apache by using the Apache Monitor tool you can find in your Windows status bar. Hopefully you are not prompted with any dialogues and the Apache Monitor continues to run green.

We will now make a test that PHP is working. Go to your web servers document root (in the default case C:\Program Files\Apache Software Foundation\Apache2.2\htdocs) and add a file called phpinfo.php with the following content:

<pre>
<?php
phpinfo();
phpinfo(INFO_MODULES);
?>
</pre>

This will render a page containing information about your PHP setup and about the various modules/extensions that are currently loaded. Point now your browser to http://localhost/phpinfo.php.

===Installing and configuring xdebug===
# Point your browser to http://www.xdebug.org/find-binary.php. This page will assist you to find the latest suitable version of xdebug.
# Copy the entire page of the phpinfo page we ran above and paste it into the textarea and follow the instructions provided to install
===Resources===
* http://www.php.net/docs.php excellent and up to date documentation with valuable additional comments from users. Also a downloadable versions are available.
* http://devzone.zend.com/article/2803 excellent and in depth tutorial on debugging with xdebug
* http://xdebug.org/docs/ xdebug reference documentation

Talk:Setting up your workstation for extension development (build with Phing)

2010-04-04T07:39:33Z

PtrNrs: /* Tips & Traps for Eclipse/SVN/JoomlaCode */

This article fails to explain the content of the original package before it is installed, way before setting up PHING needs improvement.

Quite unfair comment that. Mark's previous two articles cover the setup of XAMPP/Eclipse/Joomla in comprehensive detail.
http://docs.joomla.org/Setting_up_your_workstation_for_Joomla!_development
http://docs.joomla.org/Setting_up_your_workstation_for_Joomla%21_development_--_Part_2
([[User:PtrNrs|Pete Nurse]] 00:43, 16 March 2010 (UTC))

===Tips & Traps for Eclipse/SVN/JoomlaCode===
These are issues that I've come up against. Maybe my solutions are not definitively correct.

*Good JoomlaCode resources (and they're hard to find!) are at:-

::[http://forum.joomla.org/viewforum.php?f=406 forum.joomla.org: JoomlaCode.org]

::[http://docs.joomla.org/JoomlaCode_FAQs docs.joomla.org: JoomlaCode FAQs (mostly admin stuff)]

::[http://joomlacode.org/gf/project/attachments/forum/?action=ForumBrowse&forum_id=7017 joomlacode.org: FAQs]

*To create a JoomlaCode account, go to the [http://joomlacode.org/gf/project/ JoomlaCode Project page] and click on the "''add new Project''" bottom at the very bottom of the page. In time your application will be reviewed and (hopefully) approved.

*To initially put your project under SVN version control, right click the project folder and then select ''Team->Share Project...''.

*Eclipse will not let you upload to the root folder of your JoomlaCode Project. Instead, upload to a folder with the same name as your Eclipse project.

*When deleting a folder in Eclipse's Explorer window and then commit by right clicking and selecting ''Team->Commit'' you can (do?) get the following error:-
::''svn:Commit failed item . . . is out of date''
:To overcome this, delete the folder in the SVN repository (''Window->Show View->SVN Respositories'') first and then right click on teh folder and select ''Team->Update to HEAD''.

*Under some circumstances, you might find that you cannot write to the reposisitory receiving the following error:-
::''svn: Server sent unexpected return value (403 Forbidden) in response to MKACTIVITY request''
:This may be due to a problem with password caching. The following page shows how to clear the cached passwords:-
::http://help.collab.net/index.jsp?topic=/faq/clear_old_password.html
--[[User:PtrNrs|Pete Nurse]] 01:35, 16 March 2010 (UTC)

*You can get a "Commit failed . . . Item is out of date" error when deleting (&or moving?) a folder and then trying to commit. The work-around (from http://nickhumphrey.net/showthread.php?p=3277) is:-
:Delete the folders;
:Team->Synchronize with Repository;
:Team->Commit
--[[User:PtrNrs|Pete Nurse]] 07:37, 4 April 2010 (UTC)

Talk:Setting up your workstation for extension development (build with Phing)

2010-04-04T07:37:10Z

PtrNrs: /* Tips & Traps for Eclipse/SVN/JoomlaCode */

This article fails to explain the content of the original package before it is installed, way before setting up PHING needs improvement.

Quite unfair comment that. Mark's previous two articles cover the setup of XAMPP/Eclipse/Joomla in comprehensive detail.
http://docs.joomla.org/Setting_up_your_workstation_for_Joomla!_development
http://docs.joomla.org/Setting_up_your_workstation_for_Joomla%21_development_--_Part_2
([[User:PtrNrs|Pete Nurse]] 00:43, 16 March 2010 (UTC))

===Tips & Traps for Eclipse/SVN/JoomlaCode===
These are issues that I've come up against. Maybe my solutions are not definitively correct.

*Good JoomlaCode resources (and they're hard to find!) are at:-

::[http://forum.joomla.org/viewforum.php?f=406 forum.joomla.org: JoomlaCode.org]

::[http://docs.joomla.org/JoomlaCode_FAQs docs.joomla.org: JoomlaCode FAQs (mostly admin stuff)]

::[http://joomlacode.org/gf/project/attachments/forum/?action=ForumBrowse&forum_id=7017 joomlacode.org: FAQs]

*To create a JoomlaCode account, go to the [http://joomlacode.org/gf/project/ JoomlaCode Project page] and click on the "''add new Project''" bottom at the very bottom of the page. In time your application will be reviewed and (hopefully) approved.

*To initially put your project under SVN version control, right click the project folder and then select ''Team->Share Project...''.

*Eclipse will not let you upload to the root folder of your JoomlaCode Project. Instead, upload to a folder with the same name as your Eclipse project.

*When deleting a folder in Eclipse's Explorer window and then commit by right clicking and selecting ''Team->Commit'' you can (do?) get the following error:-
::''svn:Commit failed item . . . is out of date''
:To overcome this, delete the folder in the SVN repository (''Window->Show View->SVN Respositories'') first and then right click on teh folder and select ''Team->Update to HEAD''.

*Under some circumstances, you might find that you cannot write to the reposisitory receiving the following error:-
::''svn: Server sent unexpected return value (403 Forbidden) in response to MKACTIVITY request''
:This may be due to a problem with password caching. The following page shows how to clear the cached passwords:-
::http://help.collab.net/index.jsp?topic=/faq/clear_old_password.html
--[[User:PtrNrs|Pete Nurse]] 01:35, 16 March 2010 (UTC)

*As noted at http://nickhumphrey.net/showthread.php?p=3277, you can get a "Commit failed . . . Item is out of date" error when perfectly innocently deleting a folder and then trying to commit. The solution (work-around?) is:-
:Delete the folders;
:Team->Synchronize with Repository;
:Team->Commit
--[[User:PtrNrs|Pete Nurse]] 07:37, 4 April 2010 (UTC)

Talk:Setting up your workstation for extension development (build with Phing)

2010-03-16T03:10:14Z

PtrNrs:

Talk:Setting up your workstation for extension development (build with Phing)

2010-03-16T03:09:09Z

PtrNrs:

This article fails to explain the content of the original package before it is installed, way before setting up PHING needs improvement.

Quite unfair comment that. Mark's previous two articles cover the setup of XAMPP/Eclipse/Joomla in comprehensive detail.
http://docs.joomla.org/Setting_up_your_workstation_for_Joomla!_development
http://docs.joomla.org/Setting_up_your_workstation_for_Joomla%21_development_--_Part_2
([[User:PtrNrs|Pete Nurse]] 00:43, 16 March 2010 (UTC))

===Tips & Traps for Eclipse/SVN/JoomlaCode===
These are issues that I've come up against. Maybe my solutions are not definitively correct.

*Good JoomlaCode resources (and they're hard to find!) are at:-

::[http://forum.joomla.org/viewforum.php?f=406 forum.joomla.org: JoomlaCode.org]

::[http://docs.joomla.org/JoomlaCode_FAQs docs.joomla.org: JoomlaCode FAQs]

::[http://joomlacode.org/gf/project/attachments/forum/?action=ForumBrowse&forum_id=7017 joomlacode.org: FAQs]

*To create a JoomlaCode account, go to the [http://joomlacode.org/gf/project/ JoomlaCode Project page] and click on the "''add new Project''" bottom at the very bottom of the page. In time your application will be reviewed and (hopefully) approved.

*To initially put your project under SVN version control, right click the project folder and then select ''Team->Share Project...''.

*Eclipse will not let you upload to the root folder of your JoomlaCode Project. Instead, upload to a folder with the same name as your Eclipse project.

*When deleting a folder in Eclipse's Explorer window and then commit by right clicking and selecting ''Team->Commit'' you can (do?) get the following error:-
::''svn:Commit failed item . . . is out of date''
:To overcome this, delete the folder in the SVN repository (''Window->Show View->SVN Respositories'') first and then right click on teh folder and select ''Team->Update to HEAD''.

*Under some circumstances, you might find that you cannot write to the reposisitory receiving the following error:-
::''svn: Server sent unexpected return value (403 Forbidden) in response to MKACTIVITY request''
:This may be due to a problem with password caching. The following page shows how to clear the cached passwords:-
::http://help.collab.net/index.jsp?topic=/faq/clear_old_password.html
--[[User:PtrNrs|Pete Nurse]] 01:35, 16 March 2010 (UTC)

Talk:Setting up your workstation for extension development (build with Phing)

2010-03-16T03:07:38Z

PtrNrs:

This article fails to explain the content of the original package before it is installed, way before setting up PHING needs improvement.

Quite unfair comment that. Mark's previous two articles cover the setup of XAMPP/Eclipse/Joomla in comprehensive detail.
http://docs.joomla.org/Setting_up_your_workstation_for_Joomla!_development
http://docs.joomla.org/Setting_up_your_workstation_for_Joomla%21_development_--_Part_2
([[User:PtrNrs|Pete Nurse]] 00:43, 16 March 2010 (UTC))

===Tips & Traps for Eclipse/SVN/JoomlaCode===
These are issues that I've come up against. Maybe my solutions are not definitively correct.

*Good JoomlaCode resources (and they're hard to find!) are at:-

::[http://forum.joomla.org/viewforum.php?f=406 Joomla Forum » Joomla! Official Sites & Infrastructure » Sites & Infrastructure - Feedback/Information » JoomlaCode.org]

::[http://docs.joomla.org/JoomlaCode_FAQs JoomlaCode FAQs in doc.joomla.org]

::[http://joomlacode.org/gf/project/attachments/forum/?action=ForumBrowse&forum_id=7017 FAQs inside JoomlaCode]

*To create a JoomlaCode account, go to the [http://joomlacode.org/gf/project/ JoomlaCode Project page] and click on the "''add new Project''" bottom at the very bottom of the page. In time your application will be reviewed and (hopefully) approved.

*To initially put your project under SVN version control, right click the project folder and then select ''Team->Share Project...''.

*Eclipse will not let you upload to the root folder of your JoomlaCode Project. Instead, upload to a folder with the same name as your Eclipse project.

*When deleting a folder in Eclipse's Explorer window and then commit by right clicking and selecting ''Team->Commit'' you can (do?) get the following error:-
::''svn:Commit failed item . . . is out of date''
:To overcome this, delete the folder in the SVN repository (''Window->Show View->SVN Respositories'') first and then right click on teh folder and select ''Team->Update to HEAD''.

*Under some circumstances, you might find that you cannot write to the reposisitory receiving the following error:-
::''svn: Server sent unexpected return value (403 Forbidden) in response to MKACTIVITY request''
:This may be due to a problem with password caching. The following page shows how to clear the cached passwords:-
::http://help.collab.net/index.jsp?topic=/faq/clear_old_password.html
--[[User:PtrNrs|Pete Nurse]] 01:35, 16 March 2010 (UTC)

Talk:Setting up your workstation for extension development (build with Phing)

2010-03-16T02:41:03Z

PtrNrs:

This article fails to explain the content of the original package before it is installed, way before setting up PHING needs improvement.

Quite unfair comment that. Mark's previous two articles cover the setup of XAMPP/Eclipse/Joomla in comprehensive detail.
http://docs.joomla.org/Setting_up_your_workstation_for_Joomla!_development
http://docs.joomla.org/Setting_up_your_workstation_for_Joomla%21_development_--_Part_2
([[User:PtrNrs|Pete Nurse]] 00:43, 16 March 2010 (UTC))

===Tips & Traps for Eclipse/SVN/JoomlaCode===
These are issues that I've come up against. Maybe my solutions are not definitively correct.

*The Joomla forum about joomlacode.org is at
::[http://forum.joomla.org/viewforum.php?f=406 Board index » Joomla! Official Sites & Infrastructure » Sites & Infrastructure - Feedback/Information » JoomlaCode.org]

*To create a JoomlaCode account, go to the [http://joomlacode.org/gf/project/ JoomlaCode Project page] and click on the "''add new Project''" bottom at the very bottom of the page. In time your application will be reviewed and (hopefully) approved.

*To initially put your project under SVN version control, right click the project folder and then select ''Team->Share Project...''.

*Eclipse will not let you upload to the root folder of your JoomlaCode Project. Instead, upload to a folder with the same name as your Eclipse project.

*When deleting a folder in Eclipse's Explorer window and then commit by right clicking and selecting ''Team->Commit'' you can (do?) get the following error:-
::''svn:Commit failed item . . . is out of date''
:To overcome this, delete the folder in the SVN repository (''Window->Show View->SVN Respositories'') first and then right click on teh folder and select ''Team->Update to HEAD''.

*Under some circumstances, you might find that you cannot write to the reposisitory receiving the following error:-
::''svn: Server sent unexpected return value (403 Forbidden) in response to MKACTIVITY request''
:This may be due to a problem with password caching. The following page shows how to clear the cached passwords:-
::http://help.collab.net/index.jsp?topic=/faq/clear_old_password.html
--[[User:PtrNrs|Pete Nurse]] 01:35, 16 March 2010 (UTC)

Talk:Setting up your workstation for extension development (build with Phing)

2010-03-16T02:40:45Z

PtrNrs:

This article fails to explain the content of the original package before it is installed, way before setting up PHING needs improvement.

Quite unfair comment that. Mark's previous two articles cover the setup of XAMPP/Eclipse/Joomla in comprehensive detail.
http://docs.joomla.org/Setting_up_your_workstation_for_Joomla!_development
http://docs.joomla.org/Setting_up_your_workstation_for_Joomla%21_development_--_Part_2
([[User:PtrNrs|Pete Nurse]] 00:43, 16 March 2010 (UTC))

===Tips & Traps for Eclipse/SVN/JoomlaCode===
These are issues that I've come up against. Maybe my solutions are not definitively correct.

*The Joomla forum about joomlacode.org is at
[http://forum.joomla.org/viewforum.php?f=406 Board index » Joomla! Official Sites & Infrastructure » Sites & Infrastructure - Feedback/Information » JoomlaCode.org]

*To create a JoomlaCode account, go to the [http://joomlacode.org/gf/project/ JoomlaCode Project page] and click on the "''add new Project''" bottom at the very bottom of the page. In time your application will be reviewed and (hopefully) approved.

*To initially put your project under SVN version control, right click the project folder and then select ''Team->Share Project...''.

*Eclipse will not let you upload to the root folder of your JoomlaCode Project. Instead, upload to a folder with the same name as your Eclipse project.

*When deleting a folder in Eclipse's Explorer window and then commit by right clicking and selecting ''Team->Commit'' you can (do?) get the following error:-
::''svn:Commit failed item . . . is out of date''
:To overcome this, delete the folder in the SVN repository (''Window->Show View->SVN Respositories'') first and then right click on teh folder and select ''Team->Update to HEAD''.

*Under some circumstances, you might find that you cannot write to the reposisitory receiving the following error:-
::''svn: Server sent unexpected return value (403 Forbidden) in response to MKACTIVITY request''
:This may be due to a problem with password caching. The following page shows how to clear the cached passwords:-
::http://help.collab.net/index.jsp?topic=/faq/clear_old_password.html
--[[User:PtrNrs|Pete Nurse]] 01:35, 16 March 2010 (UTC)

Talk:Setting up your workstation for extension development (build with Phing)

2010-03-16T02:40:09Z

PtrNrs:

This article fails to explain the content of the original package before it is installed, way before setting up PHING needs improvement.

Quite unfair comment that. Mark's previous two articles cover the setup of XAMPP/Eclipse/Joomla in comprehensive detail.
http://docs.joomla.org/Setting_up_your_workstation_for_Joomla!_development
http://docs.joomla.org/Setting_up_your_workstation_for_Joomla%21_development_--_Part_2
([[User:PtrNrs|Pete Nurse]] 00:43, 16 March 2010 (UTC))

===Tips & Traps for Eclipse/SVN/JoomlaCode===
These are issues that I've come up against. Maybe my solutions are not definitively correct.

*The Joomla forum about joomlacode.org is at
[http://forum.joomla.org/viewforum.php?f=406 Board index»Joomla! Official Sites&Infrastructure»Sites&Infrastructure - Feedback/Information»JoomlaCode.org]

*To create a JoomlaCode account, go to the [http://joomlacode.org/gf/project/ JoomlaCode Project page] and click on the "''add new Project''" bottom at the very bottom of the page. In time your application will be reviewed and (hopefully) approved.

*To initially put your project under SVN version control, right click the project folder and then select ''Team->Share Project...''.

*Eclipse will not let you upload to the root folder of your JoomlaCode Project. Instead, upload to a folder with the same name as your Eclipse project.

*When deleting a folder in Eclipse's Explorer window and then commit by right clicking and selecting ''Team->Commit'' you can (do?) get the following error:-
::''svn:Commit failed item . . . is out of date''
:To overcome this, delete the folder in the SVN repository (''Window->Show View->SVN Respositories'') first and then right click on teh folder and select ''Team->Update to HEAD''.

*Under some circumstances, you might find that you cannot write to the reposisitory receiving the following error:-
::''svn: Server sent unexpected return value (403 Forbidden) in response to MKACTIVITY request''
:This may be due to a problem with password caching. The following page shows how to clear the cached passwords:-
::http://help.collab.net/index.jsp?topic=/faq/clear_old_password.html
--[[User:PtrNrs|Pete Nurse]] 01:35, 16 March 2010 (UTC)

Talk:Setting up your workstation for extension development (build with Phing)

2010-03-16T02:00:03Z

PtrNrs: /* Tips & Traps for Eclipse/SVN/JoomlaCode */

This article fails to explain the content of the original package before it is installed, way before setting up PHING needs improvement.

Quite unfair comment that. Mark's previous two articles cover the setup of XAMPP/Eclipse/Joomla in comprehensive detail.
http://docs.joomla.org/Setting_up_your_workstation_for_Joomla!_development
http://docs.joomla.org/Setting_up_your_workstation_for_Joomla%21_development_--_Part_2
([[User:PtrNrs|Pete Nurse]] 00:43, 16 March 2010 (UTC))

===Tips & Traps for Eclipse/SVN/JoomlaCode===
These are issues that I've come up against. Maybe my solutions are not definitively correct.

*To create a JoomlaCode account, go to the [http://joomlacode.org/gf/project/ JoomlaCode Project page] and click on the "''add new Project''" bottom at the very bottom of the page. In time your application will be reviewed and (hopefully) approved.

*To initially put your project under SVN version control, right click the project folder and then select ''Team->Share Project...''.

*Eclipse will not let you upload to the root folder of your JoomlaCode Project. Instead, upload to a folder with the same name as your Eclipse project.

*When deleting a folder in Eclipse's Explorer window and then commit by right clicking and selecting ''Team->Commit'' you can (do?) get the following error:-
::''svn:Commit failed item . . . is out of date''
:To overcome this, delete the folder in the SVN repository (''Window->Show View->SVN Respositories'') first and then right click on teh folder and select ''Team->Update to HEAD''.

*Under some circumstances, you might find that you cannot write to the reposisitory receiving the following error:-
::''svn: Server sent unexpected return value (403 Forbidden) in response to MKACTIVITY request''
:This may be due to a problem with password caching. The following page shows how to clear the cached passwords:-
::http://help.collab.net/index.jsp?topic=/faq/clear_old_password.html
--[[User:PtrNrs|Pete Nurse]] 01:35, 16 March 2010 (UTC)

Talk:Setting up your workstation for extension development (build with Phing)

2010-03-16T01:57:23Z

PtrNrs: /* Tips & Traps for Eclipse/SVN/JoomlaCode */

This article fails to explain the content of the original package before it is installed, way before setting up PHING needs improvement.

Quite unfair comment that. Mark's previous two articles cover the setup of XAMPP/Eclipse/Joomla in comprehensive detail.
http://docs.joomla.org/Setting_up_your_workstation_for_Joomla!_development
http://docs.joomla.org/Setting_up_your_workstation_for_Joomla%21_development_--_Part_2
([[User:PtrNrs|Pete Nurse]] 00:43, 16 March 2010 (UTC))

===Tips & Traps for Eclipse/SVN/JoomlaCode===
These are issues that I've come up against. Maybe my solutions are not definitively correct.

*To create a JoomlaCode account, go to the [http://joomlacode.org/gf/project/ JoomlaCode Project page] and click on the "''add new Project''" bottom at the very bottom of the page. In time your application will be reviewed and (hopefully) approved.

*To initially put your project under SVN version control, you right click the project folder and then select ''Team->Share Project...'', you may not upload to the root folder of your JoomlaCode Project. It is easier to upload to a folder with the same name as your Eclipse project.

*When deleting a folder in Eclipse's Explorer window and then commit by right clicking and selecting ''Team->Commit'' you can (do?) get the following error:-
::''svn:Commit failed item . . . is out of date''
:To overcome this, delete the folder in the SVN repository (''Window->Show View->SVN Respositories'') first and then right click on teh folder and select ''Team->Update to HEAD''.

*Under some circumstances, you might find that you cannot write to the reposisitory receiving the following error:-
::''svn: Server sent unexpected return value (403 Forbidden) in response to MKACTIVITY request''
:This may be due to a problem with password caching. The following page shows how to clear the cached passwords:-
::http://help.collab.net/index.jsp?topic=/faq/clear_old_password.html
--[[User:PtrNrs|Pete Nurse]] 01:35, 16 March 2010 (UTC)

Talk:Setting up your workstation for extension development (build with Phing)

2010-03-16T01:35:43Z

PtrNrs: /* Tips & Traps for Eclipse/SVN/JoomlaCode */

Talk:Setting up your workstation for extension development (build with Phing)

2010-03-16T01:34:34Z

PtrNrs: /* Tips & Traps for Eclipse/SVN/JoomlaCode */

Talk:Setting up your workstation for extension development (build with Phing)

2010-03-16T01:33:56Z

PtrNrs: /* Tips & Traps for Eclipse/SVN/JoomlaCode */

Talk:Setting up your workstation for extension development (build with Phing)

2010-03-16T01:32:11Z

PtrNrs: /* Tips & Traps for Eclipse/SVN/JoomlaCode */

Talk:Setting up your workstation for extension development (build with Phing)

2010-03-16T01:08:41Z

PtrNrs: /* Tips & Traps for Eclipse/SVN/JoomlaCode */

Talk:Setting up your workstation for extension development (build with Phing)

2010-03-16T01:08:09Z

PtrNrs: /* Tips & Traps for Eclipse/SVN/JoomlaCode */

Talk:Setting up your workstation for extension development (build with Phing)

2010-03-16T01:04:48Z

PtrNrs: /* Tips & Traps for Eclipse/SVN/JoomlaCode */

Talk:Setting up your workstation for extension development (build with Phing)

2010-03-16T01:00:23Z

PtrNrs: /* Tips & Traps for Eclipse/SVN/JoomlaCode */

Talk:Setting up your workstation for extension development (build with Phing)

2010-03-16T00:59:48Z

PtrNrs:

Talk:Setting up your workstation for extension development (build with Phing)

2010-03-16T00:49:36Z

PtrNrs:

Talk:Setting up your workstation for extension development (build with Phing)

2010-03-16T00:46:43Z

PtrNrs:

Talk:Setting up your workstation for extension development (build with Phing)

2010-03-16T00:45:43Z

PtrNrs:

Talk:Setting up your workstation for extension development (build with Phing)

2010-03-16T00:43:59Z

PtrNrs:

File:Subclipse update site 1.6.png

2009-04-16T22:28:20Z

PtrNrs:

File:Eclipse install update 1.6.png

2009-04-16T22:25:51Z

PtrNrs:

File:Eclipse install update2 1.6.png

2009-04-16T22:25:02Z

PtrNrs: