There are a couple of failing tests on Windows, neither is critical. First is due to apparent blank lines between each output line in the command line interface test_cmd_line_interface(tmpdir). Probably related to \n\r vs \n?
Second is trivial:
def test_get_continuity_fail():
with pytest.raises(ValueError) as err:
states.get_continuity('2017:014', 'letg', lookbacks=[3])
> assert 'did not find transitions' in str(err)
E AssertionError: assert 'did not find transitions' in '<ExceptionInfo ValueError tblen=2>'
E + where '<ExceptionInfo ValueError tblen=2>' = str(<ExceptionInfo ValueError tblen=2>)
The test should be str(err.value) not str(err). In more modern pytest the right way to write this is:
with pytest.raises(ValueError, match='did not find transitions'):
There are a couple of failing tests on Windows, neither is critical. First is due to apparent blank lines between each output line in the command line interface
test_cmd_line_interface(tmpdir)
. Probably related to\n\r
vs\n
?Second is trivial:
The test should be
str(err.value)
notstr(err)
. In more modern pytest the right way to write this is: