[GH-ISSUE #5469] [feature]: Enhance Collection Runner with selective requests and reusable runners #2098

New issue

Open

opened 2026-03-16 23:11:46 +03:00 by kerem · 0 comments

kerem commented

2026-03-16 23:11:46 +03:00

Owner

Originally created by @roopepaajanen on GitHub (Oct 9, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5469

Is there an existing issue for this?

I have searched the existing issues

Summary

Enhance the Collection Runner to allow users to select specific requests from a collection to run — instead of always executing the entire collection. Additionally, it would be great to mix and match requests from multiple collections in a single run.

Proposed Features

Selective request execution:
Allow users to select which endpoints within a collection they want to run. This could be a simple checkbox UI next to each request in the runner setup view. This is a feature already available and used in Postman.
Cross-collection execution:
Enable adding requests from different collections into a single runner instance, for example when testing workflows that span multiple APIs.
Saved runners:
Add the ability to save configured runners in a dedicated section (e.g., alongside Collections, Environments, History, Shared Requests, and Generated Code).

Saved runners could store selected requests, environment, and run configuration.

A distinct icon in the sidebar would make them easy to access and manage.

I’d be happy to take a look at implementing this enhancement.

Why should this be worked on?

Use Cases

Quickly rerun only a subset of requests after making small API changes.
Build end-to-end tests across multiple collections, but within the same workspace.
Maintain reusable “test suites” for regression or CI workflows.

Originally created by @roopepaajanen on GitHub (Oct 9, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5469 ### Is there an existing issue for this? - [x] I have searched the existing issues ### Summary Enhance the Collection Runner to allow users to select specific requests from a collection to run — instead of always executing the entire collection. Additionally, it would be great to mix and match requests from multiple collections in a single run. **Proposed Features** 1. **Selective request execution**: Allow users to select which endpoints within a collection they want to run. This could be a simple checkbox UI next to each request in the runner setup view. This is a feature already available and used in Postman. 2. **Cross-collection execution**: Enable adding requests from different collections into a single runner instance, for example when testing workflows that span multiple APIs. 3. **Saved runners**: Add the ability to save configured runners in a dedicated section (e.g., alongside Collections, Environments, History, Shared Requests, and Generated Code). Saved runners could store selected requests, environment, and run configuration. A distinct icon in the sidebar would make them easy to access and manage. I’d be happy to take a look at implementing this enhancement. ### Why should this be worked on? Use Cases - Quickly rerun only a subset of requests after making small API changes. - Build end-to-end tests across multiple collections, but within the same workspace. - Maintain reusable “test suites” for regression or CI workflows.