Have we considered not writing tests that assert every query ever made to the database, whether that query hit the cache, and what order they were executed in? Your test doesn't need to care about SELECT statements being run.
Show this thread
-
Do you mean people writing assertions specifically looking for a query to be run? Or tests that have lots of queries as byproduct/side effect?
Any test that is writing things like "assert N queries are made" or "assert this SELECT statement was made"
-
-
The former makes sense for integration tests tho
-
It really doesn't. It's just an insidiously disguised version of the latter. You're coupling yourself to details you don't want to be.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.