Epiphany: Just wrote a test…for tests
Epiphany: Just wrote a test…for tests!
Problem: We forget to create tests for new components.
Solution: Write one test that assures a corresponding test file exists for each component! 😎
Caveats:
1. Yes, this doesn’t assure the tests are good. But it’s a nice early reminder that enforces the habit of writing tests.
2. Yes, code coverage tools also help solve this. But I like the rapid, clear feedback of this one test: “Cypress test should exist for Tab".
One other benefit: Code coverage reports take a long time to run. So they're typically only run on CI.
In contrast, runs via Jest as part of the unit test suite. So this provides fast, explicit feedback that an integration test is missing.