Create a deadlineExceededError for unit tests with timeout: true
php editor Xiaoxin is here to introduce you to a tip about unit testing: create a deadlineExceededError: true for unit testing with timeout. When performing unit testing, sometimes you may encounter a test execution timeout. In this case, we can solve this problem by setting deadlineExceededError to true. This technique can help us better control and manage the execution time of the test and ensure the accuracy and reliability of the test. Next, we will introduce in detail how to use this technique to improve the efficiency and reliability of unit testing.
Question content
I'm trying to create a unit test in my project where I simulate an http client and set the response that the client must return. I need this behavior because my code needs to behave accordingly in case the http client fails with a timeout: so I need to mock the http client to return a deadlineExceededError and unit test from it.
What I've tried so far is to simulate the client do function in a way that client.do returns:
getdofunc = func(*http.request) (*http.response, error) { return nil, &url.error{ op: "post", err: context.deadlineexceeded, } }
It works, but not completely, which means when I execute the code with this simulated behavior, the error type returned is:
error(*net/url.error) *{op: "post", url: "", err: error(context.deadlineexceedederror) {}}
This is correct again, but not completely. Why? Because if I run the code and a real timeout occurs, I get something more complete:
error(*net/url.Error) *{Op: "Post", URL: "http://localhost:4500/scan/", Err: error(*net/http.httpError) *{err: "context deadline exceeded (Client.Timeout exceeded while awaiting headers)", timeout: true}}
What interests me the most is timeout: true
. If I manage to tell my mock to return it, I can assert this, which I find more complete than just asserting that the error returned is of type deadlineexceedederror.
Solution
In order to avoid overly complex testing, I recommend you adopt this approach. First, start by defining your error:
type timeouterror struct { err string timeout bool } func (e *timeouterror) error() string { return e.err } func (e *timeouterror) timeout() bool { return e.timeout }
In this way, timeouterror
implements both the error()
and timeout
interfaces.
Then you have to define impersonation for the http client:
type mockclient struct{} func (m *mockclient) do(req *http.request) (*http.response, error) { return nil, &timeouterror{ err: "context deadline exceeded (client.timeout exceeded while awaiting headers)", timeout: true, } }
This just returns the error defined above and nil
as http.response. Finally, let's look at how to write a sample unit test:
func TestSlowServer(t *testing.T) { r := httptest.NewRequest(http.MethodGet, "http://example.com", nil) client := &mockClient{} _, err := client.Do(r) fmt.Println(err.Error()) }
If you debug this test and pause with the debugger on the err
variable, you will see the desired results.
This way you can achieve the functionality you want without any additional complexity. Let me know if it works for you!
The above is the detailed content of Create a deadlineExceededError for unit tests with timeout: true. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

The article explains how to use the pprof tool for analyzing Go performance, including enabling profiling, collecting data, and identifying common bottlenecks like CPU and memory issues.Character count: 159

The article discusses writing unit tests in Go, covering best practices, mocking techniques, and tools for efficient test management.

This article demonstrates creating mocks and stubs in Go for unit testing. It emphasizes using interfaces, provides examples of mock implementations, and discusses best practices like keeping mocks focused and using assertion libraries. The articl

This article explores Go's custom type constraints for generics. It details how interfaces define minimum type requirements for generic functions, improving type safety and code reusability. The article also discusses limitations and best practices

This article explores using tracing tools to analyze Go application execution flow. It discusses manual and automatic instrumentation techniques, comparing tools like Jaeger, Zipkin, and OpenTelemetry, and highlighting effective data visualization

The article discusses Go's reflect package, used for runtime manipulation of code, beneficial for serialization, generic programming, and more. It warns of performance costs like slower execution and higher memory use, advising judicious use and best

The article discusses using table-driven tests in Go, a method that uses a table of test cases to test functions with multiple inputs and outcomes. It highlights benefits like improved readability, reduced duplication, scalability, consistency, and a

The article discusses managing Go module dependencies via go.mod, covering specification, updates, and conflict resolution. It emphasizes best practices like semantic versioning and regular updates.
