Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Add a test for the mosquitto example. #418
Conversation
|
retest this please |
|
retest this please |
|
retest this please |
|
restest this please |
|
@elopio it needs to be LP: #XXXXX iirc, no worries, I'll fix when merging |
|
|
retest this please |
kyrofa
reviewed
Apr 8, 2016
| @@ -162,7 +162,7 @@ def install_snap(self, example_dir, snap_name, version): | ||
| def assert_command_in_snappy_testbed(self, command, expected_output): | ||
| if not config.get('skip-install', False): | ||
| output = self.run_command_in_snappy_testbed(command) | ||
| - self.assertEqual(output, expected_output) | ||
| + self.assertEqual(expected_output, output) |
kyrofa
Apr 8, 2016
Member
I've not been able to find documentation that unittest prefers one way or another. Should expected always come first?
elopio
Apr 8, 2016
Member
with testtools, the expected is first. When it fails, it prints like: expected: first argument, actual: second argument. I always get it wrong, but I try to update it when I see it fail with the wrong message.
with only unittest I think it doesn't matter, because it prints something like: first is not equal to second.
kyrofa
Apr 8, 2016
Member
Ah okay. Yeah I wish unittest would show you expected/actual-- I always have to look at the test itself to determine it.
|
Looks good to me! |
elopio commentedApr 1, 2016
LP: 1564181