test

From my observation, code bases with a high test coverage and a certain level of complexity tend to have cluttered and messy tests. Such tests are often dominated by the preparation step in order to prepare test data or bring the system into a state required for the test. The actual test code, such as invocation of the component-under-test and verification of the results, can easily be buried under the preparation step. To ease such problems and to improve readability and maintainability of test code in general, I like to combine the Builder pattern with the Object Mother pattern and randomized test data.

While using the WebdriverIO browser automation test framework based on the Webdriver protocol, I got stuck with this error: invalid element state: invalid element state. The error occurred when interacting with an input element. Since this error message is not very descriptive, I want to point to the solution for my situation.

Alex Gilleran brings up very valid criteria on great tests in his post that I strongly recommend: https://blog.alexgilleran.com/test-against-what-wont-change.