With 2020 upon us, software development firms seeking to increase their agility are focusing more and more on aligning their testing approach with agile principles. Let’s look at seven of the key agile testing trends that will impact organizations most this year.
Testers gather lots of metrics about defect count, test case execution classification, and test velocity—but this information doesn't necessarily answer questions around product quality or how much money test efforts have saved. Testers can better deliver business value by combining test automation with regression analysis, and using visual analytics tools to process the data and see what patterns emerge.
Continuous testing means all your tests are executing all the time, providing continuous feedback into the quality and health of your applications. In order to achieve continuous testing, you must first adopt the right test automation strategy. Understanding how to bring in all different types of test automation practices as efficiently as possible enables you to get started down the path of continuous testing.
Lots of test automation efforts in agile software development fail, or at least do not maximize their potential. This article looks at two main reasons test automation may not live up to the expectations that testers and other stakeholders in the agile development process have, then outlines six steps to avoid falling into these traps. Here's how to succeed with test automation in an agile environment.
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.
John McConda, principal consultant at Mozer Consulting, discusses his workshop designed to aid testers who work in a regulated environment to implement agile and automated testing. He talks about how those who work in businesses that are regulated by federal agencies, the Sarbanes-Oxley Act, and other compliance requirements can still work within those rigid specifications to introduce agile and automated processes.
In this interview, Dawn Haynes, CEO, testing coach, and consultant for PerfTestPlus, discusses the ever-evolving world of AI and machine learning and the impact on the future of testing. Dawn explains why tools and automation will not be able to replace people, so testers don’t need to worry about job security.
Greg Paskal, test automation lead at Ramsey Solutions, talks about data lakes and how to effectively use data visualization. Done well, data visualization should help practitioners, managers, and stakeholders easily consume, understand, and act on the information the visual displays.
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.
One of the lines in the Agile Manifesto is "Working software over comprehensive documentation." This doesn't mean that no documentation is produced, but instead that only documentation that brings value to the team and the customer should be created.
The rise, fall, and resurrection of Selenium IDE begs the question: Can codeless testing actually scale? Test automation folklore is full of horror stories of failed attempts to apply record-playback tools to perform UI-based functional testing. Putting these stories aside for a moment, let's take an objective look at record-playback tools and compare them with programming-based automation tools in order to evaluate their applicability to functional and visual test automation. Join Moshe Milman as he dives into a hands-on demo of the new Selenium IDE, reviews some of its new capabilities, and goes over the latest open source and commercial tools and trends in the codeless test automation space. Find answers to questions around codeless test automation and discover best practices that will help you to scale your automated tests.
We are often reminded by those experienced in writing test automation that code is code. The sentiment being conveyed is that test code should be written with the same care and rigor that production code is written with. However, many people who write test code may not have experience writing production code, so it’s not exactly clear what is meant. And even those who write production code find that there are unique design patterns and code smells that are specific to test code. Join Angie Jones as she presents a smelly test automation code base littered with several bad coding practices and walks through every one of the smells. She'll discuss why each is considered a violation and via live coding, she will demonstrate a cleaner approach. While all coding examples will be done in Java, the principles are relevant for all test automation frameworks.