Get visibility into your Java quality with immediate feedback

With Parasoft Jtest’s sophisticated reporting and analytics, developers and managers can prioritize errors detected in the codebase, including automatically identifying which tests need to be run based on changes in the build. The results of test runs can be viewed on the desktop, web, or in static htm reports, regardless of where they were executed.

Java reporting & analytics

How does it work?

After analyzing the source code and executing unit tests to detect issues at the earliest stages of development, Parasoft’s Process Intelligence Engine analyzes the data collected and provides actionable findings that can be viewed on the desktop, web, or in static html reports.

These actionable analytics are presented in easy-to-use, customizable dashboards that are made up of highly-flexible widgets that clearly display the risks within your codebase, and provide a comprehensive view of software quality.

Jtest can perform analysis within the IDE (Eclipse, IntelliJ, NetBeans), as part of with build systems plugins (Ant, Maven, Gradle), or with the command-line interface (for custom type of builds).

Try Parasoft Jtest

Features

Jtest generates personalized reports, per execution run, with its static analysis, unit testing, and code coverage findings. Developer reports cover only the results associated with the given developer, to help them focus on issues associated with their code. Manager reports cover results for all team members, with additional statistics that report on a comprehensive view of the whole project.

Parasoft Jtest automatically assigns potential problems in the codebase to the people who are responsible for the changes that caused them, by integrating with the source control system in your development environment.

HTML reports include traceability to development artifacts, such as requirements, defects, and user stories, by integrating into tools in your development infrastructure (i.e. Jira or Bugzilla) to help you streamline your workflows and make it easier to correlate a test failure to a user story.

Parasoft provides many ways to review results quickly and effectively, so you can customize reporting to your specific workflow. Test results can be: 

  • Stored as static report files (i.e. xml, html, pdf, or CSV)
  • Automatically emailed (as part of the execution via source control integration) to the appropriate team members
  • Viewed directly in Continuous Integration servers (i.e. Jenkins, Bamboo, TeamCity)
  • Imported and reviewed directly in the developer’s IDE (i.e. Eclipse, IntelliJ, NetBeans)
  • Analyzed in Parasoft’s dedicated reporting system, to allow managers and executives to fully understand trends across runs, reviewing violations without access to the codebase or development environment.

Benefit from the Parasoft Approach

Want to learn more?

Parasoft Jtest integrates with a wide variety of software, tools, and frameworks,
so you can easily adopt and scale within your existing development environment.