Tyler-Keith-Thompson
commented
2 years ago Trying to use an XCTest failure before tests were actually up and running was a fools errand. Instead I've chosen to assert that features were found which will trap at runtime. I think this approach gives consumers the feedback they need and it should not suffer side-effects from other tests running.
When the new DocC stuff is put together I'll link to it from the assertion error message.
Is your feature request related to a problem? Please describe. Multiple consumers have had problems with understanding whether features are being found in files. This has lead to a pain point with early library adoption.
Describe the solution you'd like One obvious approach is to have CucumberSwift throw an XCTFail if it discovered no features. Bonus points if it can link to documentation and/or provide tips on what might be wrong.
Describe alternatives you've considered No alternatives worth mentioning come to mind.
Additional context It's important to realize it's not just iOS devs who are trying to work with CucumberSwift. This means that we should try and write documentation and errors with as little assumptions as possible while still providing terse, useful output.