"TAGS" As a user, I want to have a request in multiple folders, so I can run collections along certain dimensions.

[adrian0cg]

Current Behaviour

At the moment I can put a request in only one folder at a time. I.e.:

• User
  • My UserCreate-Request
  • My UserUpdate-Request
• Post
  • Get Newest Posts
  • Get Popular Posts
  • Submit Post

    Desired Behaviour

I would like to kind of "tag" the requests, i.e.:

• My UserCreate-Request: User, Authenticated
• My UserUpdate-Request: User, Authenticated
• Get Newest Posts: Post, Public
• Get Popular Posts: Post, Public
• Submit Post: Post, Authenticated

  Advantage

This way, I could run some of the requests selectively, sometimes testing everything "User", some "Posts" or via "Public"/"Authenticated".

[mblandfo]

Tags would be awesome. Here is my use case:

Server dev creates collections of requests by service.

Client dev doesn't care about what service requests come from, client dev wants them by feature.

Server dev tags them by feature, shares link to tag to client dev.

[TonyTrupp]

My QA team was hoping for this feature too, with a setup folder or setup collection, which would run before other individual folders or collections. Currently the run UI only allows selection of a single collection or folder. Sharing individual requests between multiple collections would be one way of handling this problem, or allowing multiple collections or folders to be run at the same time would be another solution.

[shamasis]

Just an update to this thread, now you can select granularity of what requests to run before running a request.