Table of Contents
Question content
Solution
Home Backend Development Golang Unit test http request retries using httptest

Unit test http request retries using httptest

Feb 10, 2024 pm 12:30 PM

使用 httptest 单元测试 http 请求重试

php editor Baicao introduces you to a unit testing tool called "httptest", which can help developers test when retrying http requests. This tool can not only simulate various http requests, but also automatically retry requests to ensure the stability and reliability of the code. Using the httptest tool, developers can easily unit test http requests, and can easily retry requests to deal with network instability or other abnormal situations. The use of this tool can greatly improve development efficiency and reduce the possibility of errors. It is a tool worth trying for every PHP developer.

Question content

I'm trying to write unit tests for a component called HttpRequest that wraps HTTP requests and handles response unmarshalling. Recently, I added a feature to this component that allows it to retry HTTP requests if it encounters a "connection refused" error on the first try.

To use the HttpRequest component, I call it once: user, err := HttpRequest[User](config). The config parameter contains all the necessary information to perform the request, such as URL, method, timeout, number of retries, and request body. It also unmarshals the response body into an instance of the specified type (User in this case)

The problem arises when I try to test a scenario where the initial request fails with a "Connection refused" error but the second attempt succeeds. The retry happens inside the component, so I only make one call to the component.

I found it challenging to create unit tests for this situation because in order for the request to fail with "Connection refused" there doesn't need to be a listener on the port being called. The problem is that when using httptest it always listens on the port when the instance is created, even when using httptest.NewUnstartedServer. Therefore, I will never encounter a "connection refused" error in my client code after creating the httptest instance.

However, I don't know which port it will listen on until I create the httptest instance. httptest always chooses a random port, and there is no way to programmatically specify a port. This means I can't make the HttpRequest call before creating the httptest instance.

Does anyone have any ideas on how to effectively unit test this scenario?

Solution

newunstartedserver Very simple:

func newunstartedserver(handler http.handler) *server {
    return &server{
        listener: newlocallistener(),
        config:   &http.server{handler: handler},
    }
}
Copy after login

If you choose a port that suits you, you can do this:

func mynewunstartedserver(port int, handler http.handler) *httptest.server {
    addr := fmt.sprintf("127.0.0.1:%d", port)
    l, err := net.listen("tcp", addr)
    if err != nil {
        addr = fmt.sprintf("[::1]::%d", port)
        if l, err = net.listen("tcp6", addr); err != nil {
            panic(fmt.sprintf("httptest: failed to listen on a port: %v", err))
        }
    }
    return &httptest.server{
        listener: l,
        config:   &http.server{handler: handler},
    }
}
Copy after login

The code to create the listener is modified from httptest.newlocallistener.

Another option is to implement the http.roundtripper interface and create a http.client using this roundtripper. The following is an example http/client_test.go copied from net/:

type recordingTransport struct {
    req *Request
}

func (t *recordingTransport) RoundTrip(req *Request) (resp *Response, err error) {
    t.req = req
    return nil, errors.New("dummy impl")
}

func TestGetRequestFormat(t *testing.T) {
    setParallel(t)
    defer afterTest(t)
    tr := &recordingTransport{}
    client := &Client{Transport: tr}
    url := "http://dummy.faketld/"
    client.Get(url) // Note: doesn't hit network
    if tr.req.Method != "GET" {
        t.Errorf("expected method %q; got %q", "GET", tr.req.Method)
    }
    if tr.req.URL.String() != url {
        t.Errorf("expected URL %q; got %q", url, tr.req.URL.String())
    }
    if tr.req.Header == nil {
        t.Errorf("expected non-nil request Header")
    }
}
Copy after login

The above is the detailed content of Unit test http request retries using httptest. For more information, please follow other related articles on the PHP Chinese website!

Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn

Hot AI Tools

Undresser.AI Undress

Undresser.AI Undress

AI-powered app for creating realistic nude photos

AI Clothes Remover

AI Clothes Remover

Online AI tool for removing clothes from photos.

Undress AI Tool

Undress AI Tool

Undress images for free

Clothoff.io

Clothoff.io

AI clothes remover

Video Face Swap

Video Face Swap

Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Tools

Notepad++7.3.1

Notepad++7.3.1

Easy-to-use and free code editor

SublimeText3 Chinese version

SublimeText3 Chinese version

Chinese version, very easy to use

Zend Studio 13.0.1

Zend Studio 13.0.1

Powerful PHP integrated development environment

Dreamweaver CS6

Dreamweaver CS6

Visual web development tools

SublimeText3 Mac version

SublimeText3 Mac version

God-level code editing software (SublimeText3)

What are the vulnerabilities of Debian OpenSSL What are the vulnerabilities of Debian OpenSSL Apr 02, 2025 am 07:30 AM

OpenSSL, as an open source library widely used in secure communications, provides encryption algorithms, keys and certificate management functions. However, there are some known security vulnerabilities in its historical version, some of which are extremely harmful. This article will focus on common vulnerabilities and response measures for OpenSSL in Debian systems. DebianOpenSSL known vulnerabilities: OpenSSL has experienced several serious vulnerabilities, such as: Heart Bleeding Vulnerability (CVE-2014-0160): This vulnerability affects OpenSSL 1.0.1 to 1.0.1f and 1.0.2 to 1.0.2 beta versions. An attacker can use this vulnerability to unauthorized read sensitive information on the server, including encryption keys, etc.

How do you use the pprof tool to analyze Go performance? How do you use the pprof tool to analyze Go performance? Mar 21, 2025 pm 06:37 PM

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

How do you write unit tests in Go? How do you write unit tests in Go? Mar 21, 2025 pm 06:34 PM

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

What is the problem with Queue thread in Go's crawler Colly? What is the problem with Queue thread in Go's crawler Colly? Apr 02, 2025 pm 02:09 PM

Queue threading problem in Go crawler Colly explores the problem of using the Colly crawler library in Go language, developers often encounter problems with threads and request queues. �...

What libraries are used for floating point number operations in Go? What libraries are used for floating point number operations in Go? Apr 02, 2025 pm 02:06 PM

The library used for floating-point number operation in Go language introduces how to ensure the accuracy is...

What is the go fmt command and why is it important? What is the go fmt command and why is it important? Mar 20, 2025 pm 04:21 PM

The article discusses the go fmt command in Go programming, which formats code to adhere to official style guidelines. It highlights the importance of go fmt for maintaining code consistency, readability, and reducing style debates. Best practices fo

PostgreSQL monitoring method under Debian PostgreSQL monitoring method under Debian Apr 02, 2025 am 07:27 AM

This article introduces a variety of methods and tools to monitor PostgreSQL databases under the Debian system, helping you to fully grasp database performance monitoring. 1. Use PostgreSQL to build-in monitoring view PostgreSQL itself provides multiple views for monitoring database activities: pg_stat_activity: displays database activities in real time, including connections, queries, transactions and other information. pg_stat_replication: Monitors replication status, especially suitable for stream replication clusters. pg_stat_database: Provides database statistics, such as database size, transaction commit/rollback times and other key indicators. 2. Use log analysis tool pgBadg

Transforming from front-end to back-end development, is it more promising to learn Java or Golang? Transforming from front-end to back-end development, is it more promising to learn Java or Golang? Apr 02, 2025 am 09:12 AM

Backend learning path: The exploration journey from front-end to back-end As a back-end beginner who transforms from front-end development, you already have the foundation of nodejs,...

See all articles