STEP 4: Set Baseline & Threshold

Typically, this step is done by QA Manager/Architect or Engineering Manager.

Setting a baseline and threshold for code changes coverage is your key to confidently tracking and boosting quality throughout development. This powerful duo offers:

1. Clear Framework: Establish a reference point (baseline) and target (threshold) for measuring and achieving desired quality levels.

2. Smarter Decisions: Introduce "Code Changes Coverage" as a new KPI, guiding your Go/No-Go decisions with objective data. The Code Changes Coverage KPI measures the percentage of code changes that have been tested with at least one test.

---

How it Works?

After removing irrelevant parts from your coverage tracking, you can generate a Proof of Testing report to set your baseline and threshold, based on the current coverage.

The baseline serves as your reference point for measuring improvement, while the threshold becomes your target for achieving the desired level of quality and guides your quality improvement efforts throughout the release.

During each test cycle, you should aim to have 0 critical untested code changes in the code subset you are focusing on. As the release progresses, your code change coverage should gradually approach and eventually meet the threshold. The goal is to increase the coverage by covering critical code areas, not just any code area.

Realistic Targets! A quality threshold should align with your goals, ideally not exceeding 20% higher than the baseline. Setting higher thresholds may be overly ambitious, especially during the initial weeks of using SeaLights.

Incorporating the threshold as a new KPI in your SDLC ensures that the Code Changes Coverage acts as a quality gate for making go/no-go decisions, helping you maintain the desired level of quality throughout your development and release process.

By continuously improving your coverage and meeting the threshold, you can enhance the overall quality and reliability of your software.