Typically developers make repeatable steps manually like:
Create user
Login user
Open page {name}
Click button {name}
Go to another page
Do smth else
Fix code, repeate actions from the bottom
So it's annoying part of development when developers make repeatable action from time to time.
Some of the steps can be covered by automatic tests, but while developing make sense do a part of a test scenario and not to make the rest, because usually tests clean data after they done.
So it's not about running a separated functional or unit test, it's about running a separated manual test case.
Usually QA also do these steps every time when they are doing chaos testing.
I think it having such opportunity as running these step would be great.
I image it as a list with actions that you can run individually or select multiple to run it as a sequence.
For first time it can be made as a list with checkboxes and two buttons: run individually or run all checked actions.
The second question is even better that the visual part of this feature: how it should be done on backend:
Acceptance test (with separated steps on each case)
Typically developers make repeatable steps manually like:
So it's annoying part of development when developers make repeatable action from time to time. Some of the steps can be covered by automatic tests, but while developing make sense do a part of a test scenario and not to make the rest, because usually tests clean data after they done.
So it's not about running a separated functional or unit test, it's about running a separated manual test case. Usually QA also do these steps every time when they are doing chaos testing.
I think it having such opportunity as running these step would be great.
I image it as a list with actions that you can run individually or select multiple to run it as a sequence.
For first time it can be made as a list with checkboxes and two buttons: run individually or run all checked actions.
The second question is even better that the visual part of this feature: how it should be done on backend: