Johannes Zellner d6badf8a2b Cleanup DO instances after test runs
We should be doing this the same way as with caas tests
where we are smart enough to only delete those where
tests were successful
2016-09-09 10:04:09 +02:00
2015-11-13 20:15:36 -08:00
2016-09-09 10:04:09 +02:00
2015-06-14 21:39:55 -07:00
2016-06-30 15:21:56 +02:00
2016-09-08 09:17:42 -07:00
2016-09-08 09:17:42 -07:00
2016-09-01 19:00:19 -07:00
2015-11-19 13:49:13 -08:00
2016-08-13 00:55:32 -07:00
2016-06-24 11:46:08 -05:00
2016-09-08 13:15:34 +02:00
2016-06-23 14:57:51 -05:00
2016-09-08 09:20:47 -07:00

To run manually on CI

cd ~/app
export BOX_VERSION=<version_to_test>

pm2-run --ecosystem ../ecosystem.json --env staging --cmd "npm test"

                OR

pm2-run --ecosystem ../ecosystem.json --env staging --cmd ./parallel_test.sh

To run specific test on CI

cd ~/app
export BOX_VERSION=<version_to_test>
pm2-run --ecosystem ../ecosystem.json --env staging --cmd "DEBUG=imap-probe,superagent-sync,e2e:* DEBUG_COLORS=true ./node_modules/.bin/mocha --bail test/new-user-test.js"

AWS Keys

AWS_STAGING_ACCESS_KEY and AWS_STAGING_SECRET_KEY exist for the release tool to make a new release.

Description
Fork of the e2e-tests from Cloudron https://git.cloudron.io/iamthefij/e2e-test
Readme 384 KiB
Languages
JavaScript 96.7%
Shell 3.3%