Continuous testing shortens feedback loops through automated testing that occurs throughout the development lifecycle—hence "continuous." Testing and QA become the responsibility of everyone working on the software, not just testers. Let's look at some proven practices from organizations that have used continuous testing effectively to realize tangible benefits.
Most organizations understand that test automation is essential for modern application delivery processes. They’re just not sure how to make it a reality in an enterprise environment without exorbitant overhead and massive disruption. Enterprise organizations typically achieve small victories, but the process ultimately decays due to challenges in five main areas. Understanding these challenges will help us overcome them.
“AIOps” stands for “artificial intelligence in IT operations,” or using machine learning and data science to solve IT problems. AI can help with many IT functions, including detecting and remediating outages, monitoring availability and performance, and IT service management. Like with DevOps, a tester plays an important part with AIOps—they just have to determine what that is.
DevOps does speed up your processes and make them more efficient, but companies must focus on quality as well as speed. QA should not live outside the DevOps environment; it should be a fundamental part. If your DevOps ambitions have started with only the development and operations teams, it’s not too late to loop in testing. You must integrate QA into the lifecycle in order to truly achieve DevOps benefits.
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.
Melissa Benua, director of engineering at mParticle, chats with TechWell community manager Owen Gotimer about the importance of whole team quality, how to get started using the test pyramid, and how developers can start writing testable code.
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.
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.