This blog post is my experience about UI test automation applied in various projects.
First disclaimer, this post is not against UI check automation. If not used as a testing hammer, it can help towards better product quality.
How to recognize UI automation as marker for important project issue? If project testing pyramid morphs into testing coan [source: Watirmelon].
- skilfull session based testing is replaced with manual repeating of instructions listed in test cases documents.
- all automation checks are in UI level, and represent end-to-end checks.
This points to important project issues:
- lack of skilfull testing
- knowing test automation framework, usually selenium based, is sexier that skilfull testing
What can you do? Start learning and practicing resources listed in point 1. This will help your project to use testing pyramid and help you to fight your desire for ice cream!