Author: FrankStelzer Date: 2010-09-20 08:10:52 +0200 (Mon, 20 Sep 2010) New Revision: 30933
Modified: plugins/sfPHPUnit2Plugin/trunk/README plugins/sfPHPUnit2Plugin/trunk/package.xml Log: [sfPHPUnit2Plugin] prepearing version 0.9.1 Modified: plugins/sfPHPUnit2Plugin/trunk/README =================================================================== --- plugins/sfPHPUnit2Plugin/trunk/README 2010-09-20 06:05:16 UTC (rev 30932) +++ plugins/sfPHPUnit2Plugin/trunk/README 2010-09-20 06:10:52 UTC (rev 30933) @@ -154,7 +154,24 @@ Selenium tests behave like functional tests with additional Selenium support. The according base class for Selenium tests extends **PHPUnit_Extensions_SeleniumTestCase** of PHPUnit. Please refer to the official documentation of [PHPUnit](http://www.phpunit.de/manual/current/en/selenium.html) and [Selenium](http://seleniumhq.org/docs/) for detailed information and usage. +### Generate configuration ### +A default configuration file for any PHPUnit test runner could be generated by this new task: + $ ./symfony phpunit:generate-configuration +This generates a **phpunit.xml.dist** configuration file in the project's root dir. It inludes a default configuration, but you may modify this file for your project needs. This file is not generated by default during the generation of the user bootstrap files. Some developers may not like this generation and so it is optional. + +The [phpunit.xml.dist](http://www.phpunit.de/manual/3.4/en/appendixes.configuration.html) is quite powerful and you may change the behavior of PHPUnit completely with some additional options. For example you can enable or disable the colofur output or log the results of the test runners in a JUnit compatible file, which could be analysed by continuous integration tools like [Hudson](http://hudson-ci.org/) for example. + +Maybe you are used to integrate phpunit.xml files in your projects. But [Christian](http://test.ical.ly/2010/08/24/best-practice-how-to-ship-phpunit-configuration/) pointed out, that it is a good practise using the phpunit.xml.dist configuration file instead. The phpunit.xml.dist includes project wide configuration options. If you need individual configurations create a phpunit.xml and place your custom configuration there. PHPUnit will check the existence of a phpunit.xml file first and then it looks for the .dist file. + +**Important:** + +When a phpunit.xml(.dist) file is used in a project, the task for running all tests has to be run with this command + + $ ./symfony phpunit:test-all --configuration + +otherwise the configuration file not be read by PHPUnit. + ## Execute test cases ## ### Unit tests ### Executing a unit test: @@ -241,28 +258,7 @@ * You do not like the PHPUnit syntax? Use **$this->getTest()** to retrieve a instance of sfPHPUnitTest, which mimics the lime-like interface! * Use the **_start** and **_end** methods for doing something just before and after a test (please do not overwrite the setUp and tearDown methods)! * implement the **getApplication** method in your unit test and call **getContext** afterwards for creating an according sfContext instance - * add a ***[phpunit.xml.dist](http://test.ical.ly/2010/08/24/best-practice-how-to-ship-phpunit-configuration/)*** in the project's root dir for defining **default** configuration options for PHPUnit calls. Thanks [Christian](http://test.ical.ly/2010/08/24/best-practice-how-to-ship-phpunit-configuration/) for pointing this out :) - * add a ***[phpunit.xml](http://www.phpunit.de/manual/3.4/en/appendixes.configuration.html)*** in the project's root dir for defining **individual** configuration options for PHPUnit calls - - <phpunit - colors="true" - convertErrorsToExceptions="true" - convertNoticesToExceptions="true" - convertWarningsToExceptions="true" - stopOnFailure="true"> - - <testsuites> - <testsuite name="Unit Tests"> - <directory>test/phpunit/unit/</directory> - </testsuite> - <testsuite name="Functional Tests"> - <directory>test/phpunit/functional/</directory> - </testsuite> - </testsuites> - </phpunit> - - ## Snippets ## Loading fixtures in your test: Modified: plugins/sfPHPUnit2Plugin/trunk/package.xml =================================================================== --- plugins/sfPHPUnit2Plugin/trunk/package.xml 2010-09-20 06:05:16 UTC (rev 30932) +++ plugins/sfPHPUnit2Plugin/trunk/package.xml 2010-09-20 06:10:52 UTC (rev 30933) @@ -13,12 +13,12 @@ <email>[email protected]</email> <active>yes</active> </lead> - <date>2010-06-09</date> - <time>23:30:00</time> + <date>2010-09-20</date> + <time>08:00:00</time> <version> - <release>0.9.0</release> - <api>0.9.0</api> + <release>0.9.1</release> + <api>0.9.1</api> </version> <stability> @@ -40,6 +40,7 @@ <file role="data" name="bootstrap.tpl" /> <file role="data" name="functional_test.tpl" /> </dir> + <file role="data" name="phpunit.xml.dist.tpl" /> <dir name="selenium"> <file role="data" name="bootstrap.tpl" /> <file role="data" name="selenium_test.tpl" /> @@ -60,6 +61,7 @@ <file role="data" name="sfPHPUnitFunctionalTask.class.php" /> <file role="data" name="sfPHPUnitGenerateBaseTask.class.php" /> <file role="data" name="sfPHPUnitGenerateCompatTestTask.class.php" /> + <file role="data" name="sfPHPUnitGenerateConfigurationTask.class.php" /> <file role="data" name="sfPHPUnitGenerateFunctionalTestTask.class.php" /> <file role="data" name="sfPHPUnitGenerateSeleniumTestTask.class.php" /> <file role="data" name="sfPHPUnitGenerateUnitTestTask.class.php" /> @@ -109,7 +111,7 @@ <api>beta</api> </stability> <license uri="http://www.symfony-project.com/license";>MIT license</license> - <date>2010-06-09</date> + <date>2010-09-20</date> <license>MIT</license> <notes> * added task for generating the default phpunit.xml.dist configuration file -- You received this message because you are subscribed to the Google Groups "symfony SVN" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/symfony-svn?hl=en.
