Wojtek
Wojtek
#### Description Usually, scenarios are composed from the steps that somehow alters the service/system under test, i.e. they may be creating/altering some domain specific objects or resources. In most cases,...
#### Description Following on #257 LightBDD should offer an ability to run scenarios multiple times, where: * all run details are present in the reports, * re-run strategy could be...
#### Description The HTML report is a few years old and looks pretty outdated. This ticket is a high level epic about revisiting the report layout, features and visualization to...
#### Description Implement package allowing to report execution progress in jsonl format with ability to serialize and deserialize it #### Progress - [ ] Feature is implemented, - [ ]...
#### Description Introduce: - test execution starting and finished events - feature, scenario, step discovery event - inline and tabular discovery, validation starting and validation finished events - tabular row...
#### Description Revisit documentation pages to be more intuitive: * check if Readme page can be make slimmer (and move of the some details to the wiki pages), * make...
#### Description Update projects with `enable` #### Progress - [ ] LightBDD.Core migrated - [ ] LightBDD.Framework migrated - [ ] Integration projects migrated - [ ] Test projects migrated
#### Description Currently, a typical step method code that needs to resolve something programmatically from the DI has to have `using LightBDD.Core.Dependencies;` in order to use generic `Resolve()` method to...
Update [Scenario State Management](https://github.com/LightBDD/LightBDD/wiki/Scenario-State-Management) page with example from: https://gist.github.com/Suremaker/10b2f05c844fe2e657f74b647a7074be
#### Description Split scenario styles to separate pages Ensure that examples are self explanatory Change 'syntax' to 'style' or 'type'? Add clear use cases for given style. Add hints on...