
7 Jun
2007
7 Jun
'07
12:58 p.m.
Benjamin Kosnik wrote:
IMHO testing release, and then debugging failures with the debug builds is the way to go. The current behavior of testing debug, and not testing release is highly suspect to me.
We've had cases in the past where a release build works while a debug build leads to an internal compiler error. Of course we also had cases where a debug build works and a release build crashes. So to be on the safe side we really need to test both. I agree that if we have to pick one, release makes more sense from a QA perspective. It's a lot slower, though.