-
Notifications
You must be signed in to change notification settings - Fork 244
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
Run component test in parallel #1797
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -158,35 +158,36 @@ $ MINISHIFT_ENABLE_EXPERIMENTAL=y minishift start --extra-clusterup-flags "--ena | |
|
||
* `odo` and `oc` binaries in `$PATH`. | ||
|
||
.Procedure: | ||
|
||
To deploy an integration test: | ||
.How to write: | ||
|
||
Refer to the odo clean test link:https://github.com/openshift/odo/blob/master/tests/template/template_cleantest_test.go[`template`]. | ||
|
||
* For the entire integration suite use: | ||
---- | ||
$ make test-e2e | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @amitkrout again, you're removing documentation and not adding it again... no documentation on There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ahh...my bad. Will update it There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||
---- | ||
.Procedure: | ||
|
||
* For the generic tests use: | ||
---- | ||
$ make test-generic | ||
---- | ||
Integration tests can be run in the following two ways: | ||
|
||
* For the component tests use: | ||
* To run the component test in parallel (default: 4 ginkgo test node), on a test cluster : | ||
+ | ||
---- | ||
$ make test-cmp-e2e | ||
---- | ||
+ | ||
|
||
* For the service catalog tests use: | ||
* To run component test sequentially or on single ginkgo test node use enviornment variable `TEST_EXEC_NODES`: | ||
+ | ||
---- | ||
$ make test-service-e2e | ||
$ make test-cmp-e2e TEST_EXEC_NODES=1 | ||
---- | ||
+ | ||
|
||
* For the e2e scenario test use: | ||
* For the entire integration test suite use: | ||
+ | ||
---- | ||
$ make test-e2e-scenarios | ||
$ make test-integration | ||
---- | ||
+ | ||
|
||
NOTE: `make test-integration` doesn't honour enviornment variable `TEST_EXEC_NODES`. So by default it runs the entire integration test suite on a single ginkgo test node sequentially. | ||
|
||
You can run a subset of tests with ginkgo by using focused specs mechanism https://onsi.github.io/ginkgo/#focused-specs | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why are we now randomizing? you need to document this in your PR description / commit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://github.com/openshift/odo/pull/1797/files#diff-b67911656ef5d18c4ae36cb6741b7965R114