# 30 Days of Automation in Testing Day 5 - Find, use and share your thoughts on a web UI testing tool **URL:** \ **Category:** 30 Days of Testing\ **Tags:** 30-days-of-testing, automation\ **Created:** [5 July 2018 11:26 UTC](https://club.ministryoftesting.com/t/30-days-of-automation-in-testing-day-5-find-use-and-share-your-thoughts-on-a-web-ui-testing-tool/16427 "2018-07-05T11:26:21Z")\ **Posts on this page:** 1\ **Showing post:** 18
**Author:** ![joaofarias](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/joaofarias/32/11709_2.png) [@joaofarias](https://club.ministryoftesting.com/u/joaofarias)\ **Post date:** [21 July 2018 20:38 UTC](https://club.ministryoftesting.com/t/30-days-of-automation-in-testing-day-5-find-use-and-share-your-thoughts-on-a-web-ui-testing-tool/16427/18 "2018-07-21T20:38:57Z")
Although the developers on my team complain about the framework, I love the Ember.js testing tools. The framework itself provides tools for creating unit test frontend code (with dependency injection and no UI rendering), component test (rendering only the (hopefully small) UI component), or acceptance test (running a user journey, mocking all data expected from services). Matching the purpose of tools that touch a UI testing to UI, and not other stuff (as @mwinteringham mentioned). Besides that, the Ember community is very passionated for testing, creating tools for [a11y testing](https://github.com/ember-a11y/ember-a11y-testing) and [visual testing](https://github.com/percy/ember-percy). I am procrastinating in writing a full blog post about it, but this presentation can give an idea:[EMBERCONF 2015 - TEST-DRIVEN DEVELOPMENT BY EXAMPLE](https://www.youtube.com/watch?v=2b1vcg_XSR8). (I will update this post when I have the blog posts 😃) --- _[View the full topic](https://club.ministryoftesting.com/t/30-days-of-automation-in-testing-day-5-find-use-and-share-your-thoughts-on-a-web-ui-testing-tool/16427)._