|
43 | 43 | > 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. |
44 | 44 | > |
45 | 45 | > - What does the test coverage landscape for this feature look like? |
46 | | -> - (Positive/negative) Behavioral tests? |
47 | | -> - (Positive/negative) Interface tests? (e.g. compiler cli interface) |
48 | | -> - Maybe link to test folders or individual tests (ui/codegen/assembly/run-make tests, etc.) |
49 | | -> - Are there any (intentional/unintentional) gaps in test coverage? |
| 46 | +> - Tests for compiler errors when you use the feature wrongly or make mistakes? |
| 47 | +> - Tests for the feature itself: |
| 48 | +> - Limits of the feature (so failing compilation) |
| 49 | +> - Exercises of edge cases of the feature |
| 50 | +> - Tests that checks the feature works as expected (where applicable, `//@ run-pass`). |
| 51 | +> - Are there any intentional gaps in test coverage? |
| 52 | +> |
| 53 | +> Link to test folders or individual tests (ui/codegen/assembly/run-make tests, etc.). |
50 | 54 | |
51 | 55 | *TODO* |
52 | 56 |
|
|
0 commit comments