mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #3983] [feature]: Ability to run a collection of requests sequentially #1399
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#1399
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mwkcoding on GitHub (Apr 18, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3983
Is there an existing issue for this?
Summary
I would like to be able to make some kind of "scenario" that runs a set of requests, waits for first one to finish and only continue if the previous was successful (aka returns status 200). Maybe the default assertion is that the request returns with status 200 but if you define tests for the requests, those have to pass before proceeding.
Why should this be worked on?
My use-case is a form for running a warmup of APIs which requires calling a bunch of endpoints which is tedious to do manually.
@liyasthomas commented on GitHub (Apr 18, 2024):
We've been working on this feature, there's an active pull request #3600 to introduce the Collection Runner feature.
@RJRReid commented on GitHub (Apr 26, 2024):
I work for a large company that very soon will need to replace POSTMAN.
However, whatever it gets replaced with will have to have a Runner that uses a CSV as input.
If you can get this working, I might convince my company to purchase several hundred of the licenses for the paid version.
@liyasthomas commented on GitHub (Apr 26, 2024):
We’re hoping to release this feature in the next few weeks.
@RJRReid, I’d love to hear your thoughts on this:
Will you be comfortable with running the Collections from the GUI or a terminal/CI/CD pipeline?
Does JSON format works for you instead of CSV?
How are these files created and maintained in your organisation?
@RJRReid commented on GitHub (Apr 26, 2024):
All of out development environment are isolated from the Internet, so
only programs that have been loaded to the machine images will run.
All of out testing scenarios are in CSV format.
All of the test data is created on the development machines and stays on
the development machines (no connection to the "outside world").
Being completely isolated is the reason we can no longer use Postman as
they are phasing this ability out of their newer releases.
------ Original Message ------
From "Liyas Thomas" @.>
To "hoppscotch/hoppscotch" @.>
Cc "RJRReid" @.>; "Mention" @.>
Date 4/25/2024 10:31:50 PM
Subject Re: [hoppscotch/hoppscotch] [feature]: Ability to run a
collection of requests sequentially (Issue #3983)
@mikeacjones commented on GitHub (Apr 27, 2024):
Question: will this support similar functionality as Postman where you can have a request basically repeat itself? The use case I’m thinking is request one loads an array as a variables, request two pops an element off that array and makes a request and then repeats itself if there are still elements in the array.
Something similar to postman.setNextRequest?
@RJRReid commented on GitHub (Apr 28, 2024):
No. We do not need that feature.
We just need a Runner that fills in variables in the Pre-script, body
and test from an item in a CSV (We use EXCEL to work with the CSV).
Each row in the Excel CSV, not including the header, is consumed by the
collection one at a time until the item count is reached or the CSV rows
are depleted.
------ Original Message ------
From "Michael Jones" @.>
To "hoppscotch/hoppscotch" @.>
Cc "RJRReid" @.>; "Mention" @.>
Date 4/27/2024 6:58:42 AM
Subject Re: [hoppscotch/hoppscotch] [feature]: Ability to run a
collection of requests sequentially (Issue #3983)
@davidsebastien commented on GitHub (Mar 18, 2025):
Hello everyone,
May I ask what the current status of this feature is?
I see that the status is still 'Open', but about a year ago, it seemed like there was a lot of demand for this feature. My team would be heavily relying on this feature, which is why I decided to post this question.
Kind regards,
David
@liyasthomas commented on GitHub (Mar 18, 2025):
Collection Runner is available.