regression suite

Concept

In the cited RISC-V vector accelerator verification flow, a regression suite is a curated set of previously passing tests used by continuous-integration pipelines to check whether RTL changes preserve known-good behavior. The flow created small and large regression sets from coverage-ranked passing tests; the small set ran on merge-candidate DUT changes, while the large set ran weekly. Directed tests for retry and vstart scenarios were also added to the regression suite so those scenarios stayed valid across RTL changes.

First seen 5/28/2026

Last seen 6/1/2026

Evidence 2 chunks

Wiki v1

WIKI

Definition

A regression suite is a set of tests rerun after design changes to check that behavior known to be correct remains correct. In the RISC-V vector accelerator verification environment described in the evidence, regression tests were selected from tests that had already passed and were then reused to validate later RTL changes.

Role in the verification flow

READ FULL ARTICLE →

NEIGHBORHOOD

No graph connections found for this entity yet. It may appear in future ingestion runs.

explore full graph →

RELATIONSHIPS

3 connections

CI/CD Infrastructure ← uses 97% 4e

The CI/CD infrastructure uses a regression suite to verify correctness on RTL changes.

Functional Verification of a RISC-V Vector Accelerator ← uses 93% 2e

A regression suite is maintained and run to ensure design correctness across changes.

Directed Tests uses → 90% 1e

Directed tests are added to the regression suite to cover specific scenarios.

LINKED ENTITIES

3 links

Functional Verification of a RISC-V Vector Accelerator USES Extracted graph relationship

CI/CD Infrastructure USES Extracted graph relationship

Directed Tests USES Extracted graph relationship

CITATIONS

5 sources

5 citations — click to expand

[1] Regression sets were built from tests classified as passed; failed tests were kept for debugging until fixed. source

[2] The CI flow ranked passed tests by collected coverage and created small and large regression sets. source

[3] The small regression set ran for merge-candidate DUT changes, and the large set ran weekly to ensure recent changes did not break known-good tests. source

[4] Directed tests covering retry and vstart scenarios were added to the regression suite so the scenarios were checked on every RTL change. source

[5] When errors were found, reproduction information was provided; after tentative fixes, regressions were run before merging changes. source