Crashtests are a very low proportion of our overall automation burden. We
also gain something from running a "tricky situation" in as many different
configurations (opt and debug) as possible, since we may catch bugs other
than the one we had in mind when writing the crashtest.
So I think we shoul
It seems we generally add crashtests even for softening assertions to
non-crash ones. I suggest that we mark those kind of crashtests debug build
only, so that testing machines don't need to waste time on testing them on
release build where they never crash.
I'm not sure how many crashtests are si
2 matches
Mail list logo
