Understand the impact of changes in your codebase and provide actionable insights to the team to ensure the delivery of high-quality software.

By aggregating data across all testing practices (static analysis, metrics, unit testing, functional testing, manual testing, code coverage, and code reviews) from both Parasoft technologies (C/C++test, dotTEST, Jtest, SOAtest) and OSS/3rd-party tools (supporting over 15 development languages) into a centralized quality dashboard, Parasoft DTP enables you to monitor and manage the quality of the entire software development process.

You don't have to test everything with every sprint. Laser-focus your testing with Change-Based Testing.

Addressing Critical Issues Impacting Teams

Reduce the cost of developing high-quality software, without sacrificing time-to-market.

  • Heightened risks of failure due to accelerated release schedules

    Mitigate business risks without reducing the productivity of the team with a centralized quality hub that aggregates all the data from your testing practices. DTP's advanced analytics uncovers the hidden risks within the codebase, so you can make decisions about what is an ‘acceptable level of risk’ and release sooner, with more confidence.

  • Managing multiple geographically-dispersed and technology-diverse teams

    To simplify the management of teams working with different core technologies and leveraging different tools for testing, DTP brings data together from both Parasoft and third-party tools. DTP's unique data management filters aggregate test runs across teams and codebases, while role-based access enables sharing of configurations and dashboards without teams treading on each other’s toes.

  • The burden of achieving compliance

    Achieving, reporting, and maintaining compliance with industry standards can be extremely costly and disruptive. DTP aggregates all of your test data (from both Parasoft and third-party tools), providing a centralized platform for standardizing and reporting compliance.

  • The cost of discovering security vulnerabilities

    Instead of waiting until the last phases of the SDLC or adding additional specialized tools, security testing can be embedded into your existing quality process. To reduce the testing burden, DTP aggregates test results from the Parasoft tools that are already supporting your team’s quality practices, including static application security testing and penetration testing, to provide a comprehensive view of your security policy.

Aggregated Reports & Dashboards in Parasoft DTP

Aggregate the data from across all of your testing practices and quickly create interactive dashboards, using DTP's customizable widgets, that you can share with the team.

Coverage Dashboard

for Architects and Development Leads

Change Dashboard

for Architects and Development Leads

Compliance & Security Dashboards

for Managers

Risk Dashboard

for Managers

Parasoft DTP’s flexible drag-and-drop dashboard provides over 50 out-of-the-box widgets (with more available on the Parasoft marketplace, and the ability to create your own), categorized and color-coded so you can quickly assemble your own view into your quality process. From inside your dashboards, navigate to actionable Explorers, providing unprecedented levels of insight into the outcomes of your quality practices.

Data Explorers

Reports and dashboards are great, but they're just the start.

The true power of DTP goes beyond reports and dashboards, leveraging advanced analytics to optimize the team’s testing practice – but the key to DTP’s advanced analytics is how the data is aggregated and correlated. The Explorers within DTP give visibility into that data, and enable powerful workflows for your development team, integrating directly in the IDE and other systems of record.

Coverage Explorer

Identify the tests that executed against specific files in the codebase to unlock the value of code coverage.

Merging coverage from across testing techniques (i.e. unit, functional and manual testing) and correlating that coverage to the specific tests, enables the team to understand the effectiveness of the different testing practices and identify the most efficient way to increase overall test coverage.

Test & Violation Explorers

Look at detailed information to strategize and implement a remediation workflow.

View violations and test results in the context of both the codebase and specific builds. With access to historical information and details of the violation or test, you can determine what needs to be done and automatically trigger workflows.

Change Explorer

Get a handle on the risk between builds by mapping changes in the codebase to changes in the quality data.

Review the code changes made between two builds, along with changes in the quality data, to perform a comprehensive audit and gain better understanding of the impact of change. When issues are identified, trigger additional review and remediation workflows both within DTP and external systems.

Metrics Explorer

Understand how well the code is constructed and mine the data metrics that measure it.

Use the Metrics Explorer to understand the structure of your code by navigating the 40+ out-of-the-box metrics calculated by Parasoft tools (i.e. Jtest, C/C++test, or dotTEST) and identify where problems exist so you can set thresholds to act as guardrails as part of your software development policy.

Powerful & Flexible Analytics

Award-winning insights from Parasoft's Process Intelligence Engine (PIE)

Advanced analytics from DTP’s award-winning Process Intelligence Engine (PIE) enable you to drive process improvements, gain greater insights, and streamline the team's testing activities. You can use existing PIE analysis “slices” that are preconfigured inside DTP, or you can create your own. DTP is fully customizable, so you can extend PIE to measure just about anything you want.

Change-Based Testing

Don't have time to re-test everything every sprint? Optimize your testing strategy and focus on re-executing only the tests that touch the changes.

Powered by the detailed code coverage analysis from the Parasoft tool suite and DTP’s correlation of that coverage to specific tests, PIE analyzes the intersection of code changes with tests and identifies the subset that need to be re-executed to validate the changes. Change-Based Testing enables the team to discover regressions sooner and avoid last minute delays and late nights before a new release.

Modified Code Coverage

