Share domain knowledge with the tests

While dealing with a complex domain and not having nice Gherkin-based tests, the best you can do to describe the behaviour of the system in test using:

• nice and descriptive test names

• and by specifying decent explanatory comments for the upcoming developers which will read your code, maintain it and have some tests broken