Issue: Test(s) not associated (not found/executed)

[yapith]

Did you check docs and existing issues?

• I have read the documentation.
• I have searched the existing configuration related discussions.
• I have updated to the latest version of Neotest.
• I have updated to the latest version of neotest-golang.
• I have checked the Neotest log for errors (see README for instructions on enabling it).

Neovim version (nvim -v)

0.10.0

Operating system/version

Ubuntu 22.04.4 LTS

Output from :checkhealth neotest-golang

neotest-golang: require("neotest-golang.health").check()

Requirements ~
- OK Binary 'go' found on PATH: /snap/bin/go
- OK Found go.mod file for /home/hussein/go/src/sandbox/dir/dir_test.go in /home/hussein/go/src/sandbox/go.mod
- OK Treesitter parser for go is installed
- OK neotest is available
- OK nvim-treesitter is available
- OK nio is available
- OK plenary is available

DAP (optional) ~
- OK Binary 'dlv' found on PATH: /home/hussein/.local/share/nvim/mason/bin/dlv
- OK dap is available
- OK dapui is available
- OK dap-go is available

Your Neotest and neotest-golang Lua setup

return {
	"nvim-neotest/neotest",
	event = "VeryLazy",
	dependencies = {
		"nvim-neotest/nvim-nio",
		"nvim-lua/plenary.nvim",
		"antoinemadec/FixCursorHold.nvim",
		"nvim-treesitter/nvim-treesitter",
		{
			"fredrikaverpil/neotest-golang",
			dependencies = {
				"leoluz/nvim-dap-go",
			},
			branch = "main",
		},
	},
--	UPDATE: opts removed per fredrikaverpil's comment, it wasn't used.
	end,
	config = function()
		require("neotest").setup({
			adapters = {
				require("neotest-golang"),
			},
			-- log_level = vim.log.levels.TRACE,
			-- log = {
			-- 	enabled = true,
			--	open = true,
			-- },
			-- vim.fn.setenv("NEOTEST_LOG_FILE", vim.fn.stdpath("data") .. "/neotest.log"),
                        require("neotest.logging"):set_level(vim.log.levels.INFO)
		})
	end,
}

Describe the problem

Hi, I'm testing out using the vanilla config described in the docs (with minor tweaks RE dependencies).

Running neotest.run.run() gives me this error:

Test(s) not associated (not found/executed): { "/home/hussein/go/src/sandbox/dir/dir_test.go::TestFooBar" }

I'm able to run "go test -v" from the project dir just fine.

The tests summary panel seems to be able to detect the tests visually with a question mark icon next to the tests.

Curious that this doesn't output any neotest.log file to stdpath("data") per the documentation:

require("neotest.logging"):set_level(vim.log.levels.INFO)

Also tried overriding NEOTEST_LOG_FILE, I'm still not getting neotest.log. Did I miss something here?

Hopefully I didn't miss anything silly. Love what you're doing. Thanks.

[fredrikaverpil]

Hey there,

Hm, so first off I can tell that your opts are not passed into your configuration function, which means they won't be used since you defined a config function. You have also mixed in some configuration in there which expects you to have a different neotest configuration (it looks like you may have copy-pasted from my personal configuration). Please remove the whole section opts = function(_, opts) ... end and let's focus on just getting the basics working without diverting from the defaults.

I've done that below, and also added in logging setup:

return {
	"nvim-neotest/neotest",
	event = "VeryLazy",
	dependencies = {
		"nvim-neotest/nvim-nio",
		"nvim-lua/plenary.nvim",
		"antoinemadec/FixCursorHold.nvim",
		"nvim-treesitter/nvim-treesitter",
		{
			"fredrikaverpil/neotest-golang",
			dependencies = {
				"leoluz/nvim-dap-go",
			},
			branch = "main",
		},
	},
	config = function()
        -- set up Neotest
		require("neotest").setup({
			adapters = {
				require("neotest-golang"),
			},
		})

        -- set up logging
        local log_level = vim.log.levels.DEBUG
        require("neotest.logging"):set_level(log_level)
        vim.notify("Logging for Neotest enabled", vim.log.levels.WARN)
        local filepath = require("neotest.logging"):get_filename()
        vim.notify("Neotest log file: " .. filepath, vim.log.levels.INFO)

	end,
}

This should show you both that logging is enabled and the path to the file. Do you still not see anything printed to the log file?

Do you have a separate lua configuration for Neotest?

A question mark next to the test means it hasn't run, or that it ran but there was no output from go test that could be correlated to the test. If this keeps occuring please have a look in the log file, and also please try to provide a minimal reproducible test example.

By the way, if you clone down this repo, you should be able to run the Go tests inside without issues. Can you do that?

EDIT: I updated the above snippet so to set up logging after loading neotest.

[fredrikaverpil]

