Detailed Query:
In our organization, we are leveraging Postman for API automation and have structured our test cases into multiple collections for better request reusability. Here’s how our structure looks:
- Collections: A, B, C, D, E
- Flows:
- Flow 1: A → D → E
- Flow 2: A → B → C
Since there are various combinations of flows, we’ve created a custom script that dynamically merges multiple collections into a single one at runtime and generates reports accordingly. This avoids replicating requests across flows and enhances reusability.
Challenges:
-
Existing Postman Functionality for Modular Flows:
Does Postman currently provide any in-built functionality to merge multiple collections into a single execution flow? If not, are there better practices to achieve this without relying on custom scripts? -
Collaboration and Collection Management:
Multiple users work on collections simultaneously, and new flows are created frequently. Managing this involves:- A Master Collection that contains all approved requests, where users fork and update for their use.
- However, any new flow requires merging existing collections into the master manually. This is labor-intensive and becomes challenging with daily updates.
Is there a way to automatically update the master collection when users create new flows or collections, ensuring seamless collaboration and consistency?
Points Considered:
- Folders as a Potential Solution: While folders group requests, they do not address merging collections or running specific combinations of flows effectively.
Looking forward to your recommendations and insights into handling these scenarios more efficiently using Postman or external tools.