Comprehensive Java Testing Made Simple With Jtest

Optimizing test creation and execution together with measuring code coverage are important parts of modern development processes. The new release of Parasoft Jtest 2023.1 adds important new capabilities enabling Java development and QA teams to be more productive and efficient in their testing practices.

With this release, you can enforce the quality of Java code in the popular Visual Studio Code IDE. Additionally, code coverage and test impact analysis workflows have been expanded to support QA teams without access to source code and application tests run by any testing framework.

Java developers can now get a 14-day free trial of Parasoft Jtest! Once you register, you’ll automatically receive a download link and an activation code that will allow you to try out Parasoft Jtest within a few minutes of signing up. Try it today for a hands-on experience of Jtest’s efficiency and productivity enhancements.

Visual Studio Code

Welcome to the new kid on the (IDE) block—Visual Studio Code!

While it’s not actually that new, Visual Studio Code continues to gain in popularity as an IDE for Java development teams. Recent surveys show that it now has about a 20% market share in the Java IDE space.

In this release, we added a Visual Studio Code extension for Parasoft Jtest. From this extension, you can:

• Run static code analysis.
• Publish and download static analysis results from Parasoft DTP, our reporting and analytics dashboard.
• Review code coverage results directly in the IDE and more.

Download it from the Visual Studio Code marketplace.

Automatically Generate & Run Unit Tests for Changed Code in the IDE

When development teams make code changes in their application, they can be tempted to skip unit testing because they don’t have the time it takes to write the appropriate set of unit tests. This is no longer an excuse with the latest release of Parasoft Jtest! With this release, developers can automatically create unit tests to specifically cover the code that they just changed. What’s more, the new unit tests are optimized to only cover the uncovered parts of their new code, eliminating the creation of redundant tests.

In addition to writing new tests for modified code, developers also need to run existing tests to validate their changes before committing code. They often don’t know which tests to run and don’t want to run all of them because it might take too much time. Parasoft Jtest’s Impacted Unit Tests view solves this problem by showing developers the specific tests they need to re-run to validate their changes with a single action to run these specific tests. In this release, the Impacted Unit Tests view has been enhanced to show the primary set of impacted unit tests even if coverage from the nightly test run has not been imported (which supports showing the full set), and it now indicates which unit tests are new and which are existing.

Measure Code Coverage Without Access to Source Code

The demand to measure code coverage seems like it’s never been higher. While code coverage doesn’t tell you whether you’ve done enough testing, it does tell you when you have NOT done enough testing. With Parasoft Jtest, development and QA teams can measure the code coverage of Java applications from multiple testing practices, including unit tests, functional tests, UI tests, and manual tests.

A significant new capability in this release is the ability for QA teams to measure code coverage in applications for which they do not have access to source code. In previous releases, teams needed to analyze source code to establish a baseline set of code against which to measure code coverage. But with this release, QA teams can now scan the application binaries directly to determine the application code against which to measure coverage.

In addition, the new command line utility, jtestcov, streamlines code coverage workflows and makes them faster and easier. This provides the ability to capture the baseline set of testable code and the runtime coverage data independently and separately upload this data to Parasoft DTP, where it gets aggregated together.

Use Test Impact Analysis With Any Test Framework

Development and QA teams want to optimize testing in their CI/CD pipelines to focus on recent code changes and get feedback as quickly as possible. In previous releases, teams could use Jtest’s test impact analysis to identify and run the specific set of unit tests that would validate their changes. But we know that teams run more than just unit tests—including functional tests and UI tests.

With that, we expanded Jtest’s test impact analysis capabilities using our new jtestcov command line utility to identify impacted functional, UI, and other kinds of tests that need to be run based on a set of code changes and the coverage collected from those tests —regardless of which testing framework is used to run those tests.

Check for Compliance With New & Updated Test Configurations

For security and compliance requirements, we updated the following static analysis test configurations to verify the security and privacy aspects of source code.

• New test configuration for the OWASP Application Security Verification Standard (ASVS) 4.0.3., which offers a framework for evaluating the technical security controls of web applications and presents developers with a set of guidelines for building secure applications.
• New test configuration for CWE 4.10
• Updated test configuration for CWE Top 25 + On the Cusp 2022
• Updated test configuration for UL 2900
• Updated test configuration for HIPAA

Support for the Latest Versions of IntelliJ & Eclipse

Jtest supports the following.

• IntelliJ versions 2022.3 and 2023.1
• Eclipse versions 2022-12 and 2023-03

Download Details & Learn More

Customers can download Jtest from the Customer Portal. Want more details about the enhancements? View the release notes.

Don’t have a license for Jtest, yet? Start a free 14-day trial now.

If you want to learn more before starting your trial, request a demo with our experts to see how Jtest makes unit testing easier and faster for development teams.