Golang test - Revision history

Pchero: /* Main */

2021-08-02T17:37:24Z

Main

← Older revision		Revision as of 17:37, 2 August 2021
Line 99:		Line 99:
	}		}
	</source>		</source>

			== linter ==
			Linter options
			* https://golangci-lint.run/usage/linters/

			<pre>
			$ golangci-lint help linters
			</pre>

	== See also ==		== See also ==

Pchero: /* Main */

2020-04-08T14:21:36Z

Main

← Older revision		Revision as of 14:21, 8 April 2020
Line 87:		Line 87:
	It is sometimes necessary for a test program to do extra setup or teardown before or after testing. It is also sometimes necessary for a test to control which code runs on the main thread. To support these and other cases, if a test file contains a function:		It is sometimes necessary for a test program to do extra setup or teardown before or after testing. It is also sometimes necessary for a test to control which code runs on the main thread. To support these and other cases, if a test file contains a function:
	<source lang=go>		<source lang=go>
			fund TestMain(m *testing.M)
	</source>		</source>

	<~~pre~~>		then the generated test will call TestMain(m) instead of running the tests directly. TestMain runs in the main goroutine and can do whatever setup and teardown is necessary around a call to m.Run. It should then call os.Exit with the result of m.Run. When TestMain is called, flag.Parse has not been run. If TestMain depends on command-line flags, including those of the testing packages, it should call flag.Parse explicitly.
	</~~pre~~>
			A simple implementation of TestMain is:
			<source lang=go>
			fund TestMain(m *testing.M) {
			// call flag.Parse() here if TestMain uses flags
			os.Exit(m.Run())
			}
			</source>

	== See also ==		== See also ==

Pchero: /* Main */

2020-04-08T11:59:16Z

Main

← Older revision		Revision as of 11:59, 8 April 2020
Line 85:		Line 85:

	== Main ==		== Main ==
	It is sometimes necessary for a test program to do extra setup or teardown before or after testing. It is		It is sometimes necessary for a test program to do extra setup or teardown before or after testing. It is also sometimes necessary for a test to control which code runs on the main thread. To support these and other cases, if a test file contains a function:
			<source lang=go>
			</source>

	<pre>		<pre>

Pchero: /* TestMain */

2020-04-08T11:52:21Z

TestMain

@@ Line 73: / Line 73: @@
 </source>
-== TestMain ==
+== Skipping ==
 <pre>

Pchero: /* Benchmarks */

2020-04-08T11:49:28Z

Benchmarks

@@ Line 56: / Line 56: @@
      big.Len()
+   }
+}
 </source>

Pchero: /* Benchmarks */

2020-04-08T11:46:41Z

Benchmarks

@@ Line 35: / Line 35: @@
 A sample benchmark function looks like this
 <source lang=go>
-fund BenchmarkHello(b * testing.B) {
+func BenchmarkHello(b * testing.B) {
+}
 </source>

Pchero: /* Basic */

2020-04-08T11:43:00Z

Basic

@@ Line 22: / Line 22: @@
+}
 </pre>
 == TestMain ==

Pchero: Created page with "== Overview == golang test 내용정리. == Basic == Package testing provides support for automated testing of Go packages. It is intended to be used in concert with the "go..."

2020-04-07T14:57:11Z

Created page with "== Overview == golang test 내용정리. == Basic == Package testing provides support for automated testing of Go packages. It is intended to be used in concert with the "go..."

New page

== Overview ==
golang test 내용정리.

== Basic ==
Package testing provides support for automated testing of Go packages. It is intended to be used in concert with the "go test" command, which automates execution of any function of the form
<pre>
func TestXxx(*testing.T)
</pre>
where Xxx does not start with a lowercase letter. The function name serves to identify the test routine.

With these functions, use the Error, Fail or related methods to signal failure.

To write a new test suite, create a file whose name ends _test.go that contains the TestXxx functions are described here. Put the file in the same package as the one being tested. The file will be excluded from regular package builds but will be included when the "go test" command is run. For more detail, run "go help test" and "go help testing".

A simple test function looks like this:
<pre>
fund TestAbs(t *testing.T) {
got := Abs(-1)
if got != 1 {
t.Errorf("Abs(-1) = %d; want 1", got)
}
}
</pre>

== TestMain ==

<pre>
</pre>

== See also ==
* https://golang.org/pkg/testing/ - Package testing

[[category:golang]]