We want to seperate expensive tests for cheap tests to maximize test cost efficiency. For example, we don't want tests that compile and prove circuits to run on every push.
Following seperation should be made:
test: Executes all unit tests with no external dependencies
test:integration: Executes all previous tests plus tests that require external dependencies
test:full: Executes all tests, including tests that compile and prove circuits
test should be executed on every push, test:integration on merging PRs, test:full on merging PRs, but have to be triggered manually.
I'd suggest we extend this with CI cross-integration to starter kit, we'd have to create an e2e test for starter kit too.
Let's not forget splitting the tests into proofs enabled / disabled too.
We want to seperate expensive tests for cheap tests to maximize test cost efficiency. For example, we don't want tests that compile and prove circuits to run on every push.
Following seperation should be made:
test
: Executes all unit tests with no external dependenciestest:integration
: Executes all previous tests plus tests that require external dependenciestest:full
: Executes all tests, including tests that compile and prove circuitstest
should be executed on every push,test:integration
on merging PRs,test:full
on merging PRs, but have to be triggered manually.