CPS Quality

Introduction

CPS project is being developed with constant aim to be best-in-class when it comes to quality standards!

For the developer on our team that means (among other things)

1. All new/modified code is accompanied with test-code (maintaining a 97%+ code coverage goal in SonarQube)

2. All new/modified code should have zero SonarQube violations (except INFO-level)

3. REST API changes are always accompanied by relevant examples

4. Read-the-Docs (.rst) files are updated per user story as needed

5. CSIT Integration test are added when required (as agreed by team during user story grooming)

6. Regular follow up of any Nexus IQ evaluation report

Quality related reports

• OpenSSF Best Practices CPS (BadgeApp)

• SonarQube

  • SQ Report CPS-NCMP

  • SQ Report CPS-Temporal

  • SQ Report DMI-Plugin

• Nexus IQ

  • Nexus IQ Policy Evaluation CPS-NCMP (Jenkins)

  • Nexus IQ Policy Evaluation CPS-Temporal (Jenkins)

  • Nexus IQ Policy Evaluation DMI-Plugin (Jenkins)