So to take the point around behaviour further I would recommend having a look at BDD(behaviour driven development) there's 2 things in particular that will help. 1. the tests are writing so that when reading the test you can quickly understand what its doing and then drill into the functions to find out how its doing it. 2. Separate the tests into separate functions and split it down into Arrange, Act, Assert. It feels like more code but in the long term will help with documenting behaviour for new developers and will help you to find/fix issues with tests or with the application
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.