Parasoft Jtest extension for Visual Studio CodeThe Jtest extension for Visual Studio Code provides integration with the static analysis capabilities of Parasoft Jtest. It allows you to analyze your code and review the results directly in Visual Studio Code. The extension requires Parasoft Jtest to be installed and licensed.
Features
RequirementsBefore you test your code with the Jtest extension, you need to download, install, and license Parasoft Jtest. For download and licensing information, or getting a free trial of Parasoft Jtest, please contact us at info@parasoft.com or via our website. This extension requires Visual Studio Code 1.95 or newer. Getting Started
Working with the Jtest Extension
Integrating with a Build SystemTo analyze a project with Jtest extension, you need to enable Parasoft Jtest, which runs under the hood, to collect information about the project. Go to There are two main methods of performing the analysis:
This method ensures that the analysis will be run on the actual project data. To perform it, provide a command line pattern for running the project build with Jtest plugin. See Integrating with Build Systems for information how to integrate with the supported build systems. If the project build is run in another way or from another extension and the Jtest analysis is configured to be executed automatically by the build system,
then you can load the generated results using
To speed up the analysis, you can perform it on a built project by using the jtest.data.json file, which was generated by Jtest plugin during the build.
If the file was not generated previously, append a jtest task to the project build command line with the property
The jtest.data.json file can be reused any time the project is analyzed. Analysis performed in this way is significantly faster, but it requires up-to-date project information. If the project dependencies or configuration settings (for example, Java version) are modified, the jtest.data.json file must be rebuilt to resolve changes properly. To perform static analysis of a built project, ensure that the path to jtest.data.json file is specified in the command line pattern.
See Parasoft Jtest User Guide to learn more. Running Static Analysis
To cancel the analysis before it completes, choose By default, the open editors are automatically saved before analysis. To disable automatic file saving, go to Editing Test ConfigurationsThe Test Configuration Editor is a browser-based editor that allows you to view and customize the test configuration used for analysis, for example to enable or disable rules or change rule parameters. To open the editor:
The extension starts the editor server using the Jtest installation and opens the currently selected test configuration in your default web browser. Save your changes in the editor; the modified test configuration can then be used in subsequent analysis runs. The editor requires a test configuration to be selected. If none is specified, you will be prompted to configure the Suppressing ViolationsYou can suppress a violation to prevent it from being reported in subsequent analysis runs.
Alternatively, you can hover over a violation in the code editor to open the You can configure the Jtest extension to always store suppressions either in code or in suppression files, without prompting you to choose. Go to See Suppressing the Reporting of Findings to find out more about suppressing static analysis violations reported by Jtest. Explaining Violations Using AIYou can leverage Parasoft AI assistant to explain static analysis violations and receive suggestions for fixing them. The assistant is integrated with GitHub Copilot Chat. Note: The Parasoft AI assistant is deprecated and will be removed in a future release. Consider using dotTEST MCP tools instead. See Extending Copilot Chat with dotTEST Tools. Requirements:To use this feature, ensure that you have the following installed:
How to Use:Option 1: From the Problems View
The explanation will be displayed in the Chat View. Option 2: From the Code Editor
The explanation will be displayed in the Chat View. Option 3: Using the Chat View You can also invoke the
AI Guidance DisclaimerThis extension includes features that allow you to interact with an AI model using GitHub Copilot Chat to assist in code development. While the AI aims to provide helpful and accurate suggestions, AI-generated answers can sometimes be incorrect or incomplete. Always verify the AI-generated code, recommendations, or explanations before applying them to your project to ensure they meet your requirements and standards. Additionally, be aware that your organization may control or limit certain features of GitHub Copilot Chat. Depending on your organization's policies, responses from the AI may be filtered or restricted based on content or compliance requirements. Ensure you are familiar with your organization's policies on AI usage and data handling. Mapping Violation SeverityBy default, all Jtest's violations are presented in the Problems View as Warnings. You can map Jtest severity levels (1-5) to Visual Studio Code severity levels (Error/Warning/Information/Hint). Go to Removing Violations from the Problems View
Viewing Rule DocumentationYou can find out more about a reported problem in the documentation for the static analysis rule that was violated. Select a violation in the Problems view or the code editor and choose Importing Results from a Local File or URLYou can import analysis results to Visual Studio Code from an external XML report file generated by Jtest during analysis ( You can choose the following options from the Command Palette to import results:
Importing Results from DTPIf your organization uses Parasoft DTP in the development testing workflow, you can import analysis results to Visual Studio Code directly from DTP. First import:
Subsequent imports:
The imported results are added to the current list of problems in the Problems view. If you want to delete the previously entered credentials, choose Importing Results from GitHub, GitLab and Azure DevOpsYou can import analysis results from GitHub, GitLab and Azure DevOps if the workflow for your GitHub project or the pipeline for your GitLab or Azure DevOps project is customized to run Jtest.
To import results from GitHub:
To import results from GitLab:
If you want to delete the previously entered credentials, choose To import results from Azure DevOps:
The import will begin immediately if the artifact that contains the Importing Code Coverage Results from a FileYou can import code coverage results to Visual Studio Code from an external XML report file generated by Jtest ( To import coverage from a file:
The imported coverage results are added to the active code editor as line highlights. To manage coverage highlights:
Extending Copilot Chat with Jtest ToolsYou can enhance Copilot Chat capabilities with the tools provided with the Jtest Extension, allowing the Chat to interact with Jtest, providing context-aware guidance and analysis. For the best performance, be sure to use Chat in The following built-in tools are available:
The tools can be used by specifying agent instructions or direct prompts in the Chat to implement various tasks and scenarios. For example:
In addition to built-in tools available in the Jtest Extension, you can install external MCP tools provided by Jtest. These MCP tools will further extend Chat with static analysis rule documentation, code coverage information and more. To install additional MCP tools:
To learn more about MCP tools provided with Jtest, see: About Parasoft JtestParasoft Jtest uses a comprehensive set of static analysis techniques, including pattern-based analysis, dataflow analysis, metrics, and more, to help you verify code quality and ensure compliance with industry standards. Installing and Licensing JtestIf you do not have Parasoft Jtest installed, request a download link and a license at our website. To install and license Parasoft Jtest:
For information about a network license and other details, see Setting the Parasoft License. Customizing Parasoft JtestYou can customize Parasoft Jtest by configuring the settings in the
You can reopen the file by choosing See Parasoft Jtest Configuration Settings for the list of available settings. FAQs and TroubleshootingGarbled output from MavenOn macOS, Maven may sometimes fail to correctly determine whether to apply colored output, resulting in garbled text. To resolve this issue, add the following setting to your command line:
If this workaround does not resolve the issue, try disabling interactive mode by using one of the following flags:
"Actual command not found"When working with Jtest violations in the Problems view while language extensions for Java (or other extensions that also report errors to the Problems view) are enabled, VS Code may sometimes fail to recalculate the available actions for the selected item. As a result, it may display an error beginning with: If you encounter this issue, try waiting a few moments and then retry invoking the action. ReferencesAI Guidance DisclaimerThis extension includes features that allow you to interact with an AI model using GitHub Copilot Chat to assist in code development. While the AI aims to provide helpful and accurate suggestions, AI-generated answers can sometimes be incorrect or incomplete. Always verify the AI-generated code, recommendations, or explanations before applying them to your project to ensure they meet your requirements and standards. Additionally, be aware that your organization may control or limit certain features of GitHub Copilot Chat. Depending on your organization's policies, responses from the AI may be filtered or restricted based on content or compliance requirements. Ensure you are familiar with your organization's policies on AI usage and data handling. Usage Data and TelemetryPlease help us improve Parasoft products by sending us usage data. The data will be used to improve the product’s user experience. You can change this setting at any time - this extension respects the AboutJtest extension for Visual Studio Code - Copyright (C) 2026 Parasoft Corporation |