How do you know if you need to create new tests? Focus on achieving 100% coverage on the code that has changed and not coverage of legacy code.

You don't have time to test all of your legacy code – most of it is already working and you are not changing it in this sprint. Also, simply focusing on increasing code coverage is not going to tell you if you are testing the code that truly matters (the new and modified code). PIE can analyze the changes between builds to determine where the risky gaps in coverage exist, helping you to focus on creating the right tests so you can move into the next sprint with confidence.

Risky Code Changes

What is the risk of the code that you just changed? What is the amount of existing quality debt?

Customize your own multi-dimensional and multi-variable definition of “risk", and let PIE show you where it exists in your codebase. Then prioritize the testing that will get the risk under control, and sleep a little better at night.

Test Stability Reporting

Did that test failure mean anything or is it always doing that? Where are the real regressions?

Because DTP tracks tests individually across builds, PIE can analyze patterns in the test execution and identify your unstable tests. This enables your team to focus on true regressions rather than wasting time chasing instabilities. Or, when you’re trying to find your unstable tests, PIE quickly pinpoints them, avoiding the frustrating hunts for the needles-in-the-haystack.

KPI Calculations

How do you measure cross-team performance to ensure efficient adoption of quality practices? How do you know the amount of debt or risk that existing across projects?

Simply counting the number of static analysis violations is not sufficient to understand the amount of work or risk that exists within a codebase. Different organizations associate different levels of risk and different costs to different static analysis rules, so PIE’s configurable KPI calculations allow you to build a consistent score card across the teams so you can quantify the values and monitor improvements.

Custom Analytics & Derived Metrics

How do I make calculations that are custom to my organization?

In addition to existing slices, you can create and customize PIE to measure whatever you want. DTP can process imported data from just about any external analysis tool, painting a complete picture of your code quality. The data aggregated in DTP is also available via REST APIs, so you can use existing PIE analytics and DTP workflows as templates to implement just about anything you want.

Policy & Compliance Enforcement with Parasoft DTP

Establish and define your software development policies and quality gates within DTP to automate enforcement and compliance as part of your DevOps workflow.

Defining Policies Across the Team(s)

There's never just one policy – there's an aggregation of multiple policies, and DTP helps you organize that complexity. A centralized policy is key to ensuring that non-functional business requirements (quality, security, and performance) are consistently met across teams within your organization. But in order to make the "go" or "no-go" decisions based on an acceptable level of risk, there needs to be visibility into how the underlying quality practices map to the non-functional business requirements. DTP’s Policy Center helps you organize that complexity, by defining thresholds around the testing practices, aggregating policies, and quality gates that can be queried as part of your CI pipeline.

Compliance Reporting and Auditing

DTP provides a centralized quality hub for compliance reporting. It aggregates all of your testing data in one place, simplifying the process and effort for demonstrating compliance while providing a central location to manage and audit the quality process.

Compliance for Industry Standards

Take data from static analysis and, without re-executing the analysis, display the results in the context of the industry standard that you need to demonstrate compliance for, i.e. MISRA, CWE, OWASP, ISO 26262, etc.

Compliance Packages

Make demonstrating compliance less painful by leveraging preconfigured compliance widgets, dashboards, and reports for industry standards. Customizing these packages to fit your organization's specific compliance needs.

Auditing and Build Certification

Leverage the audit trails of the Test, Violation and Change Explorers to track your ongoing quality process. When a specific build is ready for certification, archive all the data from the test runs, locking the build once verification is complete.

Workflows for Integrating Quality into your SDLC

DTP is at the center of integrating quality into your SDLC, not only providing the reporting and analytics but also enabling the workflows that are critical for ensuring the successful adoption of quality practices into your software development process.

To integrate DTP into your SDLC, start with dashboards and reports, where a development manager can get a view of what's going on in the ecosystem, and explore metrics in detail. Then, PIE takes the data and performs advanced analytics for you. The Explorers are there for architects to see relevant data, and the results of PIE's analyses end up back in the developer's IDE for remediation. Once the developer re-executes within their desktop and checks in their code to source control, the infrastructure picks up again and runs the same way.

DTP's centralized test configuration enables powerful integration across the SDLC:

Benefit from a Centralized Configuration for both IDE and CI Execution

DTP's centralized test configurations and rule-sets allow you to seamlessly ensure consistent execution of analysis across the team, both in the developer's IDE and as part of an integration with Continuous Integration (CI).

Integrate Results from CI into the Developer's IDE

When DTP receives violations and test results, it adds metadata that provides additional context to the findings. This customizable metadata, which includes assignee, priority, and action, can be set either manually, through DTP's Explorers, or automatically, as part of a PIE slice, and downloaded along with the findings directly in the developer's IDE.

Trigger Workflows and Correlate Data with Existing Systems

DTP can be easily configured to trigger external workflows and correlate data with your existing systems of record. For example, you could correlate test results with user stories in JIRA, create a task, or send an email to a developer when a violation has been assigned to them via the Violation Explorer.

Want to see Parasoft DTP in action?

Start benefiting from actionable insights and indicators right away.

Try Parasoft DTP