Robert Fletcher

Okay, we'll give that a try. We're not actually calling `Capybara.string` directly, but using them implicitly in view specs like: ```rb expect(rendered).to have_text("Thanks, Sonya Signer") ``` I guess we'll have...

@twalpole is there an alternative that is forward compatible with Capybara 4.x? Or do we just need to kill our view specs?

> The real question is how to implement any Capybara::Simple changes now without breaking any tests that depend on the current behavior. Well, being that we're the only people on...

@trystant let me know if you'd like to pair on this. Happy to do a screen share.

@mnyon-grandkru sure, my schedule is pretty flexible right now. I could do 2:30pm PST any day this week. If that doesn't work, you can hit me up on the Rails...

@trystant @rlgreen91 what do you think about integrating auto-upgrades? You're probably familiar with Dependabot, but I prefer Depfu. One major benefit of Depfu is that they batch updates instead of...

> As soon as you have one test that needs to retain state What sort of state do you need to retain between tests? If anything, this seems like an...

@Watson1978 I think it's probably fine to remove this, though maybe we should have a deprecation cycle first? Instead of removing it, we can add a deprecation warning first and...

This would be great! We end up adding it manually to all of our icons.

[I commented over in #56][1], but I would actually advocate for more strongly saying that `before`, `let`, and friends should be avoided. Saying "use when it makes sense" adds some...