blocks|key|64974|text|不能，您必须使用exec.Command并测试返回值。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|64975|entityMap^0|8|C|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

You can't, you would have to use <code>exec.Command</code> and test the returned value.

blocks|key|65008|text|测试代码：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|65009|package+main
import+"os"

var+my_private_exit_function+func(code+int)+=+os.Exit

func+main()+{
++++MyAbstractFunctionAndExit(1)
}

func+MyAbstractFunctionAndExit(exit+int)+{
++++my_private_exit_function(exit)
}|code-block|syntax|javascript|65010|65011|package+main

import+(
++++"os"
++++"testing"
)

func+TestMyAbstractFunctionAndExit(t+*testing.T)+{
++++var+ok+bool+=+false+//+The+default+value+can+be+omitted+:)

++++//+Prepare+testing
++++my_private_exit_function+=+func(c+int)+{
++++++++ok+=+true
++++}
++++//+Run+function
++++MyAbstractFunctionAndExit(1)
++++//+Check
++++if+ok+==+false+{
++++++++t.Errorf("Error+in+AbstractFunction()")
++++}
++++//+Restore+if+need
++++my_private_exit_function+=+os.Exit
}|65012|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|M|8|@]|9|@]|A|$E|F]]|$1|G|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|H|3|I|5|D|7|O|8|@]|9|@]|A|$E|F]]|$1|J|3|-4|5|6|7|P|8|@]|9|@]|A|$]]]|K|$]]

Code for testing:

<pre><code>package main
import "os"

var my_private_exit_function func(code int) = os.Exit

func main() {
 MyAbstractFunctionAndExit(1)
}

func MyAbstractFunctionAndExit(exit int) {
 my_private_exit_function(exit)
}
</code></pre>

Testing code:

<pre><code>package main

import (
 "os"
 "testing"
)

func TestMyAbstractFunctionAndExit(t *testing.T) {
 var ok bool = false // The default value can be omitted :)

 // Prepare testing
 my_private_exit_function = func(c int) {
 ok = true
 }
 // Run function
 MyAbstractFunctionAndExit(1)
 // Check
 if ok == false {
 t.Errorf("Error in AbstractFunction()")
 }
 // Restore if need
 my_private_exit_function = os.Exit
}
</code></pre>

blocks|key|65036|text|有一个Andrew+Gerrand的presentation+(+Go团队的核心成员之一)，他展示了如何做到这一点。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|65037|给定一个函数(在main.go中)|style|CODE|65038|package+main

import+(
++++"fmt"
++++"os"
)

func+Crasher()+{
++++fmt.Println("Going+down+in+flames!")
++++os.Exit(1)
}|code-block|syntax|javascript|65039|下面是测试它的方法(通过main_test.go)：|65040|package+main

import+(
++++"os"
++++"os/exec"
++++"testing"
)

func+TestCrasher(t+*testing.T)+{
++++if+os.Getenv("BE_CRASHER")+==+"1"+{
++++++++Crasher()
++++++++return
++++}
++++cmd+:=+exec.Command(os.Args[0],+"-test.run=TestCrasher")
++++cmd.Env+=+append(os.Environ(),+"BE_CRASHER=1")
++++err+:=+cmd.Run()
++++if+e,+ok+:=+err.(*exec.ExitError);+ok+&&+!e.Success()+{
++++++++return
++++}
++++t.Fatalf("process+ran+with+err+%25v,+want+exit+status+1",+err)
}|65041|代码所做的是通过exec.Command在单独的进程中再次调用go+test，将执行限制为TestCrasher测试(通过-test.run=TestCrasher开关)。它还通过环境变量(BE_CRASHER=1)传入一个标志，第二次调用将检查该标志，如果设置了该标志，则调用被测系统，然后立即返回以防止进入无限循环。因此，我们被放回原来的调用点，现在可以验证实际的退出代码。|65042|来源:安德鲁演示文稿的Slide+23。第二张幻灯片也包含指向presentation's+video的链接。他谈到了47:09的子过程测试|65043|entityMap|0|LINK|mutability|MUTABLE|url|https://talks.golang.org/2014/testing.slide|1|https://talks.golang.org/2014/testing.slide#23|2|http://www.youtube.com/watch?v=ndmB0bj7eyw|3|https://youtu.be/ndmB0bj7eyw?t=2834^0|I|C|0|0|8|7|0|0|C|C|0|0|8|C|V|7|19|B|1P|L|2N|C|0|B|8|1|V|K|2|1N|5|3|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@$A|19|B|1A|1|1B]]|C|$]]|$1|D|3|E|5|6|7|1C|8|@$A|1D|B|1E|F|G]]|9|@]|C|$]]|$1|H|3|I|5|J|7|1F|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|1G|8|@$A|1H|B|1I|F|G]]|9|@]|C|$]]|$1|O|3|P|5|J|7|1J|8|@]|9|@]|C|$K|L]]|$1|Q|3|R|5|6|7|1K|8|@$A|1L|B|1M|F|G]|$A|1N|B|1O|F|G]|$A|1P|B|1Q|F|G]|$A|1R|B|1S|F|G]|$A|1T|B|1U|F|G]]|9|@]|C|$]]|$1|S|3|T|5|6|7|1V|8|@]|9|@$A|1W|B|1X|1|1Y]|$A|1Z|B|20|1|21]|$A|22|B|23|1|24]]|C|$]]|$1|U|3|-4|5|6|7|25|8|@]|9|@]|C|$]]]|V|$W|$5|X|Y|Z|C|$10|11]]|12|$5|X|Y|Z|C|$10|13]]|14|$5|X|Y|Z|C|$10|15]]|16|$5|X|Y|Z|C|$10|17]]]]

