From 6fe303f4310176f5c87a0f686ea9ff8915f3ae35 Mon Sep 17 00:00:00 2001 From: Jieyou Xu Date: Thu, 19 Jun 2025 19:12:38 +0800 Subject: [PATCH] Amend test coverage explanation --- src/stabilization_report_template.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/src/stabilization_report_template.md b/src/stabilization_report_template.md index 75b84b0e..3a6c8e17 100644 --- a/src/stabilization_report_template.md +++ b/src/stabilization_report_template.md @@ -43,10 +43,14 @@ > Within each test, include a comment at the top describing the purpose of the test and what set of invariants it intends to demonstrate. This is a great help to those reviewing the tests at stabilization time. > > - What does the test coverage landscape for this feature look like? -> - (Positive/negative) Behavioral tests? -> - (Positive/negative) Interface tests? (e.g. compiler cli interface) -> - Maybe link to test folders or individual tests (ui/codegen/assembly/run-make tests, etc.) -> - Are there any (intentional/unintentional) gaps in test coverage? +> - Tests for compiler errors when you use the feature wrongly or make mistakes? +> - Tests for the feature itself: +> - Limits of the feature (so failing compilation) +> - Exercises of edge cases of the feature +> - Tests that checks the feature works as expected (where applicable, `//@ run-pass`). +> - Are there any intentional gaps in test coverage? +> +> Link to test folders or individual tests (ui/codegen/assembly/run-make tests, etc.). *TODO*