How does it work?
For unit testing, Jtest collects coverage data for unit tests that are run from different build systems (Ant, Maven or Gradle), IDEs (Eclipse and IntelliJ), and the most popular testing framework (JUnit). Jtest analyzes every line of code and marks it as covered if it was executed during the testing process. Total coverage is the ratio of covered lines to all the lines which could have been covered. Users can easily check if their code has been thoroughly tested by inspecting coverage reports, or check if they are meeting a code coverage requirement. Parasoft’s coverage report enables the user to easily identify the lines and portions of code that were not covered.
Jtest also enables customers to monitor standalone and web applications to collect coverage information for code that was executed when an application was running. QAs and testers can collect coverage data from their manual or automated testing sessions, and Jtest can easily integrate with third-party test execution software for an automated process.
To provide effective test traceability, Parasoft tracks the covered code per test, especially useful when a user wants to check what exactly is tested by their test case, or to ensure proper test isolation (for instance, if a unit test executes unintended code, that accesses locally-stored files or modifies the environment, the user can stub or mock it). By associating tests with development artifacts, such as requirements, tasks, or feature requests in a requirement or task management system, Parasoft an collect requirement-to-test and test-to-coverage information to enable users to check if their feature implementations are properly covered by their tests.
Try Parasoft Jtest