tame and Cucumber
Do Cucumber without writing each scenario by hand
Cucumber is a popular BDD framework. Its language, Gherkin, provides many teams with a common syntax and structure for writing tests.
This Given-When-Then language lets teams define scenarios in natural language. Tools in the Cucumber family can generate code to enable automated unit and UI testing.
But a popular common syntax does not address the problem of how to devise those many scenarios. Testers still have to create them one at a time.
Fortunately, TAME can create all the Gherkin BDD scenarios from a single test workbook.
Just hit the Gherkin button
When in Excel, just hit the Gherkin button and TAME generates a Gherkin feature file.
How to get great Gherkin
1. Use values
Real scenarios are specific. It's not enough just to say, "enter a good email address that names a real user." Specify an actual value.
Define values based upon input and environment condition choices.
In many cases it's also useful to define a default value for each input.
2. Write detailed directions
To make the tests even more readable, write detailed directions for each input, event, and result. By doing this you can create a test protocol that's as readable as something written by hand.
The result is a series of scenarios produced quickly and easily, ready for review and testing.
3. Combine steps into complete activities
Start by testing individual functions such as the Login page. Then combine these single functions into sequences.
