https://codereview.appspot.com/99670045/diff/40001/cmd/supercommand_test.go#newcode11
cmd/supercommand_test.go:11: gitjujutesting "github.com/juju/testing"
We use just "github.com/juju/testing" and coretesting for
"launchpad.net/juju-core/testing" elsewhere.
Anyway this makes the diff short and clean, so <shrug>.
Do we have conventions for import names?
https://codereview.appspot.com/99670045/diff/40001/testing/base.go#newcode33
testing/base.go:33: t.CleanupSuite.SetUpSuite(c)
In the Isolation suite we use the reversed order:
s.CleanupSuite.SetUpSuite(c)
s.LoggingSuite.SetUpSuite(c)
I don't think in this case it makes so much difference, but keeping them
in sync now can avoid some confusion in the future.
What do you think?
This also applies to sync_test.
Thanks for this branch Roger!
LGTM with some minor/questions below.
https:/ /codereview. appspot. com/99670045/ diff/40001/ cmd/package_ test.go
File cmd/package_test.go (right):
https:/ /codereview. appspot. com/99670045/ diff/40001/ cmd/package_ test.go# newcode26 test.go: 26: jc.DeepEquals, com/juju/ testing/ checkers. DeepEquals is preferred net/gocheck. DeepEquals.
cmd/package_
So I presume github.
over launchpad.
https:/ /codereview. appspot. com/99670045/ diff/40001/ cmd/supercomman d_test. go d_test. go (right):
File cmd/supercomman
https:/ /codereview. appspot. com/99670045/ diff/40001/ cmd/supercomman d_test. go#newcode11 d_test. go:11: gitjujutesting "github. com/juju/ testing" com/juju/ testing" and coretesting for net/juju- core/testing" elsewhere.
cmd/supercomman
We use just "github.
"launchpad.
Anyway this makes the diff short and clean, so <shrug>.
Do we have conventions for import names?
https:/ /codereview. appspot. com/99670045/ diff/40001/ cmd/supercomman d_test. go#newcode28 d_test. go:28: gitjujutesting. IsolationSuite
cmd/supercomman
Cool.
https:/ /codereview. appspot. com/99670045/ diff/40001/ testing/ base.go
File testing/base.go (right):
https:/ /codereview. appspot. com/99670045/ diff/40001/ testing/ base.go# newcode33 SetUpSuite( c) SetUpSuite( c) SetUpSuite( c)
testing/base.go:33: t.CleanupSuite.
In the Isolation suite we use the reversed order:
s.CleanupSuite.
s.LoggingSuite.
I don't think in this case it makes so much difference, but keeping them
in sync now can avoid some confusion in the future.
What do you think?
This also applies to sync_test.
https:/ /codereview. appspot. com/99670045/ diff/40001/ testing/ imports. go
File testing/imports.go (right):
https:/ /codereview. appspot. com/99670045/ diff/40001/ testing/ imports. go#newcode17 imports. go:17: imps, err := testing. FindImports( packageName,
testing/
jujuPkgPrefix)
Nice.
https:/ /codereview. appspot. com/99670045/ diff/40001/ utils/exec/ package_ test.go package_ test.go (right):
File utils/exec/
https:/ /codereview. appspot. com/99670045/ diff/40001/ utils/exec/ package_ test.go# newcode7 package_ test.go: 7: stdtesting "testing"
utils/exec/
This looks like an import error: stdtesting vs testing.
https:/ /codereview. appspot. com/99670045/ diff/40001/ utils/fslock/ package_ test.go package_ test.go (right):
File utils/fslock/
https:/ /codereview. appspot. com/99670045/ diff/40001/ utils/fslock/ package_ test.go# newcode7 package_ test.go: 7: stdtesting "testing"
utils/fslock/
Ditto.
https:/ /codereview. appspot. com/99670045/