Featured Webinar: Unveiling Parasoft C/C++test CT for Continuous Testing & Compliance Excellence | Watch Now

Person typing on computer

Java Test Impact Analysis

Test Impact Analysis

Powered by Parasoft Jtest, the enterprise development testing solution for Java

Test Impact Analysis for Java Unit Testing

Parasoft Jtest optimizes unit test execution by identifying which tests need to be run based on code changes, and automatically running just the tests needed to validate code changes, reducing the amount of time it takes to get feedback on the quality of the deliverable.

How Does It Work?

The quicker you can test, the quicker you can release. Parasoft Jtest helps you reduce the time it takes to test your application by optimizing unit test execution within the IDE and in the CI process, based on precisely what has changed in the code. With its Smart Test Execution capabilities, Parasoft Jtest uses Test Impact Analysis to analyze the source code to identify the changes a developer has made in the application, and automatically identifies the subset of tests that need to be executed to validate his or her changes. All the user has to do is simply click “execute” to automatically run impacted tests.

In the IDE

Built on top of Parasoft Jtest’s coverage analysis, Jtest collects information about which code is exercised by which tests, and applies that information within the developer’s IDE as the developer is changing code, enabling the developer to easily identify and execute the specific tests that need to be run to verify that the changed code doesn’t break any tests.

Jtest keeps track of which of the affected tests have been run, which have passed, and which have failed, making it easy for the developer to determine which tests still need to be run, or which tests have failed and need to be addressed. Once all tests have been run and are passing, the developer knows that it’s safe to commit their code and move on. Jtest supports projects that are in Git or SVN source control and can be run from popular IDEs (Eclipse, IntelliJ).

Within the CI process

Parasoft Jtest optimizes unit test execution during the CI process and can integrate seamlessly into projects that use either Maven or Gradle as their build system, to get immediate feedback on changes. Without this capability, bad code changes would introduce regressions not caught as quickly or that would interfere with work being done by other team members. Jtest identifies which code has changed since the baseline build (for example, the last nightly build), determines which tests need to be run to exercise that code, and then runs just that subset of tests. This workflow enables teams to set up CI jobs that only run tests based on the most recent code changes, shrinking the amount of time it takes to run a CI job from hours to minutes.


Benefit from the Parasoft Approach

Superior Java unit test optimization and efficiency

No other product optimizes Java unit test execution within the IDE and as part of a CI workflow, using actual correlation between the test execution and code exercised during testing. Everything is automatic, and all the developer has to do is right click and run the tests.

Faster feedback on code changes that have caused test failures

Identifying not just direct dependencies between tests and code, but indirect dependencies as well, Parasoft Jtest is comprehensive and smart, and helps teams understand as soon as possible after code is checked in whether the code broke any tests.

Integration that provides deep insights into software quality

Integrating with Parasoft’s functional testing software and award-winning Process Intelligence Engine enables users to get deeper understanding of the impact of changes on the rest of the software testing practice. Teams benefit from next-level efficiency and productivity.