/Testing

Tests That Help You Find Defects Faster

- Philipp Giese tl;dr: Each test should (1) test one thing (2) use precisely the data it needs (3) be disconnected from other tests (4) provide context to find the problem in error messages.

featured in #194


Spark Joy By Running Fewer Tests

- Jessica Xie tl;dr: Shopify's codebase has ~150,000 tests, this number is growing and expensive to run leading them to implement Dynamic Analysis. The article outlines what Dynamic Analysis is, and pros and cons.

featured in #186


3 Steps To Add Tests On Existing Code When You Have Short Deadlines

- Nicolas Carlo tl;dr: When you don't much time to write tests, try this: (1) Generate an output you can snapshot (2) use test coverage to find all input combinations (3) use mutations to verify your snapshots. 

featured in #177


How To Report Bugs (If You Want Them Fixed)

tl;dr: Boilerplate on how non-technical members of your team should report bugs to engineers.

featured in #155


Farewell To fsync(): 10× Faster Database Tests With Docker

- Shobhit Agarwal tl;dr: When running tests you don't care about writing to your database. Using Docker to create a DB instance and disabling fsync(), you are able to run tests 10x faster.

featured in #132