Skip to main content
Jump to: navigation, search

Difference between revisions of "PDT/Testing Framework"

< PDT
m
Line 16: Line 16:
  
 
* [[Migrating to PDT test framework based on Junit4 ]] <br>
 
* [[Migrating to PDT test framework based on Junit4 ]] <br>
 +
  
 
== Unit Test Arguments ==
 
== Unit Test Arguments ==
Line 24: Line 25:
 
| -DBenchmarkTests=true || Whether to enable various benchmark tests (may take a long time to run)
 
| -DBenchmarkTests=true || Whether to enable various benchmark tests (may take a long time to run)
 
|}
 
|}
 +
  
 
== Mailing List and RSS ==
 
== Mailing List and RSS ==

Revision as of 04:33, 14 July 2008

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


Unit Test Arguments

Argument Meaning
-DBenchmarkTests=true Whether to enable various benchmark tests (may take a long time to run)


Mailing List and RSS

In order to be updated on test issues, register pdt-unit-test@eclipse.org at https://dev.eclipse.org/mailman/listinfo/pdt-unit-test
also an RSS feed can show you bug status: http://download.eclipse.org/tools/pdt/downloads/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/drops/N<date>/results/TEST-php.html


for example http://download.eclipse.org/tools/php/downloads/drops/N20070113/results/TEST-php.html links to January 13th 2007 test results.

Back to the top