I'm trying to improve the concept of scenario-driven unit tests in Codeception.
The goal is to make them:
- readable
- easiest for mocks
- IDE friendly
- better with very\long\PSR\class\names
Here I took one sample unit test with mocks from this blog post. Despite author says that was wrong for him to write such test, let's try rewriting it with new Codeception paradigm.