ewintr
/
go-kit
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

more moving of links

This commit is contained in:
Erik Winter 2020-12-29 11:39:24 +01:00
parent 5940ecc532
commit 9b64161576
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
test/doc/httpmock_tutorial.adoc
View File

@ -19,7 +19,7 @@ To demonstrate this, let's look at a simple generic client for the Foo Cloud Ser
* #writing-the-tests[Writing the tests]
* #checking-the-outbound-requests[Checking the outbound requests]
_Note: If you're the type of reader that likes code better than words, skip this explanation and go directly to https://git.sr.ht/~ewintr/go-kit/test/[this repository] that contains a complete working example of everything discussed below._
_Note: If you're the type of reader that likes code better than words, skip this explanation and go directly to the `test/doc` folder in https://git.sr.ht/~ewintr/go-kit/[this repository] that contains a complete working example of everything discussed below._
== The Code We Want to Test
@ -223,7 +223,7 @@ Now we come to the interesting part: the recording of our requests. In the code
The nice thing about interfaces is that you can implement them exactly the way you want for the case at hand. This is especially useful in testing, because different situations ask for different checks. However, the go-kit test package has a straightforward implementation called `MockAssertion` and it turns out that that implementation is already enough for 90% of the cases. You milage may vary, of course.
It would be too much to discuss all details of `MockAssertion` here. If you want, you can inspect the code https://git.sr.ht/~ewintr/go-kit/tree/master/item/test/httpmock.go#L37[here]. For now, let's keep it at these observations:
It would be too much to discuss all details of `MockAssertion` here. If you want, you can inspect the code in `test/httpmock.go` in the https://git.sr.ht/~ewintr/go-kit[go-kit] repository. For now, let's keep it at these observations:
----
// recordedRequest represents recorded structured information about each request