Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "PDT/Testing Framework"
< PDT
(→Resources) |
(→Resources) |
||
Line 9: | Line 9: | ||
== Resources == | == Resources == | ||
− | * | + | * [http://wiki.eclipse.org/images/2/20/JUnit_for_PHPIDE.zip PDT Test Framework Tutorial (zip)] <br> |
* [[The Three Test Suite Modes]] <br> | * [[The Three Test Suite Modes]] <br> |
Revision as of 17:12, 7 January 2007
Background
"Testing: Early, Often and Automated" (Extreme Programmin Explained by KENT BECK)
The PDT team has accepted the XP ([1]) two principles to increase the cost-effectiveness of testing: double checking and the Defect Cost Increase.
We release the "PDT test framework" that helps us write unit tests for PDT in a very fast way.
"The sooner you find a defect, the cheaper it is to fix".
Resources
Mailing List and RSS
To get the most updated news, register php-unit-test@eclipse.org at
https://dev.eclipse.org/mailman/listinfo/php-unit-test
also an RSS feed can show you the bug status: http://download.eclipse.org/tools/php/doenloads/rss/center.xml
Unit Test Reports
Nightyly build reports include unit test results.
Access to unit test results:
http://download.eclipse.org/tools/php/downloads/reports/TEST-php<Date>.html
for example linking to http://download.eclipse.org/tools/php/downloads/reports/TEST-php20070107.html pops January 7th 2007 unit test results.