One tool that has come a long way in simplifying testing efforts through automation technology is Selenium. Read more to learn the benefits of web automation testing and why Selenium can be the ultimate choice for a solution that can aid the web automation testing processes for organizations of different sizes and industries.
Adopting a machine learning-driven self-healing technique in test automation can prevent flaky tests, reduce test failures, and save time on code maintenance. Self-healing is one of the essential factors for successfully performing continuous testing in the DevOps model.
Testers come from a wider range of backgrounds, and have complex multifaceted roles. People who test are not “just testers…” At present, many testers do not feel well-supported by their tools. As my research uncovered stories of frustration, fear, and anger, I realized the illusory role of usability in tool adoption and the importance of understanding who is using those tools.
Test automation can reach a point at which it is no longer supporting organizational goals. Martin Ivison examines four key causes for this unhealthy state and finds out that carefully chosen metrics and a holistic, adaptive, and risk-driven approach go a long way to prevent and remedy this problem.
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.
Greg Paskal, evangelist in testing sciences and lead author for RealWorldTestAutomation.com, chats with TechWell community manager Owen Gotimer about testing as a craft, choosing the right test automation tools, and current testing trends around the world.
Chloe Chen, automation developer at Upland InGenius, chats with TechWell community manager Owen Gotimer about her journey into test automation and her team’s goal of transitioning from working on a single product to offering test automation as a service across their organization.
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.
Dan McFall, president and CEO at Mobile Labs, chats with TechWell community manager Owen Gotimer about trends in enterprise mobility, the role DevOps and the cloud play in mobile application testing, and the transition to working from home.
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.