What is an example of sanity testing in WalkMe Builder?

Sanity testing in WalkMe Builder focuses on verifying that specific functionalities are working as intended after changes or updates have been made. The correct example involves ensuring that components within a Smart WalkThru perform correctly following any adjustments.

In this context, the case where the Smart WalkThru does not progress to the next step represents a scenario where the functionality is being checked. This means the primary concern is to confirm that the subsequent steps in the flow work correctly; if they do not, it indicates a potential issue that could stem from recent updates or errors in logic. By identifying whether the Smart WalkThru progresses as designed, testers can validate that the specific feature functions correctly before further testing or deployment.

The other examples relate to different testing scenarios that do not fit the definition of sanity testing. For instance, if the SWT crashes on incorrect data input, that issue signifies a more severe problem that would require in-depth testing beyond just functionality checks. The scenario where only one button triggers the next step suggests a design or configuration choice rather than a functionality verification, while the notion of all elements progressing smoothly points more towards overall workflow validation rather than isolating specific functionalities for quick checks.