Skip to main content
Jump to: navigation, search

Difference between revisions of "PDT/Testing Framework"

< PDT
(Resources)
(Mailing List and RSS)
Line 16: Line 16:
  
 
== Mailing List and RSS ==
 
== Mailing List and RSS ==
To get the most updated news, register php-unit-test@eclipse.org at
+
In order to be updated on test issues, register php-unit-test@eclipse.org at
 
[https://dev.eclipse.org/mailman/listinfo/php-unit-test https://dev.eclipse.org/mailman/listinfo/php-unit-test]
 
[https://dev.eclipse.org/mailman/listinfo/php-unit-test https://dev.eclipse.org/mailman/listinfo/php-unit-test]
 
<br>
 
<br>

Revision as of 17:14, 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

In order to be updated on test issues, 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.

Back to the top