Tools like Selenium, an outstanding tool for UI test automation, and Arquillian, an award-winning integration testing framework, offer a base for high-quality tests which are crucial for a web app development. However writing UI tests and covering server-side logic leaves many questions open:
* Does Selenium cover everything? Page transitions, simple JavaScript interaction and a portion of DOM. Is it really enough?
* Mocking requests for testing server-side code is pain. Is it necessary?
* Are you able to detect that your component’s visual representation changes?
* Does investigating these changes involve a disproportionate amount of effort?
* Isn’t manual test development too expensive?
Software Engineer at JBoss by Red Hat; RichFaces Core Developer; Enthusiast for JavaEE, Testing and HTML5; Leading Arquillian Warp and Graphene extensions. bio from Twitter
Sign in to add slides, notes or videos to this session