In this release, we've focused on helping you streamline your unit testing process and increase your code coverage with Unit Test Assistant. Support for JavaWe've added support for Java 9 and 10. Support for IDEsWe've added support for:
Test Impact AnalysisTest impact analysis allows you to identify and run a subset of tests that are affected by changes to your production code. It speeds up test execution and helps you optimize the unit testing process. To facilitate test impact analysis with Jtest, we've introduced the Impacted Unit Test view in the IDE and the Test Impact Analysis plugin for Maven and Gradle. Impacted Unit Tests ViewThe Impacted Unit Tests view is a new panel in your IDE that helps you understand how changes affect your tests. You can now monitor in real time which tests are being affected by your current code modifications and select a subset of tests you want to run. See Test Impact Analysis. Test Impact Analysis Plugin for Maven and GradleThe new test impact analysis plugin can detect and re-run only the tests that were affected by your changes. The plugin integrates with your build systems, enabling Jtest to leverage the test impact analysis functionality and accelerate test execution processes. See Test Impact Analysis with Maven and Test Impact Analysis with Gradle. Increasing Code CoverageWe've enhanced Jtest's code coverage capabilities. Enhanced Uncovered Code RecommendationsThe Uncovered code recommendation can now guide you through the process of increasing code coverage:
In addition, we've optimized detecting uncovered code. See Increasing Code Coverage for details. Creating Tests for Private MethodsUTA can now create regular, parameterized, and Spring unit tests for private methods to help you increase your code coverage. See Creating a Basic Unit Test, Creating a Parameterized Unit Test, Creating a Spring Unit Test. Additional Unit Test Assistant EnhancementsSupport for Spring in IntelliJ IDEAYou can now create, monitor, and enhance Spring unit tests in IntelliJ IDEA. See Creating a Spring Unit Test. Automatically Creating AssertionsWe've extended UTA's tracking capabilities to automatically make assertions. The Track and make assertions option monitors a method call and automatically applies all recommended assertions. See Tracking Object Changes and Creating Assertions. UTA Actions in the Quick-Fix MenuUTA actions are now available form the context assist dialog, which opens with a keyboard shortcut. See About UTA Actions. Support for Mockito 2We've added support for Mockito 2 and enabled UTA to automatically detect the Mockito version you are using. Standalone License ServerYou can now obtain the Parasoft license from an additional instance of DTP or a standalone License Server. See Setting the Parasoft License (for desktop) and Setting the License (for automation). Other Changes
Updated Test ConfigurationsThe following test configurations have been updated to improve analysis results:
Updated Code Analysis RulesThe following static analysis rules have been updated to improve analysis results:
The output messages of the following rules have been updated, and as a result, suppressions associated with these rules on DTP may no longer be available:
You can restore the previous messages and suppressions for the BD category rules; see Why are suppressions of some rules no longer available on DTP after Jtest was upgraded to a newer version?. Resolved Bugs and FRs
|
For information about this release, see https://docs.parasoft.com/display/JTEST1041/Updates+in+10.4.1. |