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.
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.
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.
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.
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.
Max Saperstone, director of test and automation at Coveros, chats with TechWell community manager Owen Gotimer about codeless automation, using ROI to drive test automation decisions, and why manual testing is here to stay. Continue the conversation with Max (@max) and Owen (@owen) on the TechWell Hub (hub.techwell.com)!
Hans Buwalda, CTO at LogiGear, discusses shifting the paradigm from not moving testing left or right along the software development lifecycle, but testing in a continuous circle to find unexpected problems. He talks about how testing is a mindset, not just a skill, and shares his insight into helping customers get further with Selenium.
Gil Sever, CEO at Applitools, discusses his journey in visual testing to making your product “visually perfect.” He talks about how companies are getting started in using automation, as well as how to get involved in leveraging and implementing AI in visual testing.
Paul Grizzaffi, Principal Automation Architect at Magenic, discusses nontraditional automation using fuzzy browser testing and the importance of the value stream analysis from idea to implementation. He also shares his insight on the most critical skills needed in automation.
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.