libcni: Fixed tests that were checking error strings.
authorAvinash Sridharan <avinash@mesosphere.com>
Tue, 4 Apr 2017 16:49:48 +0000 (16:49 +0000)
committerAvinash Sridharan <avinash@mesosphere.com>
Wed, 5 Apr 2017 21:40:24 +0000 (21:40 +0000)
Checking error strings makes these tests flaky, especially if the
error string is changed in libcni. Have gone ahead an introduced a new
error type `NoConfigsFoundError` and the Match is against the error
type making it more deterministic.

libcni/conf_test.go

index b9bd64e..40e0ca0 100644 (file)
@@ -61,7 +61,7 @@ var _ = Describe("Loading configuration from disk", func() {
 
                        It("returns a useful error", func() {
                                _, err := libcni.LoadConf(configDir, "some-plugin")
-                               Expect(err).To(MatchError("no net configurations found"))
+                               Expect(err).To(MatchError(libcni.NoConfigsFoundError{Dir: configDir}))
                        })
                })
 
@@ -244,7 +244,7 @@ var _ = Describe("Loading configuration from disk", func() {
 
                        It("returns a useful error", func() {
                                _, err := libcni.LoadConfList(configDir, "some-plugin")
-                               Expect(err).To(MatchError("no net configurations found"))
+                               Expect(err).To(MatchError(libcni.NoConfigsFoundError{Dir: configDir}))
                        })
                })