Static analysis
Analyze C# and VB.NET code using configured quality, security and maintainability rules.
Parasoft dotTEST
Apply static analysis and security rules to supported .NET projects, execute compatible tests, collect coverage and publish results to DTP.
C# & VB.NET analysisSecurity policiesTest execution & coverageDTP reporting
.NET verification workflow
InputsC# / VB.NET sourceBuilds & policies
Engineering controlsStatic analysisExecute supported testsCollect coverage
OutputsPrioritized findingsCoverage resultsCentral reports
Code-level quality, secure-coding and coverage automation for supported .NET environments.
Rule packs, IDEs, .NET versions, test frameworks and coverage capabilities vary by release and must be matched to the actual development stack.
ParasoftSoftware quality
Core capabilities
Core engineering capabilities
Exact capabilities depend on the selected edition, release and deployment environment.
Security policy enforcement
Map findings to supported security standards and organization-specific policies.
Test execution
Run supported .NET unit-test workflows as part of developer or automated pipelines.
Coverage collection
Measure coverage from unit and supported application execution scenarios.
Developer feedback
Integrate findings into supported Microsoft development environments and CI workflows.
DTP integration
Centralize findings, coverage, trends and compliance-oriented reports.
Implementation workflow
From evaluation to deployment
Validate the technology in the real build, target and reporting environment before wider rollout.
- 01Connect solution and build
- 02Select policies
- 03Run analysis
- 04Execute supported tests
- 05Collect coverage
- 06Triage and publish results
Confirm the deployment fit
Compatibility depends on the actual toolchain, target environment, integration needs and assurance objectives.
- .NET and framework versions
- Build and test runners
- Security policy requirements
- IDE and CI/CD topology
- Coverage collection scenario
- DTP, issue and ALM integration
Where the technology adds value
Well suited for
- C# and VB.NET code-quality governance
- Secure-coding policy enforcement
- Coverage collection across automated tests
- Enterprise reporting with DTP
Important considerations
- Language and framework support should be confirmed for the selected release.
- Security findings still require engineering review and risk treatment.
- Runtime and penetration testing remain complementary activities.
- Compatibility should be verified against the exact .NET and toolchain versions.
Relevant engineering frameworks
OWASPCWEPCI DSS workflowsUL 2900 workflowsOrganisation-specific coding standards
Related capabilities
Extend the software assurance workflow
Explore adjacent capabilities across requirements, verification, testing and embedded security.