Jtest's test impact analysis helps you optimize your testing efforts by automatically detecting test cases affected by locally modified code. This allows you to identify and re-run only the tests that are affected by your changes – saving the time and effort of executing a large number of unaffected tests for fear they might be brokenchange.
This section explains how to leverage Jtest's describes the test impact analysis on your workflow for Jtest desktop users. For information about about test impact analysis from the command line, see Testing and Analysis with Maven and Testing and Analysis with Gradle.
...
- Jtest 10.4.0 or later
- Eclipse or IntelliJ IDE (see Prerequisites for supported versions)
- SVN or Git
...
- JUnit 4
...
Importing Coverage
Before running tests, you need to ensure that coverage data related to the source code you modify is available in the Coverage View in your IDE. To achieve this, you need to integrate Jtest into your unit test execution to collect the coverage data in an XML file or report it to DTP, and then import the data to your IDE. Collecting coverage data for each run of your unit test suite and importing the data for the most recent test run allows you to ensure that the information in your IDE is up-to-date.
...
Jtest automatically monitors all open projects in the workspace. By default, the view displays in real time which tests are affected by your current code modifications - every modifications–every time you make a code change that impacts a test, the view is refreshed to display that test. To switch off automatic detection of affected tests, disable the Auto detect impacted tests option in the view's menu.
...
To run a subset of impacted tests, select one or more nodes in the tree – at the project, package, class, and/or method level. Then click the node(s) to analyze and click Run selected tests button in the view 's menu.
To run all impacted tests that are displayed in the view, click the Run all tests button in the view's menu.
| Info | ||
|---|---|---|
| ||
Tests executed from the Impacted Unit Tests view will not update your coverage data. To view updated coverage results, run your tests from the Unit Test Assistant view or with the Jtest test configuration (see Executing and Collecting Coverage for JUnit Tests). |
While analyzing resources, Jtest creates two .java classes in the default package of your project that are used for storing information about affected tests and running the selected test methods. Do not commit these files to your source control system. For your convenience, you may consider adding them to the .gitignore file (in Git) or setting the svn:ignore property on all projects (in SVN).
...