I think it'd be great if TestBox supported the Given-When-Then style of writing tests. For example if my requirements are:
It would be nice if, instead of having multiple nested describe calls, I could write my test using those phases, something like:
The `feature/scenario/given` functions could be a simple alias for the existing describe function. The `then` function could be a simple alias for the existing it function.
An additional thought is that when you run this you'd get an output shown as I've done my requirements above. This could be done in the code by prefixing the phase to the title. Something like:
This would make the output from the runner read nicely for the product owners if required.
Gliffy Diagrams
Activity
Show:
Aaron LongnionJanuary 12, 2016 at 12:11 AM
Hi - I'd be very interested in any code you have for integrating Gherkin-style tests with TestBox. Thank man!
John WhishSeptember 15, 2015 at 8:26 PM
I've opened a PR for this https://github.com/Ortus-Solutions/TestBox/pull/12 which adds simple support for writing the tests using the phases as aliases for the `describe` and `it` methods. I don't think this conflicts with Kev's work and hopefully compliments it.
KevMSeptember 15, 2015 at 3:13 PM
Yes I'm working on using the new Gherkin 3 parses which is a total re-write to ingest the feature files and execute the step definitions to exercise your code.
Been rather snowed under with many things but will be back on it soon and get an Alpha of it out ASAP.
Brad WoodSeptember 15, 2015 at 3:04 PM
was working on a Gherkins runner for TestBox but I haven't seen it yet. does it do anything like what has described here?
John WhishSeptember 15, 2015 at 2:58 PM
Yes I was thinking of Cucumber-esque language to describing what you are testing within TestBox's existing style.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Reference: http://martinfowler.com/bliki/GivenWhenThen.html
I think it'd be great if TestBox supported the Given-When-Then style of writing tests. For example if my requirements are:
It would be nice if, instead of having multiple nested describe calls, I could write my test using those phases, something like:
The `feature/scenario/given` functions could be a simple alias for the existing describe function.
The `then` function could be a simple alias for the existing it function.
An additional thought is that when you run this you'd get an output shown as I've done my requirements above. This could be done in the code by prefixing the phase to the title. Something like:
This would make the output from the runner read nicely for the product owners if required.