Idea: Implement a disable individual test/test suite in the context menu for work in progress items #10213
Replies: 2 comments 1 reply
|
Hi @luchianalex, Thanks for explaining the use case. To make sure I understand correctly, could you please confirm what you mean by the test in this case? Are you referring to an Insomnia test/suite created under the Tests section, or are you referring to an individual request (scripts) within a collection that you are using as part of your testing? Thank you. |
|
Hi @poojithap11, I'm referring to the Tests section in Insomnia (the suite of test specs shown in the left-hand sidebar), not an individual request/script inside a regular API collection. Specifically, I want the ability to disable/skip an item at any of these levels, similar to ReadyAPI's "Disable TestStep" feature: A single test case — one specific test in the list, without deleting it or commenting out its code, so it's skipped when the suite runs but still visible in the sidebar for later re-enabling. Of course, this disable would also mean they would be commented out in the yaml, so to be skipped in the CI/CD. Switching projects landed me on Insomnia, after some years using ReadyAPI and I find I miss this option on a daily basis. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Lets say you start work on a new ticket.
While doing the work, the requirements change, and the dev needs to implement some changes, which renders your work so far useless.
Well, simply disabling the test, while editing the title with something along the lines of "in work", "stub", "in progress"etc. would mean that what you worked on so far is not wasted, and you could focus on other issues in the mean time.
Once the devs implement the changes, you could simply come back, enable the test and continue your work.
At the moment this is not possible, and we need to have work arounds with exporting, deleting, reimporting etc etc.
Thank you.
All reactions