Description
With the goal of working towards browser events support GA, we have to start to align on UX flow of operations.
Currently both http requests and browser events live in the page under tabs with http requests visible. This makes browser events hard to find or even know they are there.
From this page the user is able to create either a Generator for protocol tests, or export a script (soon browser editor page) for a browser script. We should improve the UX here to make it clear of what has been recorded and what are the next possible steps.
Considerations
Acceptance criteria
Designs are provided for an improved UX in the Recorder view of the application where browser events or actions are not as hidden.
Description
With the goal of working towards browser events support GA, we have to start to align on UX flow of operations.
Currently both http requests and browser events live in the page under
tabswith http requests visible. This makes browser events hard to find or even know they are there.From this page the user is able to create either a
Generatorfor protocol tests, or export a script (soon browser editor page) for a browser script. We should improve the UX here to make it clear of what has been recorded and what are the next possible steps.Considerations
Acceptance criteria
Designs are provided for an improved UX in the Recorder view of the application where browser events or actions are not as hidden.