The example is trivial; of course you'll create a login function that you can reuse. But when we get to the nitty-gritty of the application — creating new data, editing rows and profiles, searching, and so on — it is tempting to just get the code to work. As you add new features, you copy/paste to make a new automated example. Over a period of years, you end up with a lot of copied/pasted code.
Collaborate around tasks with your team, with projects, comments, and assignments. MeisterTask is visually similar to Trello, but supports a native integration to MindMeister for fast and easy mind mapping. Its integrations with Dropbox, GitHub, Zendesk, Box, Bitbucket, and Google Drive allow you to map tasks to one another and keep you from entering data in the same place twice.
The ROI on automation tests varies depending on several factors. Some tests are difficult to develop because of technology constraints. For example, testing frameworks may not support test cases that run across several browser sessions or across different devices. Other tests may not need to be run frequently. For example, it might be more cost-effective to occasionally and manually test a use case for a rarely used feature, rather than invest the time to develop and maintain an automated test that runs after each nightly build. Each organization will make its considerations according to its own priorities, but it's always important to consider the ROI you'll get by automating your tests.
Lori Fairbanks has years of experience writing and editing for both print and online publications. After graduating from Brigham Young University with a Bachelor of Arts in English, she worked as an editor for Creating Keepsakes magazine and then as a freelance writer and editor for a variety of companies, including marketing firms and a medical university. She now writes for Business.com and Business News Daily.