Hi community!
We have the surprising scenario that a unit test which is marked as disabled runs anyway when trying to merge the branch the unit test is in. The merge consequently fails.
Since it doesn’t make a difference whether the disabled unit test would actually pass or fail, we suspect that deployment manager runs the previous version of the test which is geniunely expected to fail. What is not expected is that the test is being run at all. For a test that has been set to ‘withdrawn’ this would be considered normal since the rule inside the branch will not get resolved due to this particular setting.
A unit test marked as ‘disabled’, however, should be quarantined and simply never run in any version. This has also worked in another case previously. Any ideas why this happens? Would be great to hear back from you ![]()