Hi @kmeister, great question!
Short answer is that we are working towards a specific workflow, but not all of the pieces are in place to support it quite yet. For now, we would recommend creating a scenario collection file for each set of independent tests/feature, and then either merging them together when you are done, or simply triggering both collections when testing.
To merge them together, you can switch to code view and copy all of the scenarios in file A, then paste them in the code view of file B.
This is a temporary measure until we get the full versioning system in place.
Under the hood, projects in Stoplight are git repositories, and git serves as the foundation for the versioning workflow that we are working towards. We’re building a lightweight UI around git to help manage and merge multiple versions from within Stoplight (or, if you prefer, you can of course use whatever Git tooling you want to help manage the merging/branching etc).
In fact, you can already see indicators of the git underpinnings in our URLs (see master version below):
or in features like the change history (which pull data from the git commit history).
The UI we are building is not meant to be a full and complex git client, but rather a simpler set of features to help all personas (from product manager to technical writer to developer) collaborate around versions inside of Stoplight. However, because we’re on git, those with technical chops who want to drop down to lower level git operations can do so, while product managers etc use the lightweight Stoplight UI.
I hope this helps to answer your question, and provides some insight into where we’re headed! Let me know if anything isn’t clear or if you have other ideas or suggestions .