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

pending library steps #32

Closed
hans-d opened this issue Oct 21, 2013 · 4 comments
Closed

pending library steps #32

hans-d opened this issue Oct 21, 2013 · 4 comments

Comments

@hans-d
Copy link
Contributor

hans-d commented Oct 21, 2013

Feature: pending steps
  In order to have a working library
  As a feature library developer
  I want to mark some steps as pending

Scenario: Making the test runnable with all steps pending
 Given a feature file with scenarios and steps
 and no time to develop the complete library required for it
 and I create the step definitions in the library
 and use next().pending or something like it as step definition
 When I run the tests using eg mocha (or framework that supports pending tests)
 Then the feature must be runnable
 and not produce errors
 and not produce failing tests
 but scenarios should be marked as pending

Scenario: Making the test runnable with some steps pending
 Given a feature file with scenarios and steps
 and no time to develop the complete library required for it
 and I create the step definitions in the library
 and use next().pending or something like it as step definition for some steps
 and next() for the other steps without any failing assertions
 When I run the tests using eg mocha (or framework that supports pending tests)
 Then the feature must be runnable
 and not produce errors
 and not produce failing tests
 but scenarios having one or more steps marked pending should be marked as pending 
 and scenarios having no steps marked pending should be normally run and not marked pending

@hans-d
Copy link
Contributor Author

hans-d commented Oct 22, 2013

https://github.com/acuminous/yadda#functions, but following the advice here i get stack traces :-(

@cressie176
Copy link
Member

Maybe the documentation isn't clear enough, what I mean by not implementing a function is...

library.given(/some step text/);

However the downside of this approach is that your test running won't know that the test is incomplete. I mentioned in issue 30 that I'll investigate emitting an UNIMPLEMENTED_STEP event and see if I can get mocha to report a pending step.

@poum
Copy link
Contributor

poum commented Apr 16, 2014

should be great

@cressie176
Copy link
Member

I've worked out a way of doing (you remove the function from the mocha test at runtime) however it's going to require a substantial re-write. There's a lot of other changes that the original Yadda design didn't allow so I've started playing with my ideas here once they get a bit more stable I'll branch yadda work from there.

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