While we're at it, can we maybe not have #== execute queries as a side effect please?
Show this thread
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.
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
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"
- 2 more replies
New conversation -
-
-
I agree,we should test if the action generated the correct outcome, not how did it achieved that outcome.
-
Agree with
@sgrif original point. However, there are cases to test inner workings. Flight path analogy. Which path I flew to alaska matters. Not just that I flew there. But then different test intentions and diff test scenarios. - 1 more reply
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.