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.
Difference between revisions of "PDT/Testing Framework"
< PDT
Roy.zend.com (Talk | contribs) (→Unit Test Reports) |
m (→Background) |
||
| Line 2: | Line 2: | ||
'''"Testing: Early, Often and Automated"''' (Extreme Programmin Explained by KENT BECK)<br> | '''"Testing: Early, Often and Automated"''' (Extreme Programmin Explained by KENT BECK)<br> | ||
| − | The PHPIDE team has | + | The PHPIDE team has accepted 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 a very fast way. | We release the "PHPIDE test framework" that helps us write unit tests for PHPIDE in a very fast way. | ||
<p> | <p> | ||
Revision as of 03:34, 7 December 2006
Background
"Testing: Early, Often and Automated" (Extreme Programmin Explained by KENT BECK)
The PHPIDE 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 "PHPIDE test framework" that helps us write unit tests for PHPIDE in a very fast way.
"The sooner you find a defect, the cheaper it is to fix".
Resources
- PHPIDE Test Framework Tutorial - [2]
Unit Test Reports
- Media:Bare Junit Report.zip (first draft)