Files
golang.go/test
Joel Sing 3a29ebeef9 cmd/compile: additional optimisation for CZEROEQZ/CZERONEZ on riscv64
Negation on a condition can be eliminated.

Change-Id: I94fab5f019cbaebb2ca589e1d8796a9cb72f3894
Reviewed-on: https://go-review.googlesource.com/c/go/+/748401
Reviewed-by: Xueqi Luo <1824368278@qq.com>
Reviewed-by: Cherry Mui <cherryyz@google.com>
Reviewed-by: Keith Randall <khr@golang.org>
Reviewed-by: Keith Randall <khr@google.com>
Reviewed-by: Julian Zhu <jz531210@gmail.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Auto-Submit: Keith Randall <khr@golang.org>
2026-03-06 14:39:32 -08:00
..
2025-10-29 11:00:23 -07:00
2024-03-25 19:21:35 +00:00
2023-01-31 19:43:07 +00:00
2023-04-11 20:56:32 +00:00
2026-02-10 09:15:43 -08:00
2025-10-29 11:00:23 -07:00
2025-10-29 11:00:23 -07: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
2026-03-06 13:03:28 -08: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.