Explore the possibility for using Watir for QA
Last time @meks mentioned Watir as an alternative to Capybara, and I took some time looking around, and it looks good to me. The points mentioned in What are known reasons to use watir not capybara? convinced me that Watir is better designed.
@gl-quality What do you think about Watir? Would we want to explore the possibility using it?
The other thing I think nice about Watir is that it seems to be closer to Selenium, thus less magic. In https://gitlab.com/gitlab-org/gitlab-ce/issues/46074 we're discussing about Capybara's default_max_wait_time
and it feels like implicit wait, but it's actually using explicit wait in Selenium, while there's a page talking about implicit wait vs explicit wait in Watir: Selenium Waits - Implicit & Explicit
Another case is tweaking Selenium configuration. At https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/17662#note_64086197 we could see that it's not that easy to configure the underlying Selenium HTTP timeout (I spent quite some time figuring that out), while it's very simple to do in Watir: How do I change the page load Timeouts in Watir-Webdriver. Of course, this is probably the same point that DSL vs objects.