Hi Tim,
I've recently also felt the need for this feature. OTOH, I would see it
like a "dry-run" in which the steps are matched but not executed.
It should not be difficult, but we'd need to have a closer look. Please
create a Jira issue for it.
Cheers
On 10/05/2010 13:18, Tim Moore wrote:
> I think this must already have been discussed but I haven't seen it? I know
> that it came up at the recent ACCU meeting in Oxford, UK, so it's an issue
> people are talking about.
>
> Is there a way to "parse" scenarios and determine whether all steps are
> matched
> without running the scenario? i.e. there are no Pending steps.
>
> Note: I'm guessing steps can be added dynamically? Obviously you can't skip
> running the steps in that case and expect anything sane to happen.
>
> However we don't want to do this, and we already fail the tests if there are
> Pending steps so we aren't concerned about writing tests before code (at the
> moment). What we'd like is to know is whether all of the steps actually match.
> This problem often occurs as a consequence of refactoring the step definitions
> themselves, and since our scenarios take significant time to run, we often
> don't find out about the problem for some time (especially if other build
> failures hold up the BDD tests). Of course if our builds were hyper-fast then
> this wouldn't be a problem, but I don't expect you can help us there :)
>
> If the Configuration passed into runScenarioSteps could provide the initial
> State, I'm thinking it would be quite easy for the State to skip running the
> step and just determine whether it had been matched?
>
> Tim
>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
