Skip to main content
Jump to: navigation, search

Difference between revisions of "PDT/Testing Framework"

< PDT
 
Line 18: Line 18:
 
== 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.
 +
 +
See also: [[PDT/Testing Framework - PDTT]]
  
 
[[Category:PDT]]
 
[[Category:PDT]]

Latest revision as of 16:12, 21 October 2015

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 /gitroot/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.

See also: PDT/Testing Framework - PDTT

Back to the top