blocks|key|1950251|text|测试包在加载时修改全局环境:它注册了许多命令行标志。因此，我们可以检查这些标志是否已注册：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1950252|func+init()+{
++++if+flag.Lookup("test.v")+==+nil+{
++++++++fmt.Println("normal+run")
++++}+else+{
++++++++fmt.Println("run+under+go+test")
++++}
}|code-block|syntax|javascript|1950253|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

The testing package modifies the global environment when loaded: it registers a lot of command-line flags. So, we can check if these flags are registered:

<pre><code>func init() {
 if flag.Lookup("test.v") == nil {
 fmt.Println("normal run")
 } else {
 fmt.Println("run under go test")
 }
}
</code></pre>

blocks|key|44742|text|由于flag.Lookup("test.v")方法对我不起作用，我想分享我自己的解决方案：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|44743|strings.HasSuffix(os.Args[0],+".test")|code-block|syntax|javascript|44744|或|44745|strings.Contains(os.Args[0],+"/_test/")|44746|这两种方法似乎都很有效。|44747|entityMap^0|2|L|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|W|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|Y|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|R|$]]

Since the <code>flag.Lookup("test.v")</code> approach does not work for me, I'd like to share my own solution:

<pre><code>strings.HasSuffix(os.Args[0], ".test")
</code></pre>

Or 

<pre><code>strings.Contains(os.Args[0], "/_test/")
</code></pre>

Both seem to work.

blocks|key|4781807|text|代码示例会有所帮助。但是，从您的问题听起来，您似乎已经在某个地方硬编码了一个指向配置文件的路径，而您可能希望将其传递给配置文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4781808|更改正在测试的函数，以获取定义配置文件的参数，然后在测试代码中传递与在非测试代码中使用的路径不同的路径。在测试和生产时，您的代码使用不同的路径是不好的做法。|4781809|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Code examples would help. But from your question it sounds like you've hardcoded a path to a config file somewhere when you probably wanted to pass it in instead.

Change the function you are testing to take a parameter defining the config file and then in your test code pass a different path in than you use in the non test code. It's bad practice for your code to have a different path when testing vs production.

blocks|key|43741|text|一种可能性是使用build+constraints。如果您以以下方式运行go+test：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|43742|go+test+-tags+testing+pkgname|code-block|syntax|javascript|43743|然后，您可以使用该标记来选择哪些文件将包含在包的标准构建中，以及哪些文件将用于测试。|43744|如果您将您的标准配置放在它自己的文件中，那么在顶部添加一行如下所示将确保它不会用于测试：|43745|//+%2Bbuild+!testing|43746|然后，您可以将测试配置包含在其中一个*_test.go文件中，或者包含在需要设置testing标记的其他文件中。|43747|entityMap|0|LINK|mutability|MUTABLE|url|http://golang.org/pkg/go/build/#hdr-Build_Constraints^0|10|7|8|H|0|0|0|0|0|0|I|9|14|7|0^^$0|@$1|2|3|4|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@$9|13|A|14|1|15]]|E|$]]|$1|F|3|G|5|H|7|16|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|17|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|18|8|@]|D|@]|E|$]]|$1|O|3|P|5|H|7|19|8|@]|D|@]|E|$I|J]]|$1|Q|3|R|5|6|7|1A|8|@$9|1B|A|1C|B|C]|$9|1D|A|1E|B|C]]|D|@]|E|$]]|$1|S|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]]|T|$U|$5|V|W|X|E|$Y|Z]]]]

One possibility would be to use <a href="http://golang.org/pkg/go/build/#hdr-Build_Constraints" rel="noreferrer">build constraints</a>. If you run <code>go test</code> as:

<pre><code>go test -tags testing pkgname
</code></pre>

Then you can use that tag to select which files will be included in a standard build of your package, and which will be used for testing.

If you put your standard configuration in a file of its own, then adding a line to the top like the following will ensure that it is not used for testing:

<pre><code>// +build !testing
</code></pre>

You can then include the testing configuration in one of the <code>*_test.go</code> files, or in some other file that requires that the <code>testing</code> tag be set.

blocks|key|1956248|text|flag.Lookup("test.v")+==+nil方法似乎可以工作，但我建议您使用TestMain，它是专门为测试而设计的，允许进行特定的设置和拆卸。如果将此方法包含在要测试的包中，则会在单个测试之前调用该方法，因此您可以在调用m.Run()之前设置全局标志或执行任何特定于测试的配置，如下所示|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1956249|func+TestMain(m+*testing.M)+{
++++//+test+context+initialization+here
++++os.Exit(m.Run())
}|code-block|syntax|javascript|1956250|PS:这实际上是@calvin-sugianto建议的，除了Gin与此无关|1956251|entityMap|0|LINK|mutability|MUTABLE|url|https://golang.org/pkg/testing/#hdr-Main^0|0|S|18|8|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@$9|X|A|Y|1|Z]]|E|$]]|$1|F|3|G|5|H|7|10|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|11|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

The <code>flag.Lookup("test.v") == nil</code> method seems to work but I would recommend using <a href="https://golang.org/pkg/testing/#hdr-Main" rel="noreferrer">TestMain</a>, which is specifically designed to allow specific setup and teardown for tests. If you include this method in the package you want to test, it will be called before your individual tests and so you can set a global flag or perform whatever test-specific configuration you want to do before calling m.Run() as follows

<pre><code>func TestMain(m *testing.M) {
 // test context initialization here
 os.Exit(m.Run())
}
</code></pre>

PS: this is actually what @calvin-sugianto suggested, except Gin has nothing to do with it

