What is SmartFix?

With all the data collected during both test creation and every test execution, the system understands what to do at every step within the test flow. As changes are made to the application under test, the system does not always determine the correct interaction with the site. However, SmartFix can help you train the system to learn your test's intention, even if the ML gets it wrong. SmartFix will offer several typical types of suggestions to help you easily maintain your tests as your site changes..

Types of SmartFix Suggestion Scenarios

• Text Verification Suggestions offer updates on verification steps when a assertion fails
• Password Warning indicate that a password may be incorrect, there is nothing to update with the test in this scenario, but rather assistance in diagnosing a potential issue

Text Verification Suggestions

1. Open the Slider View
2. Scroll to the Failed action that includes the SmartFix tag
   
   
   
3. Hover on the SmartFix tag and proceed to Review the SmartFix suggestion(s)
   • The first suggestion, Text suffix verification, will update the action operator to Contains instead of Equals the Expected Value: 't Us'
   • The second suggestion, Change text verification, will change the Expected Value from 'About Us' to 'Contact Us'
     
     
     
4. Click the Review button next to the SmartFix suggestion to fix the failed action, a confirmation modal will appear to update the text from the old to the new without requiring re-recording with Architect, just select the radio button next the update suggestion
   For example: Update the operator to Contains versus Equals.
   
   
   
5. Click the Save button to commit the suggestion update to the test, then re-run the test and test action will Pass
   

Password Warning

In certain instances, we can determine if the password entered on a site is incorrect based on the behavior of the test. Of course, this scenario cannot provide the correct password to fix the test; instead, it simply alerts the user that an incorrect password is the probable cause of the failure.

See the example below:

This warning allows the user to go back into the test case and make the appropriate edits to these credentials.