@sgrif Trying to use system tests with an app that was upgraded to 5.1, but mutated records are still mutated in subsequent tests. Any idea?
-
-
Replying to @brandonhilkert
Are you doing anything funky to transactions? You're not trying to use database_cleaner or anything, right?
1 reply 0 retweets 0 likes -
Replying to @sgrif
Nope, just stock Rails. Introducing js testing for the first time. looked at load_defaults, but it appears I have latest config.
1 reply 0 retweets 0 likes -
-
Replying to @sgrif
Not at the moment. Didn't quite go down that path b/c figured I was missing something obvious.
1 reply 0 retweets 0 likes -
Replying to @brandonhilkert
That would be my guess, but I can't tell you what it is without code
1 reply 0 retweets 0 likes -
Replying to @sgrif
Should i expect system tests to log to logs/test.log, or is this a totally separate thing?
1 reply 1 retweet 0 likes -
Replying to @brandonhilkert
I would expect them to log to the same place but TBH I don't know off the top of my head
1 reply 0 retweets 0 likes -
Replying to @sgrif
Looks like a new app behaves normally. The object_id of current_transaction shows the same ID in every view template in diff. test. Weird?
2 replies 0 retweets 0 likes
I suspect something is messing w/ transaction state in a way we didn't anticipate.
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.