Trello gives teams a visual way to collaborate over tasks, projects, approval flows, or the next big idea. It is based on one of the most efficient methodologies ever conceived — Lean. Lean and kanban (lean’s visual project management system) was used by Toyota manufacturers to manage projects as early as the 1960s. Trello is totally free for as many cards, lists and comments as you like.
While programmers are waiting for feedback, they start the next thing, which leads to multitasking. Eventually, someone re-skins the user interface, and, unless there is some sort of business logic layer in the tool, all checks will fail and you will be left with no easy way to revise the system. In an attempt to just get done, teams revert to human exploration, the automation becomes even more out of date, and, eventually, it will be thrown away.
Watir is made to automate web application testing and this is done using Ruby libraries. Watir is also called as water by the people and is an open source testing tool. This tool can be used to tests any language-based web application. Watir works well with RSpec, Cucumber, and Test/Unit and is a business-driven development tool. It basically tests web page’s buttons, forms, links, and their responses. It can be used on a number of browsers as it is compatible with them.
While automation saves you a lot of time, it still takes time. You can't run all your tests all the time. It takes too long and would generate an unmanageable analysis and maintenance effort. In my group, we've taken both manual and automation testing to three levels: sanity, end-to-end, and full. In addition to our feature tests, on every code commit, we run a set of high level, cross-feature tests to make sure that a code change in one feature hasn't broken another one. Only then do we run a set of more extended tests specific to the feature for which the code was committed. Then, we run our suite of feature-level sanity tests on our continuous delivery environment every three hours to make sure all features are in good shape. We only do this on one browser though, because we've found that if a test fails, it doesn't usually depend on the browser. Finally, we run feature end-to-end testing on our nightly environment.