Best practices for test automation emphasize reliability, portability, reusability, readability, maintainability, and more. But how can your existing automated test suite adopt these qualities? Should you address these issues with your current tests, or create an entirely new set of tests? Here are some questions that will help you determine if your test automation maintenance program is operating as it should be.
Teams everywhere are looking to speed up testing without sacrificing quality, so once again, some of the top articles last year were about continuous integration, machine learning, and—of course—how to best implement and use test automation. But readers were also interested in what they shouldn't be doing, with two high-ranking articles about test practices we should stop and a tool you may be misusing.
When people do not have good luck with automation, it is hardly ever because of the tool being used, but almost always because of the wrong automation strategy, wrong expectations, and wrong adoption of automation. Automation tools only answer the “how” of automation, while having an automation strategy gives answers to who, where, when, what, and why. Here's why it's so important to have a test automation strategy.
The way we think about what necessitates test coverage being “complete” influences how we test and the cases we create. After all, you wouldn't design tests for situations that don't occur to you—and you can't test what you can't see. It's time to take off the blinders. Here's how you can find where the bugs in your products are occurring, and then adjust your strategy to pinpoint them.
QA testers often take on more of a role than just testing software code. When the team needs help, QA should lend a hand in assisting with business analysis, customer communication, user experience, and user advocacy.
The internet of things (IoT) continues to proliferate as connected smart devices become critical for individuals and businesses. Even with test automation, performing comprehensive testing can be quite a challenge.
Because enterprise applications are highly interconnected, development in stages puts a strain on the implementation and execution of automated testing. Service virtualization can be introduced to validate work in progress while reducing the dependencies on components and third-party technologies still under development.
Chris Loder, automation architect at InGenius, talks about being a self-taught automation developer, why learning new skills is so important, and the synergy between manual testers, automation testers, and developers.
Michael Bolton, principal at DevelopSense, explains why there should not be the perceived division between manual and automated testing. He says they are both just tools in a tester's toolkit, and we should use the tools appropriate to the job at hand.
Jeff Payne, CEO and founder of Coveros Inc., discusses the need for testers to incorporate security testing into development from the beginning. He also details some of the open source and commercial tools available for finding and resolving security problems.
In this interview, Kenneth Merkel of CA Technologies explains how service virtualization has changed the way organizations handle their testing. He also details how improved coverage can lead to better quality, a happier QA team, and remove any blockers preventing you from release.
Companies like Apple, Tesla, Google, Amazon, and Facebook have been investing in AI to solve different technological problems in the areas of health care, autonomous cars, search engines, predictive modeling, and much more. Applying AI is real, it’s coming fast, and it’s going to affect every business, no matter how big or small. How are testers going to adapt to this change and embrace AI? Join Raj Subramanian to discover how AI is going to influence the way we do test design and automation. He'll cover the basics of AI, the key ways software testing can benefit from AI, and the challenges involved in implementing AI solutions. This session will help anyone get started with AI-based testing.
Does it feel like you spend half of every sprint fixing failing automated functional tests? Are programmers unwilling to work with automation code? Is test automation a maintenance nightmare? There is a better way. The Page Object Model (POM) is a powerful design pattern for building test...