Selenium IDE3 is continually evolving and has become my new tool-of-choice for testing web apps from the user experience perspective. Some of the features of the older Selenium IDE, such as rollups, are not supported. This has required some time to learn how to recreate test scripts in the new IDE. Along the way I’ve learned some tricks which are not documented on the main Selenium IDE site.
Creating Selenium IDE3 Variables
Using variables in Selenium IDE3 is similar to the older releases. Use the Store command to save common text or other values to a variable. Target is the value to be stored and Value is the name of the variable. Yes, confusing — but that may change as the IDE continues to be refined over time.Read More
Did you know you can tell Selenium IDE to execute certain commands only if a specific element exists on the page? The if element exists trick makes your web app testing scripts far more interesting. Here is a quick example using Selenium IDE 3 — the “new” Selenium IDE.
Log out a standard user
In this use case a WordPress multisite standard user is logged in. We can only execute our commands if we are a super admin. When trying to open a URL that is only available to the super admin an error page shows up. Thankfully this page also comes with an easily identifiable body ID set to error-page.Read More
After a year-long hiatus, one of my favorite web app testing tools is back. It is nice to have Selenium IDE back as a viable option. Yes, it is similar to the old version. No, it is not perfect. It is a lot easier to use than nearly any other web app testing option available.Read More
Digging into Cypress.IO in a sprint to replace my almost-completely-useless stack of Selenium IDE tests for Store Locator Plus, I’ve run into some issues that seem to go beyond my lack of knowledge with the tool.
Yes, it is a great step in the right direction and it can be man-handled to do what I need. For now. But tools should not be forcing you to do things a specific way. That are supposed to make you more efficient, no re-train you or add extra steps.
Cypress.IO has shortcomings when it comes to doing real-world end-to-end testing of web apps. Order of tests is one of them.
Testing Store Locator Plus with lots of locations is a chore. Thankfully Cypress.IO data list processing makes this a lot easier.
It turns out that the old-school Selenium IDE scripts that we’ve been using to test Store Locator Plus for years will no longer work. We already knew Firefox versions beyond 54 broke things — but we kept an old install on hand so while we port 500+ test scripts to a new system. What finally broke the old-school Firefox bandaid was moving Store Locator Plus towards a reactive application using Vue.