-
Notifications
You must be signed in to change notification settings - Fork 795
Issues: golang/vscode-go
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Golang debug test at cursor via hotkey ctrl-k ctrl-c not working
Go Companion
Issues relating to the Go Companion extension
go-test
issues related to go test support (test output, test explorer, ...)
HelpWanted
Issues that are not prioritized by the maintainers. Help is requested from community contributors.
NeedsFix
The path to resolution is known, but the work has not been done.
Polishing Go companion integration
Go Companion
Issues relating to the Go Companion extension
go-test
issues related to go test support (test output, test explorer, ...)
testOnSave: add option to only run the previously executed test
FeatureRequest
go-test
issues related to go test support (test output, test explorer, ...)
Test explorer about 25 times slower with many subtests
go-test
issues related to go test support (test output, test explorer, ...)
Add a button to remove tests from testing panel. Or do not add tests from standard libraries
go-test
issues related to go test support (test output, test explorer, ...)
Tests fails when saving a file (a symbolic link) with testOnSave enabled
go-test
issues related to go test support (test output, test explorer, ...)
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Add option to run tests in background by default
FeatureRequest
go-test
issues related to go test support (test output, test explorer, ...)
UI for running fuzz tests
FeatureRequest
go-test
issues related to go test support (test output, test explorer, ...)
#3152
opened Jan 12, 2024 by
qiulaidongfeng
Cannot run nested tests over more than 2 levels
Go Companion
Issues relating to the Go Companion extension
go-test
issues related to go test support (test output, test explorer, ...)
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Test Explorer keeps obsolete method names when renaming test suite methods
Go Companion
Issues relating to the Go Companion extension
go-test
issues related to go test support (test output, test explorer, ...)
Remove Legacy Commands that don't integrate with the Test Explorer
FeatureRequest
Go Companion
Issues relating to the Go Companion extension
go-test
issues related to go test support (test output, test explorer, ...)
Update test explorer when tests run from "go.testOnSave"
FeatureRequest
Go Companion
Issues relating to the Go Companion extension
go-test
issues related to go test support (test output, test explorer, ...)
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
Test explorer: gets stuck a lot and often needs restarting
Go Companion
Issues relating to the Go Companion extension
go-test
issues related to go test support (test output, test explorer, ...)
Allow running specific test case of a test table
FeatureRequest
Go Companion
Issues relating to the Go Companion extension
go-test
issues related to go test support (test output, test explorer, ...)
gopls
gopls related issues
Test Explorer: test logging in another package results in wrong file path in Test Output
Go Companion
Issues relating to the Go Companion extension
go-test
issues related to go test support (test output, test explorer, ...)
Bouncing "run test | debug Test" during typing
go-test
issues related to go test support (test output, test explorer, ...)
gopls
gopls related issues
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
upstream-tools
Issues that are caused by problems in the tools that the extension depends on.
test: limit the number of subtests displayed in the test explorer UI
Go Companion
Issues relating to the Go Companion extension
go-test
issues related to go test support (test output, test explorer, ...)
Test explorer and test codelens don't interact
Go Companion
Issues relating to the Go Companion extension
go-test
issues related to go test support (test output, test explorer, ...)
Go Test Explorer shows wrong state 'running' after it errors refusing to run multiple tests with debugger
Go Companion
Issues relating to the Go Companion extension
go-test
issues related to go test support (test output, test explorer, ...)
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Allow Test Explorer UI To Automatically Trigger Testing On Save
go-test
issues related to go test support (test output, test explorer, ...)
upstream-vscode
Issues that are by problems in VS Code itself.
Test explorer does not handle panics or timeouts well
go-test
issues related to go test support (test output, test explorer, ...)
testExplorer: skip test files in testdata directory
go-test
issues related to go test support (test output, test explorer, ...)
HelpWanted
Issues that are not prioritized by the maintainers. Help is requested from community contributors.
NeedsFix
The path to resolution is known, but the work has not been done.
Add a command to run test with custom value for issues related to go test support (test output, test explorer, ...)
HelpWanted
Issues that are not prioritized by the maintainers. Help is requested from community contributors.
-run
flag
FeatureRequest
go-test
Discussion: profiling a issues related to go test support (test output, test explorer, ...)
main
function with a test.
FeatureRequest
go-test
Allow "subtest at cursor" to work with table-driven test setup
FeatureRequest
Go Companion
Issues relating to the Go Companion extension
go-test
issues related to go test support (test output, test explorer, ...)
gopls
gopls related issues
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.