dce/davideisinger.com
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[testing] not too DRY

Browse Source
This commit is contained in:
David Eisinger
2023-07-24 14:19:40 -04:00
parent b109e81b0a
commit 79a97f665d
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
content/notes/good-tests/index.md
View File

@@ -59,6 +59,12 @@ _(Notes for a Viget article I'm putting together)_
* [rspec-retry][6] * [rspec-retry][6]
* In general, though, flaky tests suck and generally indicate lack of quality with either your code or your tools * In general, though, flaky tests suck and generally indicate lack of quality with either your code or your tools
* So write better code or pick better tools * So write better code or pick better tools
* Tests are code, but they're not application code
* And the way you approach them should be slightly different
* Some (or even a lot of) repetition is OK; don't be too quick to refactor
* Ideally someone can get a sense of what a test is doing by looking at a single screen of code
* As opposed to jumping around between early setup, shared examples, complex factories w/ side-effects, etc.
* Think of it as half programming, half writing
[1]: https://en.wikipedia.org/wiki/Test-driven_development [1]: https://en.wikipedia.org/wiki/Test-driven_development
[2]: https://www.viget.com/articles/maintenance-matters-code-coverage/ [2]: https://www.viget.com/articles/maintenance-matters-code-coverage/