ExpectedError appears to only work without brackets about container-structure-test HOT 2 CLOSED

Hey @cognitiaclaeves, thanks for reporting. The strings provided to the expected/excluded output/error fields should actually be regexes, not raw strings. If you use the string Nomad v0\.7\.1\+ent \(83ac1d7316a79aacb09d349298e14e23a0aa9853\) (escaping special regex characters), your second example with the brackets will work.

This is unfortunately a bit of a misleading result, because the first test passed due to the fact that the field you provided to the expectedError was actually never parsed correctly. This made the test framework think you simply hadn't provided any fields to check, so everything seemed normal. This is just an unfortunate side effect of the way that YAML parsing works in golang.

from container-structure-test.

This made more sense. Your solution works for me. Thanks!

from container-structure-test.