You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes there are changes to the Go standard libraries that can break test expectations, e.g. different error text like in #205. Since the library supports older versions of Go, it would be nice to have the unit tests run on CI against each supported minor version of Go to account for these changes in standard library behavior. This would also gives developers assurances that they are writing test expectations correctly.
This also introduces a requirement to somehow communicate the version of Go being used in the environment to the unit test code, e.g. through a build tag, environment variable.
The text was updated successfully, but these errors were encountered:
Sometimes there are changes to the Go standard libraries that can break test expectations, e.g. different error text like in #205. Since the library supports older versions of Go, it would be nice to have the unit tests run on CI against each supported minor version of Go to account for these changes in standard library behavior. This would also gives developers assurances that they are writing test expectations correctly.
This also introduces a requirement to somehow communicate the version of Go being used in the environment to the unit test code, e.g. through a build tag, environment variable.
The text was updated successfully, but these errors were encountered: