blampe/Testify — comment on commit 846e32bd4d64b5c92f6afeacd03b3cf4a12e492f
File: test/test_case_test.py line 288
By EvanKrall:

You can't make the assumption that the `UnitTest` class above has already been set up and run:

$ bin/testify test.test_case_test UnitTestTestYoDawg
ERROR fail: test.test_case_test UnitTestTestYoDawg.test_unit_test_status
Traceback (most recent call last):
File "./test/test_case_test.py", line 299, in test_unit_test_status
assert UnitTest.status == [True] * 6, UnitTest.status
AssertionError: [False, False, False, False, False, False]

F
FAILED. 1 test / 1 case: 0 passed, 1 failed. (Total test time 0.00s)

It also doesn't always work when bucketing tests:

$ bin/testify test --bucket=1 --bucket-count=2
............ERROR fail: test.test_case_test UnitTestTestYoDawg.test_unit_test_status
Traceback (most recent call last):
File "./test/test_case_test.py", line 299, in test_unit_test_status
assert UnitTest.status == [True] * 6, UnitTest.status
AssertionError: [False, False, False, False, False, False]

F...........
FAILED. 24 tests / 15 cases: 23 passed, 1 failed. (Total test time 0.00s)

Or in client-server mode:

$ bin/testify test --serve 7357 & bin/testify test --connect localhost:7357 >/dev/null & bin/testify test --connect localhost:7357 >/dev/null
[4] 31961
[5] 31962
ERROR fail: test.test_case_test UnitTestTestYoDawg.test_unit_test_status
Traceback (most recent call last):
File "./test/test_case_test.py", line 299, in test_unit_test_status
assert UnitTest.status == [True] * 6, UnitTest.status
AssertionError: [False, False, False, False, False, False]

ERROR fail: test.test_case_test UnitTestTestYoDawg.test_unit_test_status
Traceback (most recent call last):
File "./test/test_case_test.py", line 299, in test_unit_test_status
assert UnitTest.status == [True] * 6, UnitTest.status
AssertionError: [False, False, False, False, False, False]

F