We talked to the tester after a few days of leaving him alone with RPF. We figured this might reduce the number of false-positive test failures and make updating them much quicker.
If the next test steps appeared to be working as well, the tests would keep executing during test passes only log warnings, or if in debug mode, they would pause and allow for a quick update of the matching rule with point and click via the BITE UI. If the match isn’t exact, but within tolerances (say only its parent node or class attribute had changed), we would log a warning and keep executing the test case.
Rather than simply fail like the existing Selenium automation would do when a certain element isn’t found, and require some manual DOM inspection, updating the Java code and re-deploying, re-running, re-reviewing the test code what if the test script just kept running and updates to the code could be as simple as point and click? We would keep track of all the attributes in the element recorded, and when executing we would calculate the percent match between the recorded attributes and values and those found while running. Selenium rocks, but after an initial regression suite is created, many teams end up spending a lot of time simply maintaining their Selenium tests as the products constantly change.
Why chrome web store ? It is a website with lots of data-driven UX, authentication, file upload, and it was changing all the time and breaking existing Selenium scripts: a pretty hard web testing problem, only targeted the chrome browser, and most importantly they were sitting 20 feet from us.īefore sharing with the chrome web store test developer Wensi Liu, we invested a bit of time in doing something we thought was clever: fuzzy matching and inline updating of the test scripts. Po, the developer of RPF, worked with the chrome web store team to see how an early version would work for them. Po Hu had an early version working, and decided to test this out on a real world product. Like most test tools, especially code generating ones, it works most of the time but its not perfect. The idea is to just let users use the application in the browser, record their actions, and save them as a javascript to play back as a regression test or repro later. Here is some anecdotal data and some background on how we started measuring the quality of RPF. We were originally skeptical ourselves, but figured somebody should try.
Learn more about events in Scriptcase grids, download now free version of our tool and discover this and other advantages in its use.At GTAC, folks asked how well the Record/Playback (RPF) works in the Browser Integrated Test Environment ( BITE ). Methods that can be used will be indicated with the green indicator.
Scriptcase grid applications have a feature that can help a lot in time to make them more personalized.