This is liable to change in the future.
A go_test() rule builds a native binary from the supplied set of Go source files and a generated main file. It's similar to the go test command.
Note: Buck is currently tested with (and therefore supports) version 1.10 of Go.
The name of the rule.
The set of source files to be compiled by this rule. .go files will be compiled with the Go compiler, .s files will be compiled with the assembler, and everything else is assumed to be files that may be
#included by the assembler.
Specify the library that this internal test is testing. This will copy the
depsfrom the target specified so you don't have to duplicate them.
go.prefix + path relative to the buck root + "_test") #
Sets the full name of the test package being compiled. This defaults to the path from the buck root with "_test" appended. (e.g. given a ./.buckconfig, a rule in ./a/b/BUCK defaults to package "a/b_test")
Note: if you want to test packages internally (i.e. same package name), use the
libraryparameter instead of setting
package_nameto include the tested source files.
Test coverage functionality will be included in the executable. Modes: set, count, atomic
The set of dependencies of this rule. Currently, this only supports go_library rules.
The set of additional compiler flags to pass to
go tool compile.
The set of additional assembler flags to pass to
go tool asm.
Static files to be symlinked into the working directory of the test. You can access these in your by opening the files as relative paths, e.g.
A list of labels to be applied to these tests. These labels are arbitrary text strings and have no meaning within buck itself. They can, however, have meaning for you as a test author (e.g.,
fast). A label can be used to filter or include a specific test rule when executing
If set specifies the maximum amount of time (in milliseconds) in which all of the tests in this rule should complete. This overrides the default
rule_timeoutif any has been specified in test.rule_timeout.
If set to
True, the test(s) in this rule are run separately from all other tests. (This is useful for integration tests which access a physical device or other limited resource.)
If unset, the test(s) in this rule in parallel with all other tests.
List of build target patterns that identify the build rules that can include this rule as a dependency, for example, by listing it in their
exported_depsattributes. For more information, see visibility.
For more examples, check out our integration tests.
go_library( name='greeting', srcs=[ 'greeting.go', ], deps=[ ':join', ], ) go_test( name='greeting-test', srcs=[ 'greeting_ext_test.go', ], deps=[ ':greeting' ], ) go_test( name='greeting-internal-test', package_name='greeting', srcs=[ 'greeting.go', 'greeting_test.go', ], deps=[ ':join', ], ) # Or go_test( name='greeting-better-internal-test', srcs=['greeting_test.go'], library=':greeting', )