Can you explain what you are fixing?
I am concerned that a "broken" test has been succeeding for so long. Do we have similar mistakes elsewhere? Is the assert_console_message utility function too forgiving?
assert_console_message
ping @julian8628
@mikem @tkopecek I'm fixing that assert_console_message was directly using sys.stdout for unittest without mocking. It will fail when some other factor like nosetests-2 tests/test_cli/test_list_tagged.py -s
sys.stdout
nosetests-2 tests/test_cli/test_list_tagged.py -s
But I didn't directly change assert_console_message, as test_list_tagged.py is the only place without mocking sys.stdout...
test_list_tagged.py
:thumbsup:
Issue #1902
Metadata Update from @tkopecek: - Pull-request tagged with: no_qe
Commit 8502d4d4 fixes this pull-request
Pull-Request has been merged by tkopecek