Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "PDT/Testing Framework"
< PDT
| Line 1: | Line 1: | ||
| − | + | '''"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 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. | ||
Revision as of 09:33, 22 November 2006
"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"