Windows/WSL day 2. I didn't expect this to work, for exactly this reason; but OMG it would have been great if it just didpic.twitter.com/mD4Yos1iLS
Show this thread
-
I think it's time to retire capybara-webkit - given its QT dependency it's something that generally causes problems everywhere, not just WSL. Consider something like Cuprite :)
Yes, we're actively moving off of it (which I am leading the charge on). Unfortunately for us it's not as simple as just switching to headless chrome, it'll take a few weeks
-
-
Good luck! I'd love to hear more about it when it's done :)
-
Unlikely to write about it, it's not particularly interesting. Our test suite relies on a lot of bugs (mostly around visibility). Updating browser and capybara exposes those. Root cause is mostly an element-centric testing style. Fix is moving to user-centric
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.