Improve Search In Runner

Kinson · June 8, 2020, 6:27pm

I don’t know where to leave suggestions but I have one.

We take advantage of creating branches for our code review process when dealing with postman. Because of this, we have quite a few collections that are forks of a main collection. When we want to run that collection for a particular branch, it is a bit of a pain trying to find the collection fork to run tests against.

Currently the search field in the runner searches based off of the name of the collection and its folders. Could we get it to search by the name of the branch as well?

This means we could quickly find the collection for a particular branch when want to run the tests for that collection.

Thanks!!

Kurmavatar · June 9, 2020, 7:50am

Hi @Kinson

Welcome to the community

Yes, currently only collections are searchable in Collection runner. Although not accurate but we do have a feature request on similar lines:

github.com/postmanlabs/postman-app-support

Cannot search subfolders in Collection Runner

opened 07:09PM - 05 Feb 20 UTC

allyn-psyonix

feature collection-runner product/runtime

**Describe the bug** In the Collection Runner, when choosing a folder to run, I… used to be able to search for the name of a subfolder one or two levels deep in a collection. Now I seem to only be able to search for top-level folders. This is very inconvenient and removes a lot of the value of the search feature. **To Reproduce** Steps to reproduce the behavior: 1. Go to Collection Runner 2. Enter a folder name that is not a top-level folder 3. No results **Expected behavior** The sub-folder should be displayed in the search results. **Screenshots** Not sure how to attach a file... **App information (please complete the following information):** - App Type: **Native App** - Postman Version: **7.17.0** - OS: **Windows 10**

Please add any additional comments on the thread that might help our engineering team to consider the same for the name of the branches as well. In any case, you are free to submit a new feature request for this on our GitHub tracker- thank you in advance for the inputs : )