/ go Public
cmd/go: [modules + integration] go mod test, execute all the unit tests of a module #31324
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
This report is part of a series, filled at the request of @mdempsky, focused at making Go modules integrator-friendly.
Please do not close or mark it as duplicate before making sure you’ve read and understood the general context. A lot of work went into identifying problems points precisely.
Go needs an official
go mod testcommand that executes all the unit tests of a particular Go module, to make sure it is healthy.
module path, or
module version, or
filesystem pathof a specific
go.modfile at the root of an unpacked module tree, or
modfile inside a goproxy hierarchy
go testflags should apply
go getdownload from the internet
Go modules are wonderful and exciting, until you realise they only deal with the code download part. One stills need to dissect individual Go packages in the next stages of a CI/CD Go-related job.
The Go module concept should be extended to the rest of Go code processing phases.
The text was updated successfully, but these errors were encountered: