cloudron-e2e-test

Fork of the e2e-tests from Cloudron https://git.cloudron.io/iamthefij/e2e-test

Go to file

Ian Fijolek 367b22bcff Adding a test for HTTP/2 I've never really worked with node before and not sure how to run these e2e tests, but this is baed on the usage shown on the project's Github https://github.com/stefanjudis/is-http2		2017-05-03 17:21:34 +00:00
logs	make e2e parallel	2015-11-13 20:15:36 -08:00
test	Adding a test for HTTP/2	2017-05-03 17:21:34 +00: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 appstore.login	2017-04-15 08:21:41 -07:00
cloudron.js	no callback needed	2017-04-15 09:20:47 -07:00
common.js	Fix version	2017-05-01 21:30:21 -07:00
deploy.json	Add e2e_selfhost ssh keys	2017-02-07 11:34:33 +01:00
digitalocean.js	Add missing file	2017-02-02 17:41:28 -08:00
e2etestrunner.js	Give it some more time	2016-12-30 15:30:40 -08:00
imap-probe.js	try harder for ec2 boxes	2016-08-13 00:55:32 -07:00
LICENSE	Add license	2016-09-21 19:06:20 +00:00
mailer.js	better debugs	2016-09-21 13:35:53 -07:00
package.json	Adding a test for HTTP/2	2017-05-03 17:21:34 +00:00
parallel_test.sh	Enable the selfhosting with filesystem test	2017-02-02 08:11:55 -08:00
prepareDeployTarget.sh	Put the ssh keys in the correct folder	2017-02-07 12:11:59 +01:00
README.md	add imap-probe to DEBUG	2016-06-23 14:57:51 -05:00
shell.js	Also bump up the buffer memory	2016-09-13 17:01:48 +02:00
tcpbomb.js	add tcpbomb.js	2017-03-30 16:13:11 -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.