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

Fail when pending tests pass #374

Closed
gaffo opened this issue Sep 5, 2017 · 7 comments
Closed

Fail when pending tests pass #374

gaffo opened this issue Sep 5, 2017 · 7 comments

Comments

@gaffo
Copy link

gaffo commented Sep 5, 2017

Would it be possible to run pending specs and only fail them when they pass? This was a nice feature of cucumber once upon a time basically saying "hey this now works" and trying to keep the number of pending specs small.

@williammartin
Copy link
Collaborator

@gaffo Could you elaborate on this a little, I'm not sure I fully understand the feature. What is the UX you forsee?

@gaffo
Copy link
Author

gaffo commented Dec 4, 2017 via email

@williammartin
Copy link
Collaborator

No sorry, are you describing your other open issue #377 ?

@gaffo
Copy link
Author

gaffo commented Dec 4, 2017 via email

@gaffo
Copy link
Author

gaffo commented Dec 4, 2017

So basically in some other test frameworks you can run in a special mode where you say "if a pending spec passes, it should fail" this way you see the test failures as specs that should be running every time. Eg, these are specs that are accidentally off. It's a tool that helps with cleanup. I used it with cucumber before and it basically would fail the build if we had specs that should have been enabled but were not.

Does that make sense?

@williammartin
Copy link
Collaborator

Oh yeh that's definitely an interesting feature. Do you happen to have a link to the Cucumber feature, maybe we could follow the same UX?

@onsi
Copy link
Owner

onsi commented Apr 6, 2021

I'm working through the backlog of old Ginkgo issues - apologies as this issue is probably stale now.

I think --failOnPending was introduced after this issue? And I think it solves this use case?

I'm going to close this for now, but feel free to reopen it if you'd like.

@onsi onsi closed this as completed Apr 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants