cloudron-e2e-test/test
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
..
after.js none of these are executable 2016-04-15 21:35:10 -07:00
alt-domain-test.js the cloudron test-app requires email for the addon_check 2016-09-01 23:08:38 -07:00
app-flow-test.js the cloudron test-app requires email for the addon_check 2016-09-01 23:08:38 -07:00
app-update-test.js the cloudron test-app requires email for the addon_check 2016-09-01 23:08:38 -07:00
before.js none of these are executable 2016-04-15 21:35:10 -07:00
cloudron-autoupdate-sfo1-test.js Revert "email api does not exist in old version" 2016-09-07 23:18:28 +02:00
cloudron-backup-test.js use staticIp 2016-09-08 09:17:42 -07:00
cloudron-button-test.js Replace sleep node module with execSync(sleep) 2016-06-30 16:18:10 +02:00
cloudron-migrate-test.js wait more 2016-09-01 20:55:07 -07:00
cloudron-update-ams3-test.js Get token first, then enable email 2016-09-08 22:17:30 +02:00
cloudron-user-test.js enable email 2016-09-01 09:03:27 -07:00
new-user-test.js Revert "Check for LA timezone on sfo cloudron" 2016-09-08 00:06:37 +02:00
selfhost-digitalocean-test.js Cleanup DO instances after test runs 2016-09-09 10:04:09 +02:00
selfhost-ec2-test.js Cleanup DO instances after test runs 2016-09-09 10:04:09 +02:00