blocks|key|1950319|text|flag.Lookup("test.v")解决方案也不适合我(go+1.13)，而且我有很多服务需要维护，在每个服务中都使用func+TestMain(m+*testing.M)解决方案是不可行的。由于所有服务共享一个公共库，因此我提出了以下解决方案：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1950320|func+isInTests()+bool+{
++++for+_,+arg+:=+range+os.Args+{
++++++++if+strings.HasPrefix(arg,+"-test.v=")+{
++++++++++++return+true
++++++++}
++++}
++++return+false
}|code-block|syntax|javascript|1950321|这类似于flag.Lookup("test.v")解决方案，因为我们要检查是否存在-test.v。|1950322|编辑：基于@mh-cbon注释更新了代码|BOLD|1950323|entityMap^0|0|L|1Q|R|0|0|4|L|15|7|0|0|2|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]|$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|W|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|X|8|@$9|Y|A|Z|B|C]|$9|10|A|11|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|12|8|@$9|13|A|14|B|O]]|D|@]|E|$]]|$1|P|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|Q|$]]

The <code>flag.Lookup("test.v")</code> solution does not work for me either (go 1.13), and I have lots of services to maintain and it is not feasible to use the <code>func TestMain(m *testing.M)</code> solution in every service. As all the services share a common library, I've come up with the following solution:

<pre><code>func isInTests() bool {
 for _, arg := range os.Args {
 if strings.HasPrefix(arg, "-test.v=") {
 return true
 }
 }
 return false
}
</code></pre>

This is similar to the <code>flag.Lookup("test.v")</code> solution because we check if <code>-test.v</code> is present.

EDIT: updated the code based on @mh-cbon comment

blocks|key|2668958|text|我刚接触golang，flag.Lookup("test.v")对我不起作用，所以我找到了一种方法，通过在init()中设置ENV变量来识别上下文是测试的还是正常的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2668959|如果您有测试文件，例如abc.text.go，请在init()中将环境变量"GO_ENV“设置为testing。|2668960|func+init()+{
++++os.Setenv("GO_ENV",+"testing")
}|code-block|syntax|javascript|2668961|只要你想知道上下文，就使用os.Getenv("GO_ENV")|2668962|abc.go|2668963|if+os.Getenv("GO_ENV")+==+"testing"+{

}+else+{

}|2668964|entityMap^0|B|L|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|Z|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|10|8|@]|D|@]|E|$]]|$1|Q|3|R|5|J|7|11|8|@]|D|@]|E|$K|L]]|$1|S|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|T|$]]

I am new to golang and <code>flag.Lookup("test.v")</code> did not work for me, So i have found way to identify if context is testing or normal by setting ENV variable in init().

If you have test file for example abc.text.go, set env variable "GO_ENV" to testing in init().

<pre><code>func init() {
 os.Setenv("GO_ENV", "testing")
}
</code></pre>

And where ever you want to know the context use os.Getenv("GO_ENV") 
abc.go

<pre><code>if os.Getenv("GO_ENV") == "testing" {

} else {

}
</code></pre>

blocks|key|1950352|text|与Pram的答案类似，我可能会在运行测试时设置一个环境变量。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1950353|Makefile|1950354|test:
+ENV=testing+go+test+./...|code-block|syntax|javascript|1950355|main.go|1950356|++env+:=+os.Getenv("ENV")|1950357|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Similar to Pram's answer I might set an environment variable when you run the tests.
Makefile
<pre><code>test:
 ENV=testing go test ./...
</code></pre>
main.go
<pre><code> env := os.Getenv(&quot;ENV&quot;)
</code></pre>

blocks|key|1956207|text|Garrett的解决方案是更强大的解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1956208|+func+init()+{
++++if+v+:=+flag.Lookup("test.v");+v+==+nil+%7C%7C+v.Value.String()+!=+"true"+{
++++++++fmt.Println("normal+run")
++++}+else+{
++++++++fmt.Println("run+under+go+test")
++++}
+}|code-block|syntax|javascript|1956209|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

More robust solution that Garrett's one is:

<pre><code> func init() {
 if v := flag.Lookup("test.v"); v == nil || v.Value.String() != "true" {
 fmt.Println("normal run")
 } else {
 fmt.Println("run under go test")
 }
 }
</code></pre>

blocks|key|1950342|text|如果您试图检测文件是否正在通过"go+run“与可执行文件运行，此函数将检查目录中是否包含"/Temp/go-build”(还会检查\是否支持windows+)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1950343|if+strings.Index(os.Args[0],+"/Temp/go-build")+!=+-1+%7C%7C+strings.Index(os.Args[0],+"\\Temp\\go-build")+!=+-1+{
++++//+ran+with+go+run
}+else+{
++++//+ran+as+executable+file
}|code-block|syntax|javascript|1950344|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

If your trying to detect if the file is being run through &quot;go run&quot; vs an executable, this function checks if the directory contains &quot;/Temp/go-build&quot; (also checks for \ for windows support)
<pre><code>if strings.Index(os.Args[0], &quot;/Temp/go-build&quot;) != -1 || strings.Index(os.Args[0], &quot;\\Temp\\go-build&quot;) != -1 {
 // ran with go run
} else {
 // ran as executable file
}
</code></pre>

When I run "go test", I want to use a different configuration file. How do I know within my code if I'm running within a test context or a normal context? Is there some sort of environment variable to check?

How do I know I'm running within "go test"

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

当我运行"go test“时，我想使用一个不同的配置文件。如何在我的代码中知道我是在测试上下文中运行还是在正常上下文中运行？是否有某种环境变量需要检查？

问我如何知道我是在"go test“中运行？
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我如何知道我是在"go test“中运行？EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我如何知道我是在"go test“中运行？
EN