Static analysis
Detect code-quality, reliability and security issues using configured rules and policies.
Parasoft Jtest
Apply Java static analysis, support JUnit test workflows, collect coverage and use change-focused test selection in compatible developer and CI environments.
Java static analysisJUnit automationCoverage analysisTest impact analysis
Java quality loop
InputsJava source & buildsPolicies & test suites
Engineering controlsAnalyzeGenerate / run testsMeasure impact & coverage
OutputsActionable findingsFocused feedbackQuality trends
Developer and pipeline quality automation for Java applications and services.
AI-assisted outputs, test selection and policy findings require engineer review; support varies by product release, framework and deployment model.
ParasoftSoftware quality
Core capabilities
Core engineering capabilities
Exact capabilities depend on the selected edition, release and deployment environment.
JUnit workflows
Support generation, execution and maintenance of unit tests with applicable frameworks and dependencies.
Code coverage
Collect and analyze coverage from unit and supported runtime testing workflows.
Test impact analysis
Identify tests associated with changed code to optimize selected verification runs.
IDE and CI integration
Provide feedback within supported developer environments and automated pipelines.
Central analytics
Publish results to DTP for trend, policy, coverage and compliance views.
Implementation workflow
From evaluation to deployment
Validate the technology in the real build, target and reporting environment before wider rollout.
- 01Connect project and build
- 02Configure quality policy
- 03Analyze and remediate
- 04Generate or execute tests
- 05Assess coverage and impact
- 06Publish results and gates
Confirm the deployment fit
Compatibility depends on the actual toolchain, target environment, integration needs and assurance objectives.
- JDK, framework and build compatibility
- Unit-test and mocking framework
- Monolith or distributed architecture
- Security and code-quality policies
- CI runtime and test-suite duration
- DTP and issue-tracker integration
Where the technology adds value
Well suited for
- Enterprise Java code quality programmes
- JUnit acceleration and coverage improvement
- Faster CI feedback through impact analysis
- Centralized secure-coding governance
Important considerations
- AI-generated tests and fixes require engineering review before acceptance.
- Integration and system testing remain necessary.
- Impact analysis depends on correct baselines, coverage and change data.
- Compliance-oriented records require organizational review, governance and approval.
Relevant engineering frameworks
OWASPCWECERT JavaPCI DSS workflowsOrganisation-specific secure-coding policies
Related capabilities
Extend the software assurance workflow
Explore adjacent capabilities across requirements, verification, testing and embedded security.