You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey there, Hoppscotch team! 👋
Thanks for the amazing work put on so far!
I'm using the Hoppscotch CLI to run some tests in Github Actions (hopp test).
I've run hopp test quite a few times and the execution flow of each test seems to be absolutely random. Shouldn't the tests be running in the same order that they appear in the json file that is exported/in the GUI? This is a bit frustrating because some tests require the correct execution of others and having no control of the execution order is a bit underwhelming.
For example, I have three folders with several requests in each one:
The tests are executed in the order of Tags -> Timers -> Items.
Inside each folder, the tests are run sequentially.
Is this behaviour intentional?
Why should this be worked on?
I believe the simplest solution would be running the tests in the same order they are displayed in the GUI/exported to the json file.
I think this is important for people who want to use this CLI to make API definition tests.
The text was updated successfully, but these errors were encountered:
The issue is related to the collectionstack in hoppscotch-cli/src/utils/collections.ts.
A stack is a last-in first-out collection. So, the last pushed folder is used as next step to do.
I am not a ts developer. Would be nice if an ts expert could take a look on that.
Many thanks in advanced.
SanskritiHarmukh
added
testmu
The issue or PR is related to the Hoppscotch Code Quest Challenge under TestMu Conference.
and removed
fosshack
Relegated issue for FOSS Hack 2024 Partner Projects Programme
labels
Aug 16, 2024
Is there an existing issue for this?
Summary
Hey there, Hoppscotch team! 👋
Thanks for the amazing work put on so far!
I'm using the
Hoppscotch CLI
to run some tests in Github Actions (hopp test
).I've run
hopp test
quite a few times and the execution flow of each test seems to be absolutely random. Shouldn't the tests be running in the same order that they appear in thejson
file that is exported/in the GUI? This is a bit frustrating because some tests require the correct execution of others and having no control of the execution order is a bit underwhelming.For example, I have three folders with several requests in each one:
The tests are executed in the order of
Tags
->Timers
->Items
.Inside each folder, the tests are run sequentially.
Is this behaviour intentional?
Why should this be worked on?
I believe the simplest solution would be running the tests in the same order they are displayed in the GUI/exported to the
json
file.I think this is important for people who want to use this CLI to make API definition tests.
The text was updated successfully, but these errors were encountered: