UI testing is an important part of testing. It’s easy to write simple UI tests, but not that easy to build a readable and maintainable test suite. What are the patterns to know when dealing with UI testing ? What are the common mistakes that you can easily avoid ?
Author:
Mathilde Lemee
After having worked for Software AG (Terracotta) in 2012 as R&D engineer on Ehcache and Bigmemory, Mathilde works now as freelancer in Paris. In 2010, she co-founded the JDuchess France Chapter, an organization to connect female Java developers and promote visibility of women in the Java eco-system. She blogs on http://www.java-freelance.fr about performance, general best practices and testing. She is a regular open-source committer and the creator of FluentLenium, a wrapper around Selenium that provides a fluent API, used in other open-source projects like Play!2. She is a regular speaker at Java conferences in Europe. She is also a mobile educative game editor (http://www.aetys.fr) on iPad/iPhone and Android.
Blog: http://www.java-freelance.fr