Documentation
¶
Overview ¶
Command fixture brings tests/data up to the migrations this tree registers.
go run ./tests/fixture
Every test app is a copy of tests/data, and a copy that lacks a migration runs it before the test begins. Run per app, a dozen migrations cost each one about four seconds, which is how core and apis stopped fitting the runner's limit: the work was the same in every test and none of it was the test. The fixture records the schema the migrations produce, so a test app opens it instead of building it, and tests.TestTheFixtureIsMigrated fails when a new migration is not in it yet.
Click to show internal directories.
Click to hide internal directories.