Suggested plan of action: Test author should add a pre-check for the resource in the test, and Assert.Inconclusive if the resource is down (and ONLY if the resource is down)."
What if the resource is down permanently, but
only from the view of the tests? Maybe someone broke the firewall rules on the build agent, or maybe your test API account expired?
You'll end up never running those tests, and you'll ignore the inconclusive results, and now you're running code in production that's never getting tested.
Maybe invent another assertion that fails on Mondays, but is inconclusive the rest of the week...? I can't come up with a good name, though.
Previous Topic
Index
