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"
m |
|||
Line 6: | Line 6: | ||
<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". | ||
+ | |||
== Resources == | == Resources == | ||
Line 14: | Line 15: | ||
| org.eclipse.php.core || org.eclipse.php.core.tests | | org.eclipse.php.core || org.eclipse.php.core.tests | ||
|} | |} | ||
+ | |||
== Running Unit Tests == | == Running Unit Tests == | ||
Each Unit Test plug-in has its own AllTests suite. For running the suite at once right click on it, then select: Run As -> JUnit Plug-in Test. Each test can be run independently in the same manner. | Each Unit Test plug-in has its own AllTests suite. For running the suite at once right click on it, then select: Run As -> JUnit Plug-in Test. Each test can be run independently in the same manner. | ||
+ | |||
== Mailing List and RSS == | == Mailing List and RSS == | ||
Line 23: | Line 26: | ||
<br> | <br> | ||
also an RSS feed can show you bug status: [http://download.eclipse.org/tools/pdt/downloads/rss/center.xml http://download.eclipse.org/tools/pdt/downloads/rss/center.xml] | also an RSS feed can show you bug status: [http://download.eclipse.org/tools/pdt/downloads/rss/center.xml http://download.eclipse.org/tools/pdt/downloads/rss/center.xml] | ||
+ | |||
== Unit Test Reports == | == Unit Test Reports == |
Revision as of 06:59, 21 April 2009
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
Unit tests for PDT plug-ins can be found under /cvsroot/tools/org.eclipse.pdt/tests module. The convention is the following:
Plug-in Name | Unit Test Plug-in Name |
---|---|
org.eclipse.php.core | org.eclipse.php.core.tests |
Running Unit Tests
Each Unit Test plug-in has its own AllTests suite. For running the suite at once right click on it, then select: Run As -> JUnit Plug-in Test. Each test can be run independently in the same manner.
Mailing List and RSS
In order to be updated on test issues, register pdt-unit-test@eclipse.org at
https://dev.eclipse.org/mailman/listinfo/pdt-unit-test
also an RSS feed can show you bug status: http://download.eclipse.org/tools/pdt/downloads/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/drops/N<date>/results/TEST-php.html