That may be, but it ignores the fact that software was written for the express purpose of not just identifying if a test was being ran, but then taking action to change the results of the test has no real world use.  Any case where you would want to change engine performance has no reason to be triggered only when testing.  To get both included in production as-is and turned on requires quite a series of consecutive mistakes to be considered accidental.<p>&gt; In a field more of us here understand, it would be similar to coding a feature in a server that dumps user passwords to the log file in plain text.<p>No, it&#x27;s like coding that feature but explicitly making it <i>turn off</i> whenever it detects a security review.  How is that justifiable?