Skip to content
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

Pass multiple spec in --focus flag #550

Closed
amitkrout opened this issue Dec 14, 2018 · 1 comment
Closed

Pass multiple spec in --focus flag #550

amitkrout opened this issue Dec 14, 2018 · 1 comment
Labels

Comments

@amitkrout
Copy link

I have recently starter contributing in odo project. Most of my contribution is towards the odo e2e test. I am glad to see GinkGo framework as the test framework and infact the tests are running in the CI smoothly.

Now i am planning to use the --focus flag in more user friendly way. See redhat-developer/odo#1138 for more details. When i am passing more than one spec file using separator as , it doesn't work.

How can i pass multiple spec in --focus flag. For example i have 4 specs (spec1,spec2,spec3,spec4) and i want to pass 3 spec file at a time in the --focus flag. TBH i did not get any help from https://onsi.github.io/ginkgo/#focused-specs, or am i looking into the wrong flag and wrong place, if yes would you refer me to that flag/place. Otherwise it would be a nice feature if you guys start looking into it.

@johnSchnake
Copy link

In my experience trying to run the Kubernetes test suite, something like this in Ginkgo would be really valuable. Often it is an art to try and deal with writing just the right regexp that will capture tests A,B,C,D, not X,Y,Z when there are complex/long names involved. It would make it much more simple knowing you could do --focus x --focus y --skip z --skip y.

I'm not sure a much better solution but FYI it would also be great to have a way to provide exceptions to the skip as well. E.g. I want to run all the tests with "Job" in the name but none of the ones about "storage" except for test "foo". It then becomes very difficult (or you have to just do multiple test runs) to get just the right set of tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants