Fork of the e2e-tests from Cloudron https://git.cloudron.io/iamthefij/e2e-test
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Girish Ramakrishnan d0bc8b3408 Fix version 2 years ago
logs make e2e parallel 3 years ago
test checkForUpdates 2 years ago
.gitignore Add .gitignore 4 years ago
.jshintrc tell linter we use esnext 3 years ago
LICENSE Add license 2 years ago
README.md add imap-probe to DEBUG 3 years ago
appstore.js use appstore.login 2 years ago
cloudron.js no callback needed 2 years ago
common.js Fix version 2 years ago
deploy.json Add e2e_selfhost ssh keys 2 years ago
digitalocean.js Add missing file 2 years ago
e2etestrunner.js Give it some more time 2 years ago
imap-probe.js try harder for ec2 boxes 3 years ago
mailer.js better debugs 2 years ago
package.json fix new-user-test 2 years ago
parallel_test.sh Enable the selfhosting with filesystem test 2 years ago
prepareDeployTarget.sh Put the ssh keys in the correct folder 2 years ago
shell.js Also bump up the buffer memory 2 years ago
tcpbomb.js add tcpbomb.js 2 years ago

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.