Test a local go module imported using the replace directive and use the vendor directory in the home folder

In this article, editor Youzi will introduce how to use the replacement command to import the go module locally and use the supplier directory in the main folder. Replacement instructions are a powerful feature in the Go language, which allows us to more flexibly introduce local modules during the development process and improve the maintainability and reusability of the code. Through the guidance of this article, I believe that everyone can easily master this technique and develop Go language more efficiently. Next, let’s take a look at the specific steps!

Question content

myexporter is my local module and I import it into the main module using replace. I want to run tests in myexporter using the vendor folder at the root of the main project.

My project directory structure is like this

bitbucket.com
|__agent
     |__exporter
     |     |__myexporter
     |            |__factory.go
     |               factory_test.go
     |               go.mod
     |__runner
     |     |__main.go
     |        main_test.go
     |__vendor
     |     |__bitbucket.com/agent/exporter/myexporter
     |                   |__factory.go
     |__go.mod

myexporter go.mod file

module bitbucket.com/agent/exporter/myexporter

agent go.mod file has

module bitbucket.com/agent

require (
    bitbucket.com/agent/exporter/myexporter
)

replace bitbucket.com/agent/exporter/myexporter => ./exporter/myexporter

my question is

1. If I run "go test -mod=vendor ./..." it will only test in the main_test run
2. If I use "go test -mod=vendor exporter/myexporter", I will get "package exporter/myexporter is not in goroot"
3. If I run "go test -mod=vendor bitbucket.com/agent/exporter/myexporter" there is no test file
4. If I switch to the exporter/myexporter directory and then run with "go test ./..." it works, but not "go test -mod=vendor ./..." because the vendor directory is located The root directory of the agent李>
5. If I run "go test -mod=vendor ./exporter/myexporter/" I get "Main module (bitbucket.com/agent) does not contain package bitbucket.com/agent/exporter/myexporter"

The build doesn't have access to the go package, it depends on the vendor folder, and the same goes for the tests. I don't want multiple copies of dependencies to exist in another vendor folder inside myexporter. Is there any way to run tests within myexporter using the agent/vendor folder?

Workaround

Is there any way to run tests within MyExporter using the agent/vendor folder?

No.

You must test where myexporter is. Once provided, only the actual code is provided.

The only possibility is to combine modules.

It really boils down to this: If you need to somehow test the two modules in parallel/consistently, they are not really two different modules with different lifecycles. If these were separate things with different lifecycles, you could test the first, make sure it works and supply it to the second. Then test the second one, including its use of the first, but don't run the first test since it's no longer needed.

The above is the detailed content of Test a local go module imported using the replace directive and use the vendor directory in the home folder. For more information, please follow other related articles on the PHP Chinese website!