Test Automation Teleportation? Do you skip user steps to speed up test runs?

Do you teleport in your test automation?
When automation testing, do you follow the same steps as a user, or do you jump to the desired state?
DoesQA: does.qa
#automationtesting #softwaretesting #testing #qa #codeless #nocode

[@MrDanDJRose]

I think another reason many test suites 'teleport' you to where you need to be is to simplify scripting. In a code heavy environment this can end up with some long test scripts. On the DoesQA platform your branching tests take care of this by allowing the same start to drive multiple tests, avoiding repetition, or custom node groups could be used to replicate steps across different tests.
The only downside I could potentially see is (taking login as the example) if the login page was unavailable for some reason, all tests that use it would fail. But then if something as fundamental as that is down, we should be setting alarms off, fixing, and then retesting. If it only adds a small amount extra to a test to include these steps then I don't see why you would want to teleport.

[@does_qa]

I do quite like it when 20+ tests fail, then pass again after a fix 😀