Amend test coverage explanation

This commit is contained in:
Jieyou Xu 2025-06-19 19:12:38 +08:00
parent beb25e1390
commit 6fe303f431
No known key found for this signature in database
GPG Key ID: 045B995028EA6AFC
1 changed files with 8 additions and 4 deletions

View File

@ -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. > 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? > - What does the test coverage landscape for this feature look like?
> - (Positive/negative) Behavioral tests? > - Tests for compiler errors when you use the feature wrongly or make mistakes?
> - (Positive/negative) Interface tests? (e.g. compiler cli interface) > - Tests for the feature itself:
> - Maybe link to test folders or individual tests (ui/codegen/assembly/run-make tests, etc.) > - Limits of the feature (so failing compilation)
> - Are there any (intentional/unintentional) gaps in test coverage? > - 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* *TODO*