There’s a paradox surrounding automated regression testing of the UI in Agile. On the one hand, everyone tells you how important it is. On the other, it doesn’t seem to work right in far too many Agile teams.
Test parameters are an age-old issue with well-known solutions. Use variables for the values that you know will change. For each variable, remember that the parameter name you’ve chosen must be meaningful. Follow these two rules, and you’re in a good shape. Seems simple so far, right?
The two founding pillars of software testing, verification and validation are the two terms that each and every tester knows. As far as the former term is concerned, we have great news — and an awesome feature that the Screenster users will love. Specifically, we’ve added a new verification mode for more flexibility in UI regression testing.
Okay, this one might actually be a lesser-known term, so what you’re probably asking yourself right now is: what is content verification? To begin with, no, I’m not talking about Google’s content verification program or SSL Web Page Content Verification Certificates. Things are fairly simpler in our case.
End of support for Selenium IDE in Firefox version 55 and newer (image credit: Freepik)
Mozilla’s decision to cease the support for Selenium IDE in Firefox 55 has drawn the attention of the testing community to a long-standing problem. We’ve all known for years that old-school record-playback tools underdeliver in the way of usefulness. Thanks to Mozilla, this has become more obvious.
How do you make Selenium WebDriver wait for page to load.
There’s an important difference between a human tester and an automated UI testing tool. This difference comes down to patience: humans are capable of it, and machines aren’t. When processing a test, an automation tool expects to obtain some result, like a button click. If the button is missing, the test fails, which is what we pretty much expect from it If the button takes too long to load, though, the test will also fail, which is certainly not the result we’re counting on.
Following Selenium locators best practices isn’t merely a good thing to do. Given how little it takes for UI testing to crumble into maintenance hell, having a good locator strategy is a must. And just like most things in UI testing, simple, robust locators aren’t that simple to build.
We’ve created Screenster as a product that embodies a specific vision of a web automation tool. We believe that testing automation should be about ROI, not the programming skills of your QA team. This vision defines our approach to the automated testing of web UIs, yet we realize that this approach is just one of many.
What’s so challenging about responsive design testing? Or should I say, what’s not challenging about it?
We all know that responsive web design testing can get tedious. A dozen of screen sizes, multiplied by the number of supported Webkits and Geckos. Oh, and how about IEs? Okay, I know I’m basically rubbing it in at this point…