cuprite
cuprite copied to clipboard
rubycdp
Headless Chrome/Chromium driver for Capybara
I'm trying to migrate to cuprite. I can't find any setup for mobile testing. I have the following selenium configuration. ```ruby options = Selenium::WebDriver::Chrome::Options.new options.add_argument('--no-sandbox') options.add_argument('--headless') unless ENV['VIEW'] options.add_argument('--disable-dev-shm-usage') options.add_argument('--disable-gpu')...
When I try to do ```ruby find_link 'Buchen', exact_text: true ``` in Capybara I get ```ruby Capybara::Cuprite::InvalidSelector: Browser raised error trying to find xpath: "(.//a[./@href][((((./@id = 'Buchen') or (normalize-space(string(.)) =...
I am converting a project over from capybara selenium and found that time inputs were failing to be correctly set. This allows specifying the time as a string or a...
Capybara added support to access an element's shadow DOM with `Element#shadow_root` in https://github.com/teamcapybara/capybara/pull/2546 – it would be nice if Cuprite supported it too. Here is an attempt at that. Not...
When setting the value in an input of type number, set it the same way as a text, so that we get events(keydown, keypressed, keyup) for each "char" in the...
Since upgrading Cuprite to 0.14.3 and Ferrum to 0.13.0, we're seeing intermittent errors in our RSpec runs on Github Actions. We are not seeing errors like this locally. ```sh Failure/Error:...
I noticed the following: If you replace hidden content of a hidden parent (e.g. using `innerHTML`) and then make the parent visible, Capybara intermittently picks up the old content. I...
Here's a scenario where cuprite/ferrum does not exit and the test hangs indefinitely. We've written some concurrency/race-condition tests in our application that involves forking processes. This is resulting in our...
I'm seeing an error that pops up sometimes. Not a consistent issue, but enough to fail our builds every few days. ``` Failed to load resource: the server responded with...
Since a color input has to have its value set directly via javascript (presumably because of the difficulty of interacting with the browser's colour picker), the `change` and `input` events...
