-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal: split e2e tests into their respective repositories #17
Comments
From @arschles on January 19, 2016 23:17 Requesting comments/ideas @jchauncey @slack @sgoings |
From @sgoings on January 20, 2016 21:43 How would one "run all the e2e tests" after this split up? |
From @jchauncey on January 21, 2016 16:7 So my first thought is to do the following:
|
From @arschles on January 21, 2016 16:21 I agree mostly with @jchauncey. Specifically, each component can have a package called However, we can construct that code in such a way that this repository can I hope I've explained that sufficiently It'll be fairly self explanatory after showing a prototype for a test or 2. |
From @arschles on January 19, 2016 23:10
For example, all the tests that use the
deis
CLI to run stuff against the controller, should be back indeis/workflow
and thegit push
tests should be indeis/builder
. This repository should pull all those tests together and run them in a harness.Copied from original issue: deis/workflow-e2e#26
The text was updated successfully, but these errors were encountered: