httptest | A Test Environment for HTTP Requests in R | Mock library

Solution to the first issue:
when using testify/suite, There are bunch of methods if created for the Suite struct, they will be automatically executed when running the test. That being said, These methods will pass through an interface filter. In the case of .SetupSuite, it has to have NO arguments and No return, in order to run.

Solution to the second issue: There is a way in go-sqlmock to match any kind of data by using sqlmock.AnyArg().

Fixed code:

It turned out to be a firewall issue, but a very pesky one.

• In our CA certificate there was a pki.ourdomain.org defined.
• The C# HTTP library called that URL at some point during the request (despite the ServerCertificateCustomValidationCallback returning true)
• Curl and python (requests) do not make this call so they dont timeout.
• Our firewall discarded the request to this pki domain, without any error or response.
• This caused the HTTP request to eventually timeout without any relevant error message.

When we found out this cause we added the pki.* url to the firewall rules. A more hacky solution without firewall changes is be to add pki.ourdomain.org to direct to localhost. This makes the pki request fail instantly, and the original request is executed normally.

I still dont fully understand why the C# library has this behaviour and other clients do not, but I hope this may help someone.

From the http package docs:

WriteHeader sends an HTTP response header with the provided status code.

and

Changing the header map after a call to WriteHeader (or Write) has no effect unless the modified headers are trailers.

So you are setting the "Content-Type" header after the header has already been sent out to the client. While mocking this likely works because the buffer where the headers are stored can be modified after the WriteHeader call. But when actually using a TCP connection you can't do this.

So simply move your w.WriteHeader(http.StatusOK) so it happens after the w.Header().Set(...)

I am assuming "integration test" means you will be running your entire application and then testing the running instance together with its dependencies (in your case a database & third party service). I assume you do not mean unit testing.

For integration tests you have a few options. In my case, usually I would integration test including whatever the third party client is connecting to (no mocking) because I want to test the integration of my service with the third party one. Or if that is not possible I might write a simple stub application with the same public interface as the third party service and run it on localhost (or somewhere) for my application to connect to during testing.

If you don't want to or can't do either of those and want to stub the external dependency inside your Go application, you can write an interface for the third party client and provide a stubbed implementation of the interface when running integration tests (using a flag on your application to tell it to run in "stubbed" mode or something of that nature).

Here's an example of what this might look like. Here's the source code file you posted - but using an interface for getting the third party data:

Probably the Db object is not initialized properly in the test. You'd better define a struct and inject DB as dependency and use a fake DB object in your test. For example,

Your GetData()'s return is a pointer. You run GetData() in main.go, when retun, it will close the resp.body. And if you read it again, it cause http: read on closed response body

So if you want read the body again, you should not return *http.Response, you should clone the resp.body to return

You could create a new server for each test case.

Or you can use channels, specifically a map of channels where the key is the test case's identifier, e.g.

You can do it like this:

This happens because when you do expected := mock_data.Users you are making a copy of the slice header, but not the underlying array, so changes to the array of the first slice will change the other. Please take a look at this article for more details.

If you want to make a copy of the slice you need to use the builtin copy function, like so: