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
{{ message }}
Repository navigation
Commit 30362f7
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: README.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@
3
3
Httpspec is a tool that expands upon HTTP Files by adding assertions to them, to be used for integration tests. HTTPSpec is also intended
4
4
to be a test suite runner for these extended HTTP Files.
5
5
6
-
Httpspec takes in an .http (or .httpspec) file, runs those requests in sequence with optional assertions that are checked along the way. Let's take the following specfile:
6
+
Httpspec takes in an .http (or .httpspec) file (or a directory containing those files, defaulting to CWD if none is provided), runs those requests in sequence with optional assertions that are checked along the way. Let's take the following specfile:
7
7
8
8
```
9
9
### Make a simple 200 request to HTTP Bin
@@ -41,6 +41,5 @@ Fail: 1
41
41
There are some gaps in this implementation at this point (these are things I plan to address):
42
42
43
43
1. There is not currently a way to pipe the response from a previous request into the next request. This is limiting as you often may need an ID from a previous request to make the next request.
44
-
2. Currently, HTTPSpec only takes in a single file. I intend to also support directory paths, but this hasn't been implemented yet.
45
-
3. Currently, everything runs serially. The plan is to run each file in isolation against a thread pool. This will happen eventually, so if you start writing tests today, write them with this in mind (dont try to get fancy with sequencing of test files).
46
-
4. Not all of the assertion types specified in the [specification](./HTTPSpec.md) are implemented yet.
44
+
2. Currently, everything runs serially. The plan is to run each file in isolation against a thread pool. This will happen eventually, so if you start writing tests today, write them with this in mind (dont try to get fancy with sequencing of test files).
45
+
3. Not all of the assertion types specified in the [specification](./HTTPSpec.md) are implemented yet.
0 commit comments