As an automation engineer, I want to be able to merge two or more tests into one painlessly, or split one test into multiple, in order to avoid double work if I discover a better way to handle a test I have already written.
For example, I had one test that covered downloading and testing many PDFs. When I discovered that didn't work as I wanted (and submitted ML-I-250), I split that one test into four, manually. If the issue in ML-I-250 is resolved, I will want to merge those four tests back into one.
Thanks for the detailed description of your use case. We recommend using reusable flows to split and merge tests. For example, you can use a flow to wrap around multiple steps within a test and then remove that flow from the test for the time being. When you are ready to bring those steps back, just insert the flow back into the test.