-
Notifications
You must be signed in to change notification settings - Fork 949
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test: modify the env test #2872
Conversation
Signed-off-by: Lang Chi <21860405@zju.edu.cn>
Codecov Report
@@ Coverage Diff @@
## master #2872 +/- ##
==========================================
- Coverage 69.09% 69.04% -0.06%
==========================================
Files 285 285
Lines 17844 17844
==========================================
- Hits 12330 12321 -9
- Misses 4114 4117 +3
- Partials 1400 1406 +6
|
@@ -305,7 +305,7 @@ func (suite *PouchCreateSuite) TestCreateWithEnv(c *check.C) { | |||
env3 := "TEST3" // should not in container's real env | |||
env4 := "TEST4=a b" // valid | |||
env5 := "TEST5=a=b" // valid | |||
res := command.PouchRun("run", "-d", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why change to create here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is "create" test, So I feel "create+start" is more suitable than "run".
LGTM |
Signed-off-by: Lang Chi 21860405@zju.edu.cn
Ⅰ. Describe what this PR did
Modify the env test in test/cli_create_test.go
Ⅱ. Does this pull request fix one issue?
NONE
Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗?)
No need!
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews