Switching SUTs During a Test
Often, a test needs to validate that a change made on a different system. For example, updating something via a phone-based application requires validating that in a desktop client application.
// Perform actions on SUT 1:
TypeText "firstname.lastname@example.org", return -- Performs actions on existing connection
Click "SubmitButton" -- This submits a form
connect IP.ADDRESS.TO.SUT -- The saved name of the SUT from the Connection List can also be used
# Perform actions on SUT2 -- These actions might check that the submitted form has been received
// Re-connect to SUT 1:
TypeText "email@example.com", return -- The saved name of the SUT from the Connection List can also be used.
Click "SubmitButton" -- Submit a second form
You can switch back and forth between SUTs as much as you need.