您需要 登录 才可以下载或查看，没有帐号？立即注册
Output's go test -vas TAP.
Patter has no arguments. It reads from STDIN, the output of go test -v, and outputs TAP v13compatible output.
Suppose the current directory has a test file, foo_test.go. Running go test -v ./...might produce the following output:
If we, instead, pipe the output of go test -v ./...into patter, we get the following output: 复制代码
- $ go test -v ./...
- === RUN TestSkip
- --- SKIP: TestSkip (0.00s)
- foo_test.go:6: this test is being skipped
- === RUN TestError
- --- FAIL: TestError (0.00s)
- foo_test.go:10: this test is erroring
- === RUN Test2Errors
- --- FAIL: Test2Errors (0.00s)
- foo_test.go:14: this test is error 1
- foo_test.go:15: this test is error 2
- === RUN TestFatal
- --- FAIL: TestFatal (0.00s)
- foo_test.go:19: this test is fataling
- === RUN TestOK
- --- PASS: TestOK (0.00s)
- exit status 1
- FAIL github.com/apg/patter 0.007s
Because patterdoesn't know how many tests will be run, it outputs the plan line (e.g. 1..5) at the end. This is allowed via the spec. 复制代码
- $ go test -v ./... | patter
- TAP version 13
- ok 1 # skip TestSkip (0.00s)
- # foo_test.go:6: this test is being skipped
- not ok 2 - TestError (0.00s)
- # foo_test.go:10: this test is erroring
- not ok 3 - Test2Error (0.00s)
- # foo_test.go:14: this test is error 1
- # foo_test.go:15: this test is error 2
- not ok 4 - TestFatal (0.00s)
- # foo_test.go:19: this test is fataling
- ok 5 - TestOK (0.00s)
It's possible that patterwill encounter I/O errors while reading from STDIN. If this happens, patter bails outusing the special words Bail out!followed by an error message. This is the expected emergency behaviour of TAP.
Contributions are welcome, and encouraged! Please open an issue before a Pull Request to avoid duplicated effort, and/or functionality that will not be merged.
(c) 2016, Andrew Gwozdziewycz [email protected]
See LICENSE file for more information.