Sponsored Content
Full Discussion: Infrastructure Testing
Special Forums UNIX and Linux Applications Infrastructure Monitoring Infrastructure Testing Post 302914135 by rdunne on Friday 22nd of August 2014 05:58:19 AM
Old 08-22-2014
what parts are u looking to test?
 

3 More Discussions You Might Find Interesting

1. What is on Your Mind?

freeware to document your IT infrastructure for unix

I just started using this good free software that lets you document your entire IT infrastructure. It's called Auditor Lite or Documentor for Unix and in my opinion it's the best software out there and the fact that it is free is even better. Just thought I would let you guys know if you want to... (1 Reply)
Discussion started by: itguy321
1 Replies

2. UNIX for Advanced & Expert Users

HOWTO plug server into infrastructure

Hi I consider how to plug server into infrastructure. What is the actual standard for sys admins to plug server and make it up and running. Whether use LACP/EtherChannel, IPMP, JumboFrame and when ? How to make server redundancy and fail-over to maximize its uptime ? How many network... (7 Replies)
Discussion started by: presul
7 Replies

3. Solaris

Solaris packages for Oracle grid infrastructure installation

Hello guys, I am trying to install oracle grid infrastructure 11.2 on Solaris 5.11. while I was reading the installation guide to check for the software requirements, there were two packages mentioned for the Solars 5.11. They are as follows pkg://solaris/developer/build/make... (2 Replies)
Discussion started by: zacsparrow
2 Replies
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)
All times are GMT -4. The time now is 12:51 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy