ChatGPT解决这个技术问题 Extra ChatGPT

Golang testing: "no test files"

I'm creating a simple test within my package directory called reverseTest.go

package main

import "testing"

func TestReverse(t *testing.T) {
    cases := []struct {
        in, want string
    }{
        {"Hello, world", "dlrow ,olleH"},
        {"Hello, 世界", "界世 ,olleH"},
        {"", ""},
    }

    for _, c := range cases {
        got := Reverse(c.in)
        if got != c.want {
            t.Errorf("Reverse(%q) == %q, want %q", c.in, got, c.want)
        }
    }
}

whenever i try to run it the output is

exampleFolder[no test files] 

this is my go env

GOARCH="amd64"
GOBIN=""
GOCHAR="6"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/juan/go"
GORACE=""
GOROOT="/usr/lib/go"
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
TERM="dumb"
CC="gcc"
GOGCCFLAGS="-g -O2 -fPIC -m64 -pthread"
CXX="g++"
CGO_ENABLED="1"

Any help will be greatly appreciated. Thanks!!

for Go testing your Test file should have **_test.go example.go should have correspondingexample_test.go

M
Michael Neale

Files containing tests should be called name_test, with the _test suffix. They should be alongside the code that they are testing.

To run the tests recursively call go test -v ./...

From How to Write Go Code:

You write a test by creating a file with a name ending in _test.go that contains functions named TestXXX with signature func (t *testing.T). The test framework runs each such function; if the function calls a failure function such as t.Error or t.Fail, the test is considered to have failed.


In addition to this, your test methods should be in the same package as the tested code, not main as in your question.
my file did end in _test.go. fixing the issue for me required removing a re-definition of TestMain in the new test file that I added to the package. I also had to change directory into the package folder itself and run go test from there instead of running it from the root directory
@thwd Test methods don't need to be (and many times shouldn't be) in the same package as the tested code.
The file containing test can't be named only _test.go. It should be at least one character before underscore like a_test.go.
@Dan Esparza: +1, But I don't know how to separate them without getting th error.
b
blockloop

It's possible you don't have any test files in the root package and running go test -v does not test sub-packages, only the root package.

For example

.
├── Dockerfile
├── Makefile
├── README.md
├── auth/
│   ├── jwt.go
│   ├── jwt_test.go
├── main.go

As you see there are no test files in the root package, only the main.go file. You will get "no test files."

The solution is to test all packages within the current working directory, recursively

go test -v ./...

Or if you use govendor

govendor test +local

Or you can specify which package (directory) to test

go test -v ./packagename

Or test a package recursively

go test -v ./packagename/...

This helped. To run tests for non-main packages (in sub-directories): go test -v ./<package_name> runs the tests for that specific package.
Under Wndows 10, go test -v ./packagename worked for me.
P
PodTech.io

Your test function within your _test file must start with the prefix "Test"

GOOD:

func TestName (

BAD:

func NameTest (

This function will not be executed as a test and results with the reported error


To add to this it has to be Test followed by an capital letter or underscore etc. You can't have TestmyFunction(). This bit me.
Y
Yevhenii Shashkov

I faced same problem. In addition to previous answers i find an issue when impossible to run test if your package's folder name is testing.

Terminal demonstration of the issue below:

with testing folder name:

~/go/src/testing$ go test
?       testing [no test files]

without testing folder name:

~/go/src/testing_someothername$ go test
PASS
ok      testing_someothername   0.089s

In my case it was helpful


This is exactly what was the problem
S
Sumer

To run all the tests use below command

> go test ./...
//For verbose output use -v flag
> go test -v ./...

S
Sendhil Vel

I faced same problem. I fixing them by appending various packages

go test -v ./ ./2ndpackage ./3rdpackage ./4thpackages

this solved the issue.

Also I added "_" between Test keyword and function name Test_FuncName


关注公众号,不定期副业成功案例分享
Follow WeChat

Success story sharing

Want to stay one step ahead of the latest teleworks?

Subscribe Now