


Using errors.As() when iterating the test structure, return the second parameter to errors.As should not be *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 }
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, },
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 { // ... } })
However, using errors.as
as described above returns
second argument to errors.As should not be *error
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()) }
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!

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

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

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

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.

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

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

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

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? When using GoLand for Go language development, many developers will encounter custom structure tags...

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

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