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
m (PHPIDE Testing Framework moved to PDT Testing Framework) |
|||
| 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 | + | The PDT 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 " | + | We release the "PDT test framework" that helps us write unit tests for PDT in a very fast way. |
<p> | <p> | ||
"The sooner you find a defect, the cheaper it is to fix". | "The sooner you find a defect, the cheaper it is to fix". | ||
| Line 9: | Line 9: | ||
== Resources == | == Resources == | ||
| − | * | + | * PDT Test Framework Tutorial - [http://wiki.eclipse.org/images/2/20/JUnit_for_PHPIDE.zip] <br> |
* [[The Three Test Suite Modes]] <br> | * [[The Three Test Suite Modes]] <br> | ||
Revision as of 11:57, 28 December 2006
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
- Media:Bare Junit Report.zip (first draft)