tree 2aced51bc5e2935a1ca706782532598a59ee3255
parent 945a47e5ce50767ae895065bed1457c0e4b284bc
author Ethan Reesor <ethan.reesor@gmail.com> 1629170411 +0000
committer Hyang-Ah Hana Kim <hyangah@gmail.com> 1629170684 +0000

src/goTestExplorer: implement a test provider for the new test api

What this does:
- Implements a test provider using the new API
- Populates the test explorer with a list of modules and/or workspaces
- Populates each module/workspace/package/file as it is expanded
- Creates test entries for the current file, and package/module parents
- Runs tests!

What this does not:
- Debug tests
- Handle stretchr suites

Issues:
- Handling of benchmarks isn't great. But I'm not sure it can get much
  better without changes to `go test`.
- If a test has subtests, I add those subtests. This can get annoying if
  you have a bunch of subtests. Should this be configurable? Disabling
  `testing.followRunningTest` can improve this UX.

Fixes golang/vscode-go#1579

Change-Id: I027c7c3b615eda4c528da9739520e6bfd1aa6911
GitHub-Last-Rev: 59af29b6a2f585135a58b91ed6cc842796219512
GitHub-Pull-Request: golang/vscode-go#1590
Reviewed-on: https://go-review.googlesource.com/c/vscode-go/+/330809
Reviewed-by: Hyang-Ah Hana Kim <hyangah@gmail.com>
Trust: Hyang-Ah Hana Kim <hyangah@gmail.com>
Trust: Suzy Mueller <suzmue@golang.org>