QASource’s Advanced Technology Group Monthly Update: July 2015

Good question! But unfortunately, choosing the perfect test automation tool has little to do with playing favorites and everything to do with requirements and the various parameters you’ve set for your project. In terms of language, the closest we’ll get to “favorite” is “most widely applicable” or “commonly used”.

Without high-quality defect tracking tools, monitoring software bugs is impossible. No engineer can track each and every defect in his or her head, nor with a single spreadsheet. Bug tracking allows teams to focus on priority issues that directly affect the quality of the software, and communicate about them more effectively.

Every month our Advanced Technology group evaluates the latest tools in QA testing and passes on their findings to you. This month, we will take a look at Spoon, Jasmine, Twist and Testing Anywhere. We have also provided a list of the latest support updates. As always, we hope this will help increase your QA team’s efficiency and productivity, as well as help you get the most out of test automation .

It’s standard practice for companies to monitor APIs during production to ensure that the live API endpoints are up, functioning quickly and returning expected information to the user. That way, testing teams know whenever something breaks down and can fix any issue before users notice any discrepancy.

But what if consumers find issues related to the API issue before you do? And what if the problem is more serious than slowness?

The digital age has made software integration a crucial part of any business’s success. Companies that continue to invest in big data, cybersecurity, and cloud technology — among other digital solutions — grow over 50% faster than their competition. To retain your edge, you must build and constantly maintain your digital infrastructure.

Nothing is more frustrating than funding a test automation project that results in endless time and resources to maintain , or worse, funding one that requires re-building after six months. Often a test automation strategy fails because the objectives were not identified early on or the scripting strategy excluded considerations for long-term maintenance.