Files
go/test
Joel Sing 7971fcdf53 test/codegen: tidy tests for bits
Use Go idiomatic function names, use a common prefix, attempt to
maintain some consistency, avoid naming functions based upon
machine specific instructions and combine a duplicate test that
likely exists due to this confusion.

Change-Id: I996e9efd7497821edef94c1997d4a310d9d79a71
Reviewed-on: https://go-review.googlesource.com/c/go/+/732200
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Cherry Mui <cherryyz@google.com>
Auto-Submit: Joel Sing <joel@sing.id.au>
Reviewed-by: Michael Knyszek <mknyszek@google.com>
2025-12-26 07:51:44 -08:00
..
2025-12-26 07:51:44 -08:00
2025-10-29 11:00:23 -07:00
2024-03-25 19:21:35 +00:00
2025-10-29 11:00:23 -07:00
2023-01-31 19:43:07 +00:00
2023-04-11 20:56:32 +00:00
2025-10-29 11:00:23 -07:00
2025-10-29 11:00:23 -07:00
2020-11-28 02:31:54 +00:00
2025-07-30 11:47:14 -07:00
2024-04-04 14:29:45 +00:00
2025-05-08 10:18:37 -07:00
2025-10-29 11:00:23 -07:00
2021-10-06 15:53:04 +00:00

The test directory contains tests of the Go tool chain and runtime. It includes black box tests, regression tests, and error output tests. They are run as part of all.bash.

To run just these tests, execute:

../bin/go test cmd/internal/testdir

To run just tests from specified files in this directory, execute:

../bin/go test cmd/internal/testdir -run='Test/(file1.go|file2.go|...)'

Standard library tests should be written as regular Go tests in the appropriate package.

The tool chain and runtime also have regular Go tests in their packages. The main reasons to add a new test to this directory are:

  • it is most naturally expressed using the test runner; or
  • it is also applicable to gccgo and other Go tool chains.