Code Assurance: How it's used

Typical workflow scenarios

Code assurance can be used in a variety of ways to minimise the likelihood of releasing a previously identified bug.

To Ensure Releases are Clean of Previously Fixed Bugs

For Build/Release Owners, Pattern Insight easily integrates into the release process, or continuous integration, to identify previously fixed bugs in nightly builds or releases going out the door. For example, customers have built catalogues containing hundreds of security vulnerabilities and other important defects and run nightly reports indicating if any of these bugs have leaked into their daily builds. If a match is found, the build is blocked and the developer is automatically notified.

To Eliminate All Instances of a Bug in Development

Developers use Code Assurance to ensure bugs have been fixed across all locations, branches and components in the development process. Simply running a Pattern Insight report identifies every instance of a bug, allowing them to be fixed immediately. 

To Ensure All Changes are Ported into the Final Release

Release engineers use Code Assurance to automatically ensure that changes made in separate branches of the code make it into the final release. Thousands of changes can be checked in a single run.

• Code Assurance: How it's used

• Code Assurance: How it's different

• Code Assurance: How it works