mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-10-05 03:21:16 +08:00
Mathias Bynens
79e2cf0633
This also adds CC-BY-4.0 to the list of accepted licenses. DISABLE_THIRD_PARTY_CHECK=update dependencies Bug: chromium:1083142 Change-Id: I8612de2fba52dae32eeb71af79d5aacfde52142b Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2220097 Reviewed-by: Paul Lewis <aerotwist@chromium.org> Commit-Queue: Mathias Bynens <mathias@chromium.org>
24 lines
965 B
Markdown
24 lines
965 B
Markdown
# Writing system tests
|
|
|
|
System tests verify that stylelint works as expected. They are another line of defense against regressions, after the unit tests and integration tests.
|
|
|
|
Each of these system tests asserts that we end up with some expected output, given a configuration and a stylesheet.
|
|
|
|
These tests should not be comprehensive and systematic (_the unit tests should_). They should reproduce real use-cases and verify that those use-cases work as expected.
|
|
|
|
## Jest snapshots
|
|
|
|
The tests use Jest snapshots, so we can easily:
|
|
|
|
- assert against potentially large objects and strings
|
|
- update expectations as needed.
|
|
|
|
## The pattern
|
|
|
|
To add a system test, you should:
|
|
|
|
- add a test-case folder to `system-tests/` incrementing the number from existing test cases
|
|
- add a configuration file and a stylesheet
|
|
- add a `fs.test.js` and `no-fs.test.js` following the format established by existing tests, and using the `systemTestUtils`
|
|
- take a snapshot of `output`
|