Btw did you get logging to work?
I think I might have made a mistake in my code example above. I think you have to call Neotest setup function and then set the log level.

If you then run one single test and then attach the entire neotest log file here, it should reveal what is going on.

[fredrikaverpil]

I failed to mention earlier you can change test runner (this is so far documented only in PR draft as I'm still not 100% sure how I want this to be configured). This could actually be great to try out in order to figure out what is going on as well.

Make sure you have gotestsum installed:

go install gotest.tools/gotestsum@latest

Then add the following to your neotest-golang opts: runner = "gotestsum".

But first and foremost, a complete debug-level Neotest log of running a single test (or a all tests in a file, if that's when the issue is hit) would be the most insightful in figuring out the root cause of what you are experiencing.

[fredrikaverpil]

Hm. In your repro video clip, you are running all tests in the current file, right?

Do you also see this issue when running a single test or when running all tests in a folder?
Or does this only happen when running all the tests in a file?

I am really curious to take a look at what your test execution command looks like (from a log). I suspect that the package (which I get from go list is not proper here.
What I really don't understand is how this differs on your machine vs my machine.

[yapith]

Yes, I have logging working. It was my fault, I had messed up symlinks and need a reboot for some reason. Apologies for the human error.

go list looks fine to me:

RE Do you also see this issue when running a single test or when running all tests in a folder?
I see this in all run test mode, single, suite, all.

Let me try gotestsum and observe the logs. I'll keep you posted.

[yapith]

neotest.log

Attached is the logs from a single file test of neotest-golang/tests/go/positions_test.go with gotestsum. I think you're right go list -json ./... seems to show nothing based on the attached logs:

DEBUG | 2024-08-07T19:49:17Z-0700 | .../nvim/lazy/neotest-golang/lua/neotest-golang/logging.lua:52 | [neotest-golang] Running Go list: go list -json ./... in /home/hussein/go/src/neotest-golang/tests/go
INFO | 2024-08-07T19:49:17Z-0700 | .../nvim/lazy/neotest-golang/lua/neotest-golang/logging.lua:64 | [neotest-golang] Go list output:

How could this line possibly returns nothing:
local output =
vim.fn.system("cd " .. cwd .. " && " .. go_list_command_concat, " ")

which is odd because I can clearly see go list -json ./... output running manually:
{
"Dir": "/home/hussein/go/src/neotest-golang/tests/go",
"ImportPath": "github.com/fredrikaverpil/neotest-golang",
"Name": "main",
"Target": "/home/hussein/go/bin/neotest-golang",
"Root": "/home/hussein/go/src/neotest-golang/tests/go",
"Module": {
"Path": "github.com/fredrikaverpil/neotest-golang",
"Main": true,
"Dir": "/home/hussein/go/src/neotest-golang/tests/go",
"GoMod": "/home/hussein/go/src/neotest-golang/tests/go/go.mod",
"GoVersion": "1.22.2"
},
"Match": [
"./..."
],
"Stale": true,
"StaleReason": "build ID mismatch",
"GoFiles": [
"main.go"
],
"Imports": [
"fmt"
],
"Deps": [
"cmp",
"errors",
"fmt",
"internal/abi",
"internal/bytealg",
"internal/chacha8rand",
"internal/coverage/rtcov",
"internal/cpu",
"internal/fmtsort",
"internal/goarch",
"internal/godebugs",
"internal/goexperiment",
"internal/goos",
"internal/itoa",
"internal/oserror",
"internal/poll",
"internal/race",
"internal/reflectlite",
"internal/safefilepath",
"internal/syscall/execenv",
"internal/syscall/unix",
"internal/testlog",
"internal/unsafeheader",
"io",
"io/fs",
"math",
"math/bits",
"os",
"path",
"reflect",
"runtime",
"runtime/internal/atomic",
"runtime/internal/math",
"runtime/internal/sys",
"runtime/internal/syscall",
"slices",
"sort",
"strconv",
"sync",
"sync/atomic",
"syscall",
"time",
"unicode",
"unicode/utf8",
"unsafe"
],
"TestGoFiles": [
"positions_test.go",
"testname_test.go"
],
"TestImports": [
"testing"
]
}
{
"Dir": "/home/hussein/go/src/neotest-golang/tests/go/testify",
"ImportPath": "github.com/fredrikaverpil/neotest-golang/testify",
"Name": "testify",
"Root": "/home/hussein/go/src/neotest-golang/tests/go",
"Module": {
"Path": "github.com/fredrikaverpil/neotest-golang",
"Main": true,
"Dir": "/home/hussein/go/src/neotest-golang/tests/go",
"GoMod": "/home/hussein/go/src/neotest-golang/tests/go/go.mod",
"GoVersion": "1.22.2"
},
"Match": [
"./..."
],
"TestGoFiles": [
"othersuite_test.go",
"positions_test.go"
],
"TestImports": [
"github.com/stretchr/testify/assert",
"github.com/stretchr/testify/suite",
"testing"
]
}

[yapith]

Update: I figured it out the go bin installed via ubuntu snaps don't print to stdout when called from nvim, the exit code from jobstart is 0, but nothing outputed to stdout/stderr.

I had to download a go tarball and that fixed it. Thank you for your patience. Good call with the go list

[goshleg]

Hi there,

I'm encountering the same warning message when running the entire test suite with neotest-go. The message is:

Test(s) not associated (not found/executed)

This happens specifically when I use the run.run({ suite = true }) command. However, when I run individual test packages from the Neotest Summary using the run action, everything works as expected.

My project structure is as follows:
project_root/

├── cmd/
│   └── sitetrace/
│       └── main.go
├── config/
├── go.mod
├── go.sum
├── internal/  # Contains application packages
│   └── ... (various subdirectories)
├── tests/     # Contains integration tests
│   ├── api/
│   └── helper/

As you can see, I don't have any .go files directly in the project root directory. Through experimentation, I discovered that creating a dummy.go in the root allows the test suite command to run without warnings or errors.

Therefore, my question is: Is it mandatory to have a .go file at the root of the project for neotest-go to recognize and run the entire test suite with?

[goshleg]

Thanks for looking into this. You're correct; module sitetrace is declared at the top of my root go.mod file.

Regarding the db package, I realize my previous description was inaccurate. I don't have a db package in the traditional sense. Instead, I have a db/queries directory containing SQL files and a db/sqlc package generated by sqlc. Here's a full representation of the relevant directory structure:

└── sitetrace_main
    ├── cmd
    │   ├── docs
    │   │   ├── docs.go
    │   │   ├── swagger.json
    │   │   └── swagger.yaml
    │   └── sitetrace
    │       └── main.go
    ├── config
    │   └── local.yaml
    ├── coverage.out
    ├── db
    │   ├── queries
    │   │   ├── api_service_queries.sql
    │   │   ├── api_token_auth_queries.sql
    │   │   ├── dashboard_queries.sql
    │   │   ├── development.sql
    │   │   ├── integration_testing_queries.sql
    │   │   ├── protected_queries.sql
    │   │   └── user_auth_queries.sql
    │   └── sqlc
    │       ├── api_service_queries.sql.go
    │       ├── api_token_auth_queries.sql.go
    │       ├── dashboard_queries.sql.go
    │       ├── db.go
    │       ├── integration_testing_queries.sql.go
    │       ├── models.go
    │       ├── protected_queries.sql.go
    │       └── user_auth_queries.sql.go
    ├── go.mod
    ├── go.sum
    ├── http_requests
    │   ├── http-client.env.json
    │   └── pack1.http
    ├── internal
    │   ├── auth
    │   │   ├── api_token_auth.go
    │   │   ├── auth.go
    │   │   └── backend.go
    │   ├── config
    │   │   └── config.go
    │   ├── domain
    │   │   ├── appstate
    │   │   │   └── appstate.go
    │   │   ├── argon2
    │   │   │   ├── argon2.go
    │   │   │   └── argon2_test.go
    │   │   ├── object_key
    │   │   │   ├── object_key.go
    │   │   │   └── object_key_test.go
    │   │   ├── requests
    │   │   │   ├── service_api.go
    │   │   │   └── service_api_test.go
    │   │   ├── user_candidate
    │   │   │   └── user_candidate.go
    │   │   └── userpass
    │   │       └── userpass.go
    │   ├── html_template
    │   │   └── html_template.go
    │   ├── httputil
    │   │   └── httputil.go
    │   ├── logger
    │   │   └── logger.go
    │   ├── middleware
    │   │   ├── api-token-auth
    │   │   │   └── api-token-auth.go
    │   │   └── user-login
    │   │       └── user-login.go
    │   ├── rabbitmqpool
    │   │   └── pool.go
    │   ├── rabbit_mq_writer
    │   │   └── rabbit_mq_writer.go
    │   ├── routes
    │   │   ├── common
    │   │   │   └── common.go
    │   │   ├── open
    │   │   │   └── open.go
    │   │   ├── protected
    │   │   │   ├── admin.go
    │   │   │   └── starter.go
    │   │   ├── service-api
    │   │   │   └── service-api.go
    │   │   └── signup
    │   │       └── signup.go
    │   ├── service_providers
    │   │   ├── captcha_verifier
    │   │   │   └── captcha_verifier.go
    │   │   ├── client_tracking
    │   │   │   ├── client_tracking.go
    │   │   │   └── client_tracking_test.go
    │   │   ├── email_client
    │   │   │   ├── email_client.go
    │   │   │   ├── email_client_test.go
    │   │   │   ├── postmark.go
    │   │   │   ├── relay.go
    │   │   │   ├── smtpbz.go
    │   │   │   └── testing.go
    │   │   ├── geoip
    │   │   │   └── geoip.go
    │   │   └── s3_storage
    │   │       └── s3_storage.go
    │   ├── startup
    │   │   ├── dbmigration
    │   │   │   └── dbmigration.go
    │   │   └── startup.go
    │   ├── tasks
    │   │   ├── post_requests.go
    │   │   └── sessions.go
    │   └── types
    │       ├── httpmethod.go
    │       └── secret_string.go
    ├── main
    ├── scripts
    │   └── swag
    ├── setenv
    ├── sqlc.yaml
    ├── tests
    │   ├── api
    │   │   ├── api_test.go
    │   │   ├── helpers.go
    │   │   └── service_api_test.go
    │   └── helper
    │       ├── common.go
    │       └── cookiejar
    │           └── cookiejar.go
    └── VERSION

So, the go test command you showed:

go test -json -v -coverprofile=/home/george/dev/go/projects/sitetrace/services/sitetrace_main/coverage.out sitetrace/db/...

is trying to run tests in sitetrace/db/.... Since I don't have test files directly in the db directory, and my tests are likely located elsewhere, this command won't find any tests to run. The db/sqlc package contains generated code, not test files. I think it should run go test -json -v ./... instead.

I was inspecting neotest-goland/runspec/dir.lua and in func find_go_package_import_path found this: if there is .go file at the root, it goes into 'perfect match' branch, and if not, it goes into 'subpackage match' branch, which in the case of this repo are:

All paths:
{ "github.com/fredrikaverpil/neotest-golang/x", "github.com/fredrikaverpil/neotest-golang/testify", "github.com/fredrikaverpil/neotest-golang/subpackage/subpackage2/subpackag
e3", "github.com/fredrikaverpil/neotest-golang/subpackage/subpackage2" }
Shortest path:
github.com/fredrikaverpil/neotest-golang/x
{ "go", "test", "-json", "-v", "-coverprofile=/home/george/temp/neotest-golang/tests/go/coverage.out", "github.com/fredrikaverpil/neotest-golang/..." }

and in case of mine are:

All paths:
{ "sitetrace/tests/helper/cookiejar", "sitetrace/tests/helper", "sitetrace/tests/api", "sitetrace/internal/types", "sitetrace/internal/tasks", "sitetrace/internal/startup/dbm
igration", "sitetrace/internal/startup", "sitetrace/internal/service_providers/s3_storage", "sitetrace/internal/service_providers/geoip", "sitetrace/internal/service_provider
s/email_client", "sitetrace/internal/service_providers/client_tracking", "sitetrace/internal/service_providers/captcha_verifier", "sitetrace/internal/routes/signup", "sitetra
ce/internal/routes/service-api", "sitetrace/internal/routes/protected", "sitetrace/internal/routes/open", "sitetrace/internal/routes/common", "sitetrace/internal/rabbitmqpool
", "sitetrace/internal/rabbit_mq_writer", "sitetrace/internal/middleware/user-login", "sitetrace/internal/middleware/api-token-auth", "sitetrace/internal/logger", "sitetrace/
internal/httputil", "sitetrace/internal/html_template", "sitetrace/internal/domain/userpass", "sitetrace/internal/domain/user_candidate", "sitetrace/internal/domain/requests"
, "sitetrace/internal/domain/object_key", "sitetrace/internal/domain/argon2", "sitetrace/internal/domain/appstate", "sitetrace/internal/config", "sitetrace/internal/auth", "s
itetrace/db/sqlc", "sitetrace/cmd/sitetrace", "sitetrace/cmd/docs" }
Shortest path:
sitetrace/db/sqlc
{ "go", "test", "-json", "-v", "-coverprofile=/home/george/dev/go/projects/sitetrace/services/sitetrace_main/coverage.out", "sitetrace/db/..." }

Interestingly, in your case, it seems to be able to correctly identify the shortest path (github.com/fredrikaverpil/neotest-golang/x) for running tests.
In my project, where there's no .go file at the root, it picks sitetrace/db/sqlc as the shortest path, which isn't the intended package for tests. Perhaps the matching logic could be improved to handle projects with different layouts?

[fredrikaverpil]

Thanks for all the great details on this issue. I believe I have a fix ready: #241

[fredrikaverpil]

I'm also addressing the gin.Engine.Run bug in #244

[fredrikaverpil]

@goshleg I just cut a new release 🍰 which I hope will address all of your concerns. Don't hesitate to reach out again if the problem persists on your end or if you find something else!

[goshleg]

@fredrikaverpil This is fantastic! Thanks for taking the time to fix this. It's working great now!