Page tree

Skip to end of metadata
Go to start of metadata

The latest release of DTP Engines build on Parasoft’s innovative approach to continuously improving software quality processes. 

In this release:

Understanding Change in Continuous Delivery Environments

As organizations implement continuous software delivery platforms, conventional reporting mechanisms based on data aggregated over time are no longer viable. Understanding the risk that incremental changes introduce from build to build becomes critical as the release velocity accelerates. Organizations need immediate visibility into changes in coverage, changes in test regressions, and the ability to quickly identify which tests need to be rerun. The updates in this release help you understand these changes and identify any issues that need to be resolved in order to mitigate risk and accelerate delivery. 

Reporting Static Analysis Violations by Build

In this release, we’ve extended the concept of reporting build-based data. DTP Engines can now report new, fixed, and existing static analysis violations by build, enabling organizations to not only address potential defects more efficiently early in the SDLC, but also correlate violations with change to pinpoint specific areas of the code where defects may have been introduced. 

Multisession Application Coverage for Java Web Applications

The Java application coverage engine (Jtest DTP Engine) has been extended to track the unique coverage for users that are simultaneously accessing the same application server.  Multiple QA engineers, for example, can access the same web application server, perform parallel testing, and the coverage agent will be able to determine which coverage is associated with which server. 

A Better Desktop Experience for Developers

Developers want to write code, not be burdened with more tools and processes that slow them down. This release introduces the following IDE-based features and enhancements enable developers to create defect-free software faster.

Unit Testing Assistant for Java

The shift to Agile has amplified the challenges associated with unit testing that threaten to erase the gains made by adopting iterative development approaches in the first place:

  • Unit tests are expensive to create and maintain in terms of resources. Someone with the technical knowledge and understanding of the code is required to construct the tests and update them as the code evolves.
  • Unit tests are often executed without the context of the user story. Without traceability from test to requirement, organizations may not have full confidence that the test verifies the intended functionality.
  • Unmaintained or poorly constructed tests might behave inconsistently and become highly dependent on the environment. As a result, tests may introduce volatility into the regression suite as the code evolves, making it impossible to reliably execute the tests in a continuous environment.

The Jtest Unit Test Assistant (UTA)a, which helps developers create meaningful, maintainable unit tests, solves these problems. UTA not only reduces the time to create unit tests, its interface removes some of the technical barriers that have historically required developer expertise.

In addition to easing the burdens of writing unit tests, UTA can actually analyze existing tests to root out potential issues, such as stability. The unit test monitoring functionality helps identify tests that are highly dependent on the environment, enabling teams to improve the test so that it can consistently run in isolation. Additionally, UTA enables a developer to track an object during test execution to generate assertions on the observed changes of the object.

Continuous Quality Assistant (CQA)


CQA enables developers to get immediate feedback on the code they’re working with. CQA analyzes code as the developer performs actions, such as opening and saving files, prior to running a full analysis. CQA executes targeted, high-performance rules as controlled through the test configuration, keeping analysis overhead low.Other Updates and Enhancements

  • Improved rules parameterization in the DTP Test Configuration UI.
  • Improved reporting of errors and setup problems within HTML reports and on DTP.

Resolved PRs/FRs





The Categories used by the "Compliance by Category" Widget don't match the target Test Configurations


Unable to see Test Configuration in DTP Server after it is created


Required feature for Server Edition license is not available with ENT licenses


Jenkins Cobertura Coverage widget does not work with Japanese locale


Rule UC.UP is missing inJtest10.x


Rule METRIC.DIF is missing inJtest10.x


Rule GLOBAL.ACD is missing inJtest10.x


Gradle 3.0 not supported


IntelliJ:sourcelevelinjsonfileis empty


Bulitin Test Configurations are not available in IBM RAD GUI


Discrepancy between documentationandjtestcli.jvmregarding -Xmx value


NAMING.NE does not work correctly in case of inner classes


Wrong example repair code in rule's documentation of HIBERNATE.SLM


BD-PB_NOTINIT stops triggering when unrelated code is added




Error: use of __if_exists is not supported in this context


MISRA2008-5.0.6.a False Negative for expression initializers


Differences between the results of the analysis when incremental mode is enabled or disabled


Parsing error: a derived class is not allowed here


Problem when -include/-exclude file is not found


BD.PB.VOVR parameter name is incorrect and should be updated


MISRA2004-9_2 false positive when #define symbol used in array initializer


Incorrect use of website option


Invalid MSBuild target when building WebSite with special characters in name or located in a solution subfolder


Coverage markers are not visible when importing results to a project with path including Japanese characters


Randomly failing Engine analysis


Setup problems reported during diff operation on TFS


Suppressions are ignored when rule id includes severity

  • No labels
Write a comment...