go-test(1) [debian man page]

GO-TEST(1)						      General Commands Manual							GO-TEST(1)

NAME

       go - tool for managing Go source code

SYNOPSIS

       go test [-c] [-i] [ build flags ] [ packages ] [ flags for test binary ]

DESCRIPTION

       "Go test" automates testing the packages named by the import paths.  It prints a summary of the test results in the format:

	     ok   archive/tar	0.011s
	     FAIL archive/zip	0.022s
	     ok   compress/gzip 0.033s
	     ...

       followed by detailed output for each failed package.

       "Go  test"  recompiles each package along with any files with names matching the file pattern "*_test.go".  These additional files can con-
       tain test functions, benchmark functions, and example functions.  See go-testfunc(7) for more.

       By default, go test needs no arguments.	It compiles and tests the package with source in the current directory, including tests, and  runs
       the tests.

       The package is built in a temporary directory so it does not interfere with the non-test installation.

OPTIONS

       In addition to the build flags, the flags handled by 'go test' itself are:

       -c     Compile the test binary to pkg.test but do not run it.

       -i     Install packages that are dependencies of the test.  Do not run the test.

       The  test  binary  also accepts flags that control execution of the test; these flags are also accessible by 'go test'.	See go-testflag(7)
       for details.

       For more about build flags, see go-build(1).

       For more about specifying packages, see go-packages(7).

SEE ALSO

       go-build(1), go-vet(1).

AUTHOR

       This manual page was written by Michael Stapelberg <stapelberg@debian.org>, for the Debian project (and may be used by others).

								    2012-05-13								GO-TEST(1)

GO-BUILD(1)						      General Commands Manual						       GO-BUILD(1)

NAME

       go - tool for managing Go source code

SYNOPSIS

       go build [-o output] [ build flags ] [ packages ]

DESCRIPTION

       Build compiles the packages named by the import paths, along with their dependencies, but it does not install the results.

       If the arguments are a list of .go files, build treats them as a list of source files specifying a single package.

       When the command line specifies a single main package, build writes the resulting executable to output.	Otherwise build compiles the pack-
       ages but discards the results, serving only as a check that the packages can be built.

       The -o flag specifies the output file name.  If not specified, the name is packagename.a (for a non-main package) or the base name  of  the
       first source file (for a main package).

OPTIONS

       The build flags are shared by the build, install, run, and test commands:

       -a     force rebuilding of packages that are already up-to-date.

       -n     print the commands but do not run them.

       -p n   the number of builds that can be run in parallel. The default is the number of CPUs available.

       -v     print the names of packages as they are compiled.

       -work  print the name of the temporary work directory and do not delete it when exiting.

       -x     print the commands.

       -compiler name
	      name of compiler to use, as in runtime.Compiler (gccgo or gc)

       -gccgoflags 'arg list'
	      arguments to pass on each gccgo compiler/linker invocation

       -gcflags 'arg list'
	      arguments to pass on each 5g, 6g, or 8g compiler invocation

       -ldflags 'flag list'
	      arguments to pass on each 5l, 6l, or 8l linker invocation

       -tags 'tag list'
	      a  list  of  build tags to consider satisfied during the build.  See the documentation for the go/build package for more information
	      about build tags.

       For more about specifying packages, see go-packages(7).

       For more about where packages and binaries are installed, see go-gopath(1).

SEE ALSO

       go-install(1), go-get(1), go-clean(1).

AUTHOR

       This manual page was written by Michael Stapelberg <stapelberg@debian.org>, for the Debian project (and may be used by others).

								    2012-05-13							       GO-BUILD(1)