mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #465] [suggestion] - Tests tab #175
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#175
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 @Olyno on GitHub (Jan 1, 2020).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/465
Originally assigned to: @nickpalenchar on GitHub.
Is your feature request related to a problem? Please describe.
I really love postwoman, and I'm using it to test my rest api. Problem: I currently can't make a serie of tests. I'm searching a way to automate requests and check if everything is fine or not, like if x request returns me correctly y response.
Of course maybe it's already implemented, and in this case I didn't find the way to do that, sorry about that.
Describe the solution you'd like
Add a new tab named "tests" where we could add a requests we saved in our collections, and a "predictable" reponse. Postwoman could test requests automatically using 1 single button.
Describe alternatives you've considered
Using the documentation tab, and implement it directly inside this one.
Additional context
/
@liyasthomas commented on GitHub (Jan 1, 2020):
Will surely look into the possibilities of implementing them.
@liyasthomas commented on GitHub (Jan 1, 2020):
Do you really want to mention the exact predicted response or is it okay with the response code/state like 200 or 403 (success or forbidden)..?
@Olyno commented on GitHub (Jan 2, 2020):
I think status could be enough
@allquixotic commented on GitHub (Jan 3, 2020):
I use the "tests" feature of Postman to store variables into the collection, then refer to them in later API requests. This is very useful for things like unique tokens, generated access keys, etc. that are used from one request to the next. Without this feature in Postwoman, I have to manually copy values out of the response from earlier requests and paste it into the next.
Really all that's needed is basically a "post-request hook" to execute arbitrary JS with access to the innards of the engine enough to set variables that will be referenced in a future request. I don't actually need the "unit testing" (assertions, etc.) support of Postman.
@liyasthomas commented on GitHub (Jan 4, 2020):
#218 @nickpalenchar
@nickpalenchar commented on GitHub (Jan 6, 2020):
This sounds doable, and can we can definitely leverage some work in pre-request hooks from #218 to extend into this.
@liyasthomas commented on GitHub (Jan 17, 2020):
@nickpalenchar ping!
@nickpalenchar commented on GitHub (Jan 17, 2020):
@liyasthomas hi still working but it's been smooth development! Probably can get it merged this weekend.
I only have some weekend time to work on open source these days so progress will look more sporadic than usual for now. But you can check out work for this on
feature/post-request-tests, branch, which I'll keep updating.@liyasthomas commented on GitHub (Jan 23, 2020):
@nickpalenchar Just a friendly reminder: In the past few days, base branch has been updated with lot of core features. I advise you to keep the https://github.com/liyasthomas/postwoman/tree/feature/post-request-tests branch updated with the
masterbranch.And we could merge tests feature when the MVP is ready and iterate over it in the upcoming weeks.
@nickpalenchar commented on GitHub (Jan 24, 2020):
Ooh thanks for the update. I'll be back on this tomorrow but that’s a good point for my future week hiatuses. Looking to push it out tomorrow either way
On Thu, Jan 23, 2020, at 6:58 PM, Liyas Thomas wrote: