Skip to main content
Jump to: navigation, search

Difference between revisions of "PDT/Testing Framework"

< PDT
(Unit Test Reports)
Line 16: Line 16:
  
 
== Unit Test Reports ==
 
== Unit Test Reports ==
Nightyly build reports include unit test results, the reports are locted under
+
Nightyly build reports include unit test results.<br>
/tools/php/downloads/reports/ folder, if you want to access one of the reports use: <br> <br>
+
http://download.eclipse.org/tools/php/downloads/reports/TEST-php''<Date>''.html <br>
+
  
for example [http://download.eclipse.org/tools/php/downloads/reports/TEST-php20070107.html]
+
Access to unit test results: <br>
 +
<pre>http://download.eclipse.org/tools/php/downloads/reports/TEST-php<Date>.html</pre><br>
 +
for example linking to http://download.eclipse.org/tools/php/downloads/reports/TEST-php20070107.html pops January 7th 2007 unit test results.

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

  • PDT Test Framework Tutorial - [2]

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