installing tests on top of existing test directories when the snakemake log has changed creates situations where invalid combinations of tests can be installed on top of one another. this is primarily due to snakemake's rule execution order being non-deterministic. for the most conservative behavior, it may be appropriate to recursively remove existing unit test installations by rule if --update-all is specified, or possibly if some yet-to-be-implemented flag is provided on the command line.
note that this is relatively easy for the user to intervene in, by just deleting the relevant directory; but this could be a safety feature to prevent inconsistent tests.
installing tests on top of existing test directories when the snakemake log has changed creates situations where invalid combinations of tests can be installed on top of one another. this is primarily due to snakemake's rule execution order being non-deterministic. for the most conservative behavior, it may be appropriate to recursively remove existing unit test installations by rule if
--update-allis specified, or possibly if some yet-to-be-implemented flag is provided on the command line.note that this is relatively easy for the user to intervene in, by just deleting the relevant directory; but this could be a safety feature to prevent inconsistent tests.