Table of Contents
Question content
Solution
Home Backend Development Golang Using errors.As() when iterating the test structure, return the second parameter to errors.As should not be *error

Using errors.As() when iterating the test structure, return the second parameter to errors.As should not be *error

Feb 15, 2024 pm 02:06 PM

在迭代测试结构时使用errors.As(),将第二个参数返回给errors.As 不应该是*error

php editor Strawberry found an error while iterating the test structure. When using errors.As(), the second parameter returned to errors.As should be a pointer to error, not an error. This error may cause the program to behave unexpectedly or incorrectly. Therefore, when using errors.As(), be sure to pay attention to the type of the parameter and ensure that a pointer to error is passed to avoid causing problems. This problem may arise when iterating over test structures, so pay special attention when using errors.As().

Question content

I'm currently writing some unit tests for a package where functions can return multiple types of errors. I define the structure as:

tests := []struct {
    name   string
    data   string
    url    string
    status int
}
Copy after login

And want to use errors.as() to find test.err in errors for my tests. The example structure I used in my tests is as follows:

{
    name:   "url not available",
    err:    &url.error{},
    data:   srvdata,
    url:    "a",
    status: http.statusok,
},
Copy after login

I want to use errors.as for a different structure type that implements the errors interface. So as you can see in the structure, I define err as an error. As can be seen, I use &url.error{} which should implement the error interface.

t.run(test.name, func(t *testing.t) {
    data, err := i.getid(url)
    if err != nil {
        require.notnil(t, test.err)
        assert.true(t, errors.as(err, &test.err))
    } else {
        // ...
    }
})
Copy after login

However, using errors.as as described above returns

second argument to errors.As should not be *error
Copy after login

Now from what I understand, errors.as() accepts any as the second argument, so I'm confused why *error can't be used.

I also tried changing the err field in the test structure to interface{}; however, doing so made all assertions pass regardless of whether the target was present in the error.

I can't find how to use errors.as() to achieve a different type of solution that implements the errors interface in a similar way to above, so now I rely on using contains() instead. Wondering if anyone can provide some insight.

Solution

The pointer to the error type does not satisfy the error interface, which is why the second parameter of as is of type any. In order to store the type you want directly in the .err field, the field must also be of type any.

However, since you have wrapped this pointer value in an interface, you will need to use a type assertion or reflection to get the value for inspection:

var testErr any = new(*url.Error)
_, err := http.Get("http://error.error/")

if errors.As(err, testErr) {
    fmt.Println(reflect.ValueOf(testErr).Elem())
}
Copy after login

The above is the detailed content of Using errors.As() when iterating the test structure, return the second parameter to errors.As should not be *error. 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.

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,...

How to specify the database associated with the model in Beego ORM? How to specify the database associated with the model in Beego ORM? Apr 02, 2025 pm 03:54 PM

Under the BeegoORM framework, how to specify the database associated with the model? Many Beego projects require multiple databases to be operated simultaneously. When using Beego...

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 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 should I do if the custom structure labels in GoLand are not displayed? What should I do if the custom structure labels in GoLand are not displayed? Apr 02, 2025 pm 05:09 PM

What should I do if the custom structure labels in GoLand are not displayed? When using GoLand for Go language development, many developers will encounter custom structure tags...

In Go, why does printing strings with Println and string() functions have different effects? In Go, why does printing strings with Println and string() functions have different effects? Apr 02, 2025 pm 02:03 PM

The difference between string printing in Go language: The difference in the effect of using Println and string() functions is in Go...

How to solve the user_id type conversion problem when using Redis Stream to implement message queues in Go language? How to solve the user_id type conversion problem when using Redis Stream to implement message queues in Go language? Apr 02, 2025 pm 04:54 PM

The problem of using RedisStream to implement message queues in Go language is using Go language and Redis...

See all articles