Calling verify at the beginning and then after the prep steps is a waste of cycles. By delaying the call to verify until after the tests are run we also take advantage of any pre/post tests tasks added to the package.json.
We found that calling verify immediately conflicted with our release process:
clean (remove node_modules and lib)
setup (npm install)
npub publish X
Calling verify immediately caused it to fail since our checkout was dirty (missing lib contents). Part of our test process is to build the coffee. By verifying the git status after prep and test we cover all our bases.
abloom
commented
9 years ago
Calling
verifyat the beginning and then after theprepsteps is a waste of cycles. By delaying the call toverifyuntil after the tests are run we also take advantage of any pre/post tests tasks added to thepackage.json.We found that calling verify immediately conflicted with our release process:
Calling verify immediately caused it to fail since our checkout was dirty (missing lib contents). Part of our test process is to build the coffee. By verifying the git status after prep and test we cover all our bases.