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
Line 4: Line 4:
 
The PHPIDE team has excepted the XP ([http://www.extremeprogramming.org/]) two principles to increase the cost-effectiveness of testing: double checking and the Defect Cost Increase.<br>
 
The PHPIDE team has excepted the XP ([http://www.extremeprogramming.org/]) two principles to increase the cost-effectiveness of testing: double checking and the Defect Cost Increase.<br>
 
We release the "PHPIDE test framework" that helps us write unit tests for PHPIDE in fast way.
 
We release the "PHPIDE test framework" that helps us write unit tests for PHPIDE in fast way.
 +
<p>
 +
Remember: "The sooner you find a defect, the cheaper it is to fix".
 +
 +
 +
== How to ==
  
 
* [[PHPIDE test framework presentation]].
 
* [[PHPIDE test framework presentation]].
  
<p>
+
 
Remember: "The sooner you find a defect, the cheaper it is to fix"
+
== Unit Test Reports ==
 +
* Last unit testing report here...

Revision as of 09:34, 22 November 2006

Background

"Testing: Early, Often and Automated" (Extreme Programmin Explained by KENT BECK)
The PHPIDE team has excepted the XP ([1]) two principles to increase the cost-effectiveness of testing: double checking and the Defect Cost Increase.
We release the "PHPIDE test framework" that helps us write unit tests for PHPIDE in fast way.

Remember: "The sooner you find a defect, the cheaper it is to fix".

How to


Unit Test Reports

  • Last unit testing report here...

Copyright © Eclipse Foundation, Inc. All Rights Reserved.