Hi Andy,

One approach is to wrap the entire multi-screen journey within a Wizard component. This way your testers will have “point-and-click”  access. By assigning a “Tester” role, you can expose the wizard only to your testers team while keeping it hidden from regular users.

There is an expression "you can't have the cake and eat it". If the form prevents users from advancing, it also prevents testers from advancing.

How to have both not simultaneously, but almost:

-If the sections of the form are blocks, you can have a different page that displays them. Like a style guide.

-Maybe do a toggle that allows anyone to move in the page without validations and switch it off when you want to treat validations. This can be achieved by either a site property or an extra role,like Mihai suggested.

Both are valid approaches to the issue. 

Hello Andy,

I understand your flow is complex but not clear why would you want the testers to skip initial flow. This kind of skip might makes sense for unit testing but quality testing must flow the end to end flow to ensure completeness of the testing scope.

Yet if you want to do it, these are the options I can think of off the top of my head.

1. With support from developers through some database script you can enter appropriate registration data related to test users accounts. This would allow testers to use those accounts and skip the initial set up.

2. In one of the applications we had similar need, to expedite the initial user accounts set up we had kind of automated the initial data entry part with the flexibility to allow the team to enter required data for test accounts. This supporting application was restricted to DEV and TEST environments only to ensure there are no loop holes in the actual registration flow.

Hope it helps!

Junaid