[GH-ISSUE #5324] [feature]: Support setting number of iterations in Collection Runner UI #2035

New issue

Open

opened 2026-03-16 22:55:36 +03:00 by kerem · 2 comments

kerem commented

2026-03-16 22:55:36 +03:00

Owner

Originally created by @rafi-hibob on GitHub (Aug 12, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5324

Is there an existing issue for this?

I have searched the existing issues

Summary

Add a feature to the Hoppscotch Collection Runner UI to specify the number of iterations for a run, similar to the existing functionality available in the CLI.

Why should this be worked on?

The CLI already supports specifying the number of iterations when running a collection, which is great for automation and scripting. However, users who rely on the UI lack an intuitive way to repeat a collection run multiple times without manually re-triggering it.

Adding this to the UI would significantly improve usability and bring feature parity with the CLI. It would make the tool more friendly for less technical users and enable common workflows such as load testing, mass resource creation, and regression or flakiness testing through the UI.

Originally created by @rafi-hibob on GitHub (Aug 12, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5324 ### Is there an existing issue for this? - [x] I have searched the existing issues ### Summary Add a feature to the Hoppscotch Collection Runner UI to specify the number of iterations for a run, similar to the [existing functionality available in the CLI](https://docs.hoppscotch.io/documentation/clients/cli/overview#running-collections-present-on-the-api-client:~:text=no_of_iterations%3A%20Indicates%20the%20number%20of%20iterations%20to%20run%20the%20collection.%20Each%20iteration%20will%20run%20the%20entire%20collection%20once%2C%20replacing%20any%20iteration%2Dspecific%20data%20defined%20by%20the%20%2D%2Diteration%2Ddata%20flag%20(if%20provided).). ### Why should this be worked on? The CLI already supports specifying the number of iterations when running a collection, which is great for automation and scripting. However, users who rely on the UI lack an intuitive way to repeat a collection run multiple times without manually re-triggering it. Adding this to the UI would significantly improve usability and bring feature parity with the CLI. It would make the tool more friendly for less technical users and enable common workflows such as load testing, mass resource creation, and regression or flakiness testing through the UI.

kerem added the

feature

label

2026-03-16 22:55:36 +03:00

kerem commented

2026-03-16 22:55:47 +03:00

Author

Owner

@rafi-hibob commented on GitHub (Aug 26, 2025):

Hi @anwarulislam @jamesgeorge007 👋

I saw that you worked on adding the Collection Runner feature in #3600 — super helpful!

Just wanted to flag this feature request to support setting the number of iterations in the UI, similar to what’s possible in the CLI.

Would love to hear your thoughts on whether this might be considered!

Thanks again for all your work on Hoppscotch 🙌

@rafi-hibob commented on GitHub (Aug 26, 2025): Hi @anwarulislam @jamesgeorge007 👋 I saw that you worked on adding the Collection Runner feature in #3600 — super helpful! Just wanted to flag this feature request to support setting the number of iterations in the UI, similar to what’s possible in the CLI. Would love to hear your thoughts on whether this might be considered! Thanks again for all your work on Hoppscotch 🙌

kerem commented

2026-03-16 22:55:52 +03:00

Author

Owner

@broccolism commented on GitHub (Feb 10, 2026):

+1 My team also needs this feature to run tests multiple times conveniently

@broccolism commented on GitHub (Feb 10, 2026): +1 My team also needs this feature to run tests multiple times conveniently