Here are the known limitations of Parasoft Jtest:

Test Impact Analysis

• Test Impact Analysis for JUnit 5 requires additional dependencies, including JUnit 4. This limitation is caused by a known issue in the JUnit 5 framework where test suites must be executed by a different test engine that requires dependencies that may not be configured within the project (see https://github.com/junit-team/junit5/issues/744). This means that Test Impact Analysis, which depends on test suites for collecting test cases affected by code changes, is unable to re-run affected JUnit 5 tests if the required dependencies are missing. As a workaround, Jtest automatically updates your project with a container that includes additional dependencies when affected tests cases are re-run.
• The Impacted Unit Tests view does not populate correctly when running in an IDE with Java 16 or later. As a workaround for Java 16, you can pass the --illegal-access=permit VM argument to the JVM that is used to start your IDE. This workaround does not work for Java versions later than Java 16.

Unit Test Assistant

• Creating unit tests with Unit Test Assistant for large projects may require a lot of memory. If the selected file scope is too large, the memory consumption may exceed the limit of memory allocated to Eclipse.

Other

• Running static analysis may require additional memory allocation.
• The violations reported for the DISA-ASD-STIG test configuration may contain duplicates, so the number of violations reported may be larger than the actual number of violations.