在BDD中，将尚未实现的测试与实现的测试分开的策略是什么？

Question

In behaviour driven development, you write the tests first.

However, when you are in the middle of development and you have a functional but limited application, some tests will have been implemented and some will not have been.

How do you keep all the failures of the not-yet-implemented tests from obscuring the true errors?

Answer 1

I found the solution here:

https://github.com/Codeception/Codeception/issues/3823

Mark the scenarios with a tag (e.g. incomplete) and then use:

codecept run functional --skip-group incomplete