-
-
Notifications
You must be signed in to change notification settings - Fork 147
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
Possible of generate empty tests with a "Pending" warning? #75
Comments
I think this is more of a cypress / mocha thing - what happens if you put this.skip() inside your step definition? |
It just skips it, and the test itself marks as passing (if only skipped steps are left) I've tried to throw an error saying "Step pending" or just not write the step until I get to it, but both cases, it seems to override the entire test ,Cypress doesn't show the other steps that were executed before. i.e. I have a step that is pending, where I just do an 'assert.isTrue(false)'. The error emerges, but it does not show the previous steps |
return this.pending(); |
I would love to have a way to write specs that are 'Pending' in the sense of a 'TODO: Write this step'. The following is what Cypress does with Mocha tests:
The 2 skipped steps are reported in the pale blue highlight in the log panel and the final step runs. So, given this feature:
And this step def:
This does tell Cypress to skip:
ie it displays the pale blue "skipped" style, but it also prevents any further steps from running (unlike the Mocha test above which executed the remaining step). If I change it to this:
all steps run (and the Log entries are after 2 Passing assertions). The 'Skips' step is just logged. If I remove that So, in Mocha / Cypress, the Are my assumptions correct here and is there any way we can have Thanks. It is just a small thing but would be great to have it work so we can visually see which feature steps are not yet implemented. Cheers, |
I see what you are saying and I would love to have that as well, but at this moment I don't see a way to achieve that, as Cypress forces us to treat all steps as one test. you can try to introduce a warning instead of the this.skip but that will be easy to miss for example in the CI (which is the point of pending tests as far as I understand). |
OK. All good. Just as long as it is on the radar! Thanks, |
Hello - any updates on the development of this feature? |
This feature would be awesome... right now, not being able to set a scenario as "pending" with cucumber is what's hindering me from using cypress... |
Any update here? My use case is the following: Is there a way to do that? I came up with an approach like that, but I can not seem to get it running: |
Any update on this? |
It is a good feature to have. As right now, the result table of the test show pending |
Anyone here found a way to achieve the desired behaviour? |
I have used cucumber with Java and to acheive this you throw a PendingException() is there a similar concept that can be used here? |
While this doesn't address the bigger issue, this is helpful: https://github.com/cypress-io/cypress-skip-test |
hi! when using versions
config
|
Yeah i use the skip-test plugin too. but in my json file is every expected |
Due to personal reasons, the previous maintainers of this package are stepping down and handing the reigns over to me, a long-time contributor to the project and a user of it myself. This is a responsibility I'm very excited about. Furthermore, I'd like to thank @lgandecki ++ for all the work that they've done so far. Read more about the transfer of ownership here. The repository has however moved and all outstanding issues are being closed. This is not a reflection of the perceived importance of your reported issue. However, if after upgrading to the new version, you still find there to be an issue, feel free to open up another ticket or comment below. Please make sure to read CONTRIBUTING.md before doing so. |
I have to leave all tests empty, which gives a false status of passing and fails on guiding the development process.
Is there any way to do it? Or am I missing it? #
The text was updated successfully, but these errors were encountered: