#1 Shield34 wraps every Selenium command

Shield34 wraps every Selenium command, while adding the following layers to every command:

  • Waiting for all required conditions to be fulfilled prior to executing the command
  • Verifying the command was executed successfully
  • Handling errors/exceptions thrown
  • Automatic retry in case of error, exception or verification failure

Shield34 is not replacing Selenium, the Selenium command will eventually be executed, but Shield34 will make sure it is fulfilled 100% successfully

#2 Automatic deep reporting

An automatic report is generated for every test-run.
You don't have to manually report any actions, as all actions are being collected and reported automatically by Shield34 including test-steps, screenshots, APIs (XHRs), page HTML, Cookies, local storage, CPU, memory, storage and more.
This is achieved by the command wrappings mentioned above and by adding specific listeners

#3 Automatic failure's root cause analysis

On test failure, all test attributes are compared to the times the test was successful using AI algorithms to find anomalies in those attributes, aiming to pinpoint test's failure's root cause.
For example, Shield34 will pinpoint automatically any changes in APIs (XHRs) status code, duration, content or Cookies, any changes in element's locator in the page HTML, screen resolution, browser version, OS, CPU behavior, etc.

#4 Integrate Shield34 with your tests

In order to let all this magic happen, you need to use Shield34 commands instead of Selenium commands.

  • If you already have Selenium tests, please zip and upload them to Shield34, every Selenium command will be replaced with the corresponding one in Shield34 and let you download the updated tests few seconds later
  • If you are starting a new project, please download a top-notch Selenium project skeleton built with the best practices architecture to support your current and future needs, it also includes example tests so writing new tests would be much easier