iamthefij/cloudron-e2e-test
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
Fork of the e2e-tests from Cloudron https://git.cloudron.io/iamthefij/e2e-test
414 Commits 2 Branches 0 Tags 384 KiB
JavaScript 96.7%
Shell 3.3%
d6badf8a2b
Go to file
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
logs make e2e parallel 2015-11-13 20:15:36 -08:00
test Cleanup DO instances after test runs 2016-09-09 10:04:09 +02:00
.gitignore Add .gitignore 2015-06-14 21:39:55 -07:00
.jshintrc tell linter we use esnext 2016-06-30 15:21:56 +02:00
appstore.js use staticIp 2016-09-08 09:17:42 -07:00
cloudron.js use staticIp 2016-09-08 09:17:42 -07:00
common.js bump test app version 2016-09-01 19:00:19 -07:00
deploy.json Use cloudron-cli as a asset just like release 2016-06-30 16:26:29 +02:00
e2etestrunner.js do not send stderr in email 2015-11-19 13:49:13 -08:00
imap-probe.js try harder for ec2 boxes 2016-08-13 00:55:32 -07:00
mailer.js have same text 2016-06-24 11:46:08 -05:00
package.json Replace sleep node module with execSync(sleep) 2016-06-30 16:18:10 +02:00
parallel_test.sh Rename ec2 selfhost test 2016-09-08 13:15:34 +02:00
prepareDeployTarget.sh Use cloudron-cli as a asset just like release 2016-06-30 16:26:29 +02:00
README.md add imap-probe to DEBUG 2016-06-23 14:57:51 -05:00
shell.js bump the buffer size 2016-09-08 09:20:47 -07:00

README.md

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.