Do you use mocks in automated tests? What are the advantages and disadvantages of their use?

Mocks in automated tests are used to simulate the behavior of external dependencies such as databases, APIs, services, etc. This allows isolating the tested component and verifying its logic without external influences.

Advantages of using mocks:

• Accelerate test execution as they do not require real calls to external systems.
• Enable testing of edge cases and errors that are difficult to reproduce on real services.
• Ensure test stability by eliminating the instability of external services.

Disadvantages:

• Mocks may not reflect the real behavior of dependencies, leading to a false sense of confidence.
• Require maintenance and updates when dependency interfaces change.
• Excessive use of mocks can lead to tests that only check stubs rather than real integration.

Example in Go using mocks for an HTTP client:

// Client interface
 type HttpClient interface {
     Do(req *http.Request) (*http.Response, error)
 }

// Creating a mock in the test
 type MockClient struct {}

 func (m *MockClient) Do(req *http.Request) (*http.Response, error) {
     // Return a pre-prepared response
     return &http.Response{
         StatusCode: 200,
         Body: ioutil.NopCloser(strings.NewReader(`{"result":"ok"}`)),
     }, nil
 }

// Using MockClient instead of a real http.Client