There's a <a href="https://talks.golang.org/2014/testing.slide" rel="noreferrer">presentation</a> by Andrew Gerrand (one of the core members of the Go team) where he shows how to do it.

Given a function (in <code>main.go</code>)

<pre><code>package main

import (
 "fmt"
 "os"
)

func Crasher() {
 fmt.Println("Going down in flames!")
 os.Exit(1)
}
</code></pre>

here's how you would test it (through <code>main_test.go</code>):

<pre><code>package main

import (
 "os"
 "os/exec"
 "testing"
)

func TestCrasher(t *testing.T) {
 if os.Getenv("BE_CRASHER") == "1" {
 Crasher()
 return
 }
 cmd := exec.Command(os.Args[0], "-test.run=TestCrasher")
 cmd.Env = append(os.Environ(), "BE_CRASHER=1")
 err := cmd.Run()
 if e, ok := err.(*exec.ExitError); ok &amp;&amp; !e.Success() {
 return
 }
 t.Fatalf("process ran with err %v, want exit status 1", err)
}
</code></pre>

What the code does is invoke <code>go test</code> again in a separate process through <code>exec.Command</code>, limiting execution to the <code>TestCrasher</code> test (via the <code>-test.run=TestCrasher</code> switch). It also passes in a flag via an environment variable (<code>BE_CRASHER=1</code>) which the second invocation checks for and, if set, calls the system-under-test, returning immediately afterwards to prevent running into an infinite loop. Thus, we are being dropped back into our original call site and may now validate the actual exit code.

Source: <a href="https://talks.golang.org/2014/testing.slide#23" rel="noreferrer">Slide 23</a> of Andrew's presentation. The second slide contains a link to the <a href="http://www.youtube.com/watch?v=ndmB0bj7eyw" rel="noreferrer">presentation's video</a> as well.
He talks about subprocess tests at <a href="https://youtu.be/ndmB0bj7eyw?t=2834" rel="noreferrer">47:09</a>

blocks|key|65083|text|我通过使用bouk/monkey来实现这一点|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|65084|func+TestDoomed(t+*testing.T)+{
++fakeExit+:=+func(int)+{
++++panic("os.Exit+called")++++++
++}
++patch+:=+monkey.Patch(os.Exit,+fakeExit)
++defer+patch.Unpatch()
++assert.PanicsWithValue(t,+"os.Exit+called",+doomed,+"os.Exit+was+not+called")
}|code-block|syntax|javascript|65085|当涉及到这类工作，以及故障注入和其他困难任务时，monkey是超级强大的。它确实来自with+some+caveats。|65086|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/bouk/monkey|1|https://github.com/bouk/monkey#notes^0|5|B|0|0|0|16|H|1|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|Z|8|@]|9|@$A|10|B|11|1|12]]|C|$]]|$1|K|3|-4|5|6|7|13|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]|S|$5|N|O|P|C|$Q|T]]]]

I do this by using <a href="https://github.com/bouk/monkey" rel="noreferrer">bouk/monkey</a>:

<pre><code>func TestDoomed(t *testing.T) {
 fakeExit := func(int) {
 panic("os.Exit called") 
 }
 patch := monkey.Patch(os.Exit, fakeExit)
 defer patch.Unpatch()
 assert.PanicsWithValue(t, "os.Exit called", doomed, "os.Exit was not called")
}
</code></pre>

monkey is super-powerful when it comes to this sort of work, and for fault injection and other difficult tasks. It does come <a href="https://github.com/bouk/monkey#notes" rel="noreferrer">with some caveats</a>.

Given this code
<pre><code>func doomed() {
 os.Exit(1)
}
</code></pre>
How do I properly test that calling this function will result in an exit using <code>go test</code>? This needs to occur within a suite of tests, in other words the <code>os.Exit()</code> call cannot impact the other tests and should be trapped.

How to test os.exit scenarios in Go

给定以下代码func doomed() {  os.Exit(1)}如何正确测试调用此函数是否会导致使用go test退出？这需要在一组测试中发生，换句话说，os.Exit()调用不会影响其他测试，应该被捕获。

问如何在Go中测试os.exit场景
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在Go中测试os.exit场景EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在Go中测试os.exit场景
EN