mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 08:45:58 +03:00
[GH-ISSUE #5] Readable #2
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#2
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 @jgroom33 on GitHub (Aug 22, 2019).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5
A test flow should be readable in a repository. It should not require a UI to run the tests. It should be succinct and compact.
Reference ansible uri and strest for examples.
Handling loops, if conditions, and wait should also be possible without requiring the tester to write JavaScript.
@liyasthomas commented on GitHub (Aug 22, 2019):
I didn't get what you meant. Please elaborate what you tried to convey. I would like to hear what you've to share.
@jgroom33 commented on GitHub (Aug 22, 2019):
one of the challenges with Postman is that it requires a UI to run and update tests. The json output of a postman collection is unreadable because it is too complex. because of this complexity, when these json collections are committed to a git repository they are essentially binaries that require a UI.
A better solution is to use YAML that implements a DSL for executions. This eliminates the need for writing javascipt in
pre-request scriptsandtestsAnsible URI and stREST are examples of a yaml syntax with a DSL for executions.
@liyasthomas commented on GitHub (Aug 23, 2019):
Thanks for you quick clarification. I'll look into it.
@liyasthomas commented on GitHub (Oct 24, 2019):
#209 fixes this, hence closing.
@jgroom33 commented on GitHub (Nov 8, 2019):
This project has implemented all the things I was suggesting:
Yaml, cache, var storage, test assertion
https://testmace.com/