How to Test Nested Go Modules from the Parent Directory?

Testing Nested Go Modules from Parent Directory

Go's testing framework, go test, is designed to work within a single Go module. When encountering a folder structure like the one described, where multiple Go modules reside in nested subdirectories, executing go test from the root directory will not succeed.

The error message encountered, "no packages to test," indicates that go test failed to find any testable packages within the current directory or its parent. This is because go test expects to work on a single module rooted in the current directory or its immediate parent.

Unfortunately, go test does not currently support testing nested modules directly. To run tests in multiple subdirectories, you'll need to either use a shell script or a Makefile to execute go test individually in each subdirectory.

For instance, a Makefile could be used to loop through the subdirectories, invoke go test, and aggregate the results:

all-tests:
    for dir in one two; do \
        make -C $$(cd $$dir && pwd) test; \
    done

Alternatively, a shell script could be written to perform the same task:

<code class="sh">#!/bin/sh
for dir in one two; do
    (
        cd "$dir"
        go test
    )
done</code>

In large projects with multiple modules, a dedicated test script or a Makefile is often used to automate the testing process, as seen in the example provided in the original answer. These scripts typically loop through a list of modules and execute go test for each directory.

The above is the detailed content of How to Test Nested Go Modules from the Parent Directory?. For more information, please follow other related articles on the PHP Chinese website!