jand3r/swift-behave

Behaviour-driven testing framework on top of the Xcode UI Tests that allows to define acceptance tests using a natural language that all team members understand.

swift-behave's Issues

Execute scenarios in the order of their appearance in the story file

Depending on the overall structure of your test cases it could be that you like to define scenarios that are building on each other instead of re-launching the app under test for each scenario. Therefore it is essential that the scenarios are executed in the same order that they are defined in the .story file.

Setting scenario-specific app environment variables

Add a statement that allows to set environment variables on a per-scenario-basis.

With this feature you can control some of your app's behaviour to allow testing variants without changing productive code, e.g. you could provide a CLIENT_ID to control which mock data is returned at runtime.

Update example app for latest Swift version

Add story file parse error handling

Qualified messages should assist the developer or tester in finding errors in the story files.

Support for "Scenario Outline" and "Examples"

It should be possible to use placeholders in a scenario and fill them from a table of variants. In Gherkin this can be done via a Scenario Outline followed by an Examples table. Placeholders are specified like e.g. <variable>. The Examples table contains a row for each scenario outline execution and has a column for each placeholder used.

Add language construct to execute actions multiple times

Support of a language construct to execute a "when" action multiple times...

Example: Instead of repeating the same line multiple times

When I add the item with barcode 123456 to the basket
And I add the item with barcode 123456 to the basket
And I add the item with barcode 123456 to the basket

write this:

When I add the item with barcode 123456 to the basket 3 times