From custom tests to Common Test
summary
Replaces Riak's brittle custom runner with Common Test, migrating dozens (not all of ~300) legacy suites so huge confirm/0 monsters split into meaningful test cases and yield precise failures instead of 400-line stack dumps. Extracts the code intercept library into its own repo (about 40 intercept-based tests use it) to inject delays, drop or corrupt replies at runtime. Pins a bundled rebar3 profile to support Erlang/OTP 16 and runs multi-release test batches; the new setup works for migrated suites but cross-release interaction testing remains unimplemented.
AI-written summary · about
chapters (15)
- 0:00Start
- 1:13OUTLINE
- 2:39HOW DO YOU TEST THE PROPERTIES OF A SYSTEM
- 4:02COMMON TEST FEATURES
- 5:37NON-TRIVIAL TESTING SETUPS ON COMMON TEST
- 6:23WHAT A GREAT OPPORTUNITY TO BUILD A TESTING FRANEWORK
- 7:59THE TEST RUNNER SCRIPT - STARTING OUT SIMPLE
- 8:30THE TEST RUNNER SCRIPT - THE SIMPLEST TEST CASE
- 11:42RIAK TEST RUNNER SUMMARY
- 14:10CODE INTERCEPTS IN PRACTICE - TRIGGERING INTERCEPT
- 19:25REPLACING RIAK TEST RUNNER
- 20:06CONSTRAINTS
- 24:36CURRENT STATUS
- 25:43BONUS OBJECTIVES
- 27:54THREE BIG REASONS TO CONSIDER BEING A MENTOR
related talks
01h 00mTesting Heresies
35mA Whirlwind Tour of Testing in Elixir
38mMinitest 6: test feistier!
34mTesting legacy code when you dislike tests (and legacy code)
35mTest automation guide: How to move away from chain tests
34mEliminating Inconsistent Test Failures
48mModern Testing Patterns
23mAdaptive Testing