responses

When it comes to web automation testing, the first automation testing framework that comes to mind undoubtedly has to be the Selenium framework. Selenium automation testing has picked up a significant pace since the creation of the framework way back in 2004.

This article is a part of our Content Hub. For more in-depth resources, check out our content hub on Selenium 4.

The art of debugging can be complex—it’s no secret that bugs can wreak havoc on an otherwise lovely bit of code. Luckily, there are several tools that can make debugging easier. Some debuggers allow you to set breakpoints so that your program stops at certain points, letting you peek and poke around and see what’s happening.

In my last blog, I investigated both the stateless and the stateful class of model-based testing. Both have some advantages and disadvantages. You can use them for different types of systems, depending on whether a stateful solution is required or a stateless one is enough. However, a better solution is to use an aggregate technique that is appropriate for each system. Currently, the only aggregate solution is action-state testing, introduced in the book Paradigm Shift in Software Testing. This method is implemented in Harmony.

Have you ever experienced a 404 error? From an end user’s perspective, a 404 error (or broken link) experience can be a complete turn-off. Apart from annoying end-user experience, broken links (or dead links) on a website can dampen the SEO (Search Engine Optimization) activity.