tyler.durden/test262
1
0
Fork 0
mirror of https://github.com/tc39/test262.git synced 2025-05-30 03:30:30 +02:00
Code Issues Packages Projects Releases Wiki Activity

fixup! Document rationale for some maintenance practices

Browse Source
This commit is contained in:
Mike Pennisi 2022-03-25 19:39:50 -04:00 committed by Philip Chimento
parent 17238ca018
commit f59823860e
1 changed files with 8 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
docs/rationale.md
View File

@ -26,7 +26,7 @@ For instance:
Since existing tests do not necessarily reflect the project's current Since existing tests do not necessarily reflect the project's current
best-practices, it's especially important for test authors to familiarize best-practices, it's especially important for test authors to familiarize
themselves with the contribution guidelines. themselves with [the contribution guidelines](CONTRIBUTING.md).
## Test generation ## Test generation
@ -134,20 +134,14 @@ to learn.
When testing a syntactic feature of the language, it can be tempting to write When testing a syntactic feature of the language, it can be tempting to write
tests which verify that some bit of source text does *not* produce a syntax tests which verify that some bit of source text does *not* produce a syntax
error. Contributors should try to push beyond verifying only the lack of a error. Contributors should try to push beyond verifying only the lack of a
syntax error because almost all such tests also have observable semantics. It's syntax error because such tests also have observable semantics. It's better for
often better for a test to assert that the expected semantics are followed, a test to assert that the expected semantics are followed.
even when they may already be covered elsewhere.
However, this is not always desirable because verifying semantics invariably However, verifying semantics invariably requires inserting still more code, and
requires inserting still more code, and that additional code may degrade the that additional code may degrade the tests' precision for verifying syntax. For
tests' precision for verifying syntax. cases where this trade-off is significant, contributors may consider submitting
simplified tests to [the test262-parser-tests
When considering this tension, be aware that TC39 maintains [a separate project project](https://github.com/tc39/test262-parser-tests).
called test262-parser-tests](https://github.com/tc39/test262-parser-tests).
This project was partially motivated by a desire to offer test material that
isn't (and perhaps cannot be) related to any specific grammar production. The
availability of that project may inform decisions about if, where, and how to
include tests for syntax in Test262.
## Avoiding abstraction ## Avoiding abstraction