Refactor beastrun tests?

[lmaurits]

Refactor beastrun tests?

[xrotwang]

This is already the case now. Using pytest.mark.parametrize will essentially turn each call of the actual test function into a separate test, and report the arguments passed into the test function:

============================================== FAILURES ==============================================
_________________________________ test_beastrun[configs100-<lambda>] _________________________________

configs = ('admin', 'covarion_multistate', 'ancestral_state_reconstruction', 'ascertainment_false')
assertion = <function <lambda> at 0x7fce8fc44f28>
config_factory = <function config_factory.<locals>.make_cfg at 0x7fce8fc43f28>
tmppath = PosixPath('/tmp/[email protected]/pytest-64/test_beastrun_configs100__lamb0')

...

[xrotwang]

What I did locally - but can push as well - is copying the XML to cwd. This could be cleaned up after successfully passing the test - so whatever is leftover is the XML of the last failure.

[lmaurits]

Ah, okay, I do see that now! Easily missed amongst the screens of screens output, including long code listings, that pytest gives me right now. But I guess I can put things in setup.cfg to control how verbose it is...

That XML in cwd thing sounds pretty handy!

[xrotwang]

What I also did was not calling validate_ids right at the end of build_xml, but "manually", in beastrun_tests, after writing and copying the XML.

[xrotwang]

can be closed, I guess?

[lmaurits]

Yep, thanks.