Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "PDT/Testing Framework"

< PDT
(Unit Test Reports)
Line 14: Line 14:
  
 
* [[List of components to unit test.]] <br>
 
* [[List of components to unit test.]] <br>
 +
 +
== 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 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 http://download.eclipse.org/tools/php/doenloads/rss/center.xml]
 +
 +
<br>
  
 
== Unit Test Reports ==
 
== Unit Test Reports ==

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

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.

Copyright © Eclipse Foundation, Inc. All Rights Reserved.