WIP: Contribution contracts tests #159
18
.travis.yml
18
.travis.yml
@ -15,21 +15,25 @@ cache:
|
|||||||
- apps/token/node_modules
|
- apps/token/node_modules
|
||||||
- apps/vault/node_modules
|
- apps/vault/node_modules
|
||||||
|
|
||||||
|
env:
|
||||||
|
- TASK=lint:wrapper
|
||||||
|
- TASK=lint:contract-tests
|
||||||
|
- TASK=test:token
|
||||||
|
- TASK=test:contributor
|
||||||
|
- TASK=test:contribution
|
||||||
|
- TASK=test:proposal
|
||||||
|
|
||||||
|
|||||||
install:
|
install:
|
||||||
- npm install -g @aragon/cli
|
- npm install -g @aragon/cli
|
||||||
- npm install -g truffle
|
- npm install -g truffle
|
||||||
- npm install
|
- npm install
|
||||||
|
|
||||||
before_script:
|
before_script:
|
||||||
- npm run devchain &
|
- npm run devchain > /dev/null &
|
||||||
|
- sleep 5
|
||||||
|
|
||||||
script:
|
script:
|
||||||
- npm run lint:wrapper
|
- travis_wait 60 npm run $TASK
|
||||||
- npm run lint:contract-tests
|
|
||||||
- npm run test:token
|
|
||||||
- npm run test:contributor
|
|
||||||
- npm run test:contribution
|
|
||||||
- npm run test:proposal
|
|
||||||
|
|
||||||
branches:
|
branches:
|
||||||
only:
|
only:
|
||||||
|
Loading…
x
Reference in New Issue
Block a user
This should be the same as the test script itself, because
&&
is supposed to exit with 1, if any of the commands on the way exit with 1.yeah true, I changed that also to
It is the same also, but
> /dev/null &
to not show the output and usingTASK
for better visualization I think...But the thing is there is an error in Contribution tests, but it doesn't exit with 1!
I don't see how the env vars make it clearer. I think it's actually less understandable that way. In fact, I wouldn't even know off the top of my head what happens when you assign the same env variable twice.
Yes, that's the thing that needs to be fixed I think. Not how the tests are run. The test task should just be
npm test
and nothing else, in my opinion.What I meant by the env vars make it clearer, in Travis u don't need to look at the whole log in case a test fail...

Oh, I see. The feature you're looking for is the build matrix:
https://docs.travis-ci.com/user/customizing-the-build/#naming-jobs-within-matrices