How to use assert_type method of Selenium.WebDriver.Interactions Package

You can use the rake gem, for this you need to create a file named rakefile.rb, and paste the below content:

task :default do
    FileList['file*.rb'].each { |file| ruby file }
end

Now call rake in your terminal, you should be good.

Changing a webrat step from

When /^I press "([^\"]*)"$/ do |button|
  click_button(button)
end

to

When /^I press "([^\"]*)"$/ do |button|
  click_button(button)
  selenium.wait_for_page_to_load
end

it works. Telling selenium to wait fixes!

Capybara is designed to emulate a user so you can't click on a non-visible element because a user couldn't. You should, however, be able to replicate a users actions to make the element visible and then click it

find('#button_div').hover
find('#icon').click

if that doesn't raise an error but also doesn't appear to click the button try putting a short sleep between the two actions since you may have an animated appearance which can cause clicks to miss items

Instead of using the services + docker, I decided to use docker-compose. The file that did the trick:

version: "3.7"

services:
  db:
    image: postgres:14.4
    ports:
      - 5432:5432
    env_file:
      - ./.docker/env_files/.env
    healthcheck:
      test: ["CMD-SHELL", "pg_isready"]
      interval: 10s
      timeout: 5s
      retries: 5
    volumes:
      - ./.docker/volumes/postgres_data:/var/lib/postgresql/data

  web:
    image: test
    env_file:
      - ./.docker/env_files/.env
    build:
      context: .
    depends_on:
      db:
        condition: service_healthy
    links:
      - db
    ports:
      - 3000:3000
    volumes:
      - .:/opt/test:cached
    stdin_open: true
    tty: true

  livereload:
    image: test
    depends_on:
      - web
    ports:
      - 35729:35729
    command: ["bundle", "exec", "guard", "-i"]
    env_file:
      - ./.docker/env_files/.env
    volumes:
      - .:/opt/test:cached

  tailwindcsswatcher:
    image: test
    depends_on:
      - web
    ports:
      - 3035:3035
    command: ["bin/rails", "tailwindcss:watch"]
    env_file:
      - ./.docker/env_files/.env
    volumes:
      - .:/opt/test:cached
    tty: true

  selenium:
    image: selenium/standalone-chrome:3.141.59
    ports:
      - 4444:4444

volumes:
  postgres_data:

Now the ci.yml using the docker-compose:

name: CI
on: push
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      -
        name: Check out repository code
        uses: actions/checkout@v3
      -
        name: 'Create docker-compose file'
        run: cp .docker/docker-compose.dev.yml docker-compose.yml
      -
        name: 'Create env file'
        run: cp .docker/env_files/.env.dev .docker/env_files/.env
      -
        name: Build web container
        run: docker-compose build web selenium
      -
        name: 'Create database'
        run: docker-compose run --rm web bin/rails db:create db:migrate
      -
        name: 'Start container'
        run: docker-compose up -d web selenium
      -
        name: 'Run unit tests'
        run: docker-compose exec -T web bin/rails test
      -
        name: 'Run system tests'
        run: docker-compose exec -T web bin/rails test:system

The Ruby selenium-webdriver API doesn't expose a separate Chrome options object like Java/Python but you can set the options via "Capabilities".

The Capabilities web page provides a Ruby example and the table of recognized capabilities that you can inject. Plugging those together with excludeSwitches:

caps = Selenium::WebDriver::Remote::Capabilities.chrome("chromeOptions" => {"excludeSwitches" => [ "--ignore-certificate-errors" ]})
driver = Selenium::WebDriver.for :chrome, desired_capabilities: caps

Take a look at Watir too, it's a front end for WebDriver.
Their examples show how you can send a :switches array which is passed straight through to the web driver so you can do the same. That makes adding other switches a bit easier rather than going through capabilities.

There is a chromedriver issue on the topic as well. There are posts detailing that you can add a --test-type argument to work around the certificate issue and ruby code examples like above.

This is a selenium error and you are getting it whether because your webdriver times out before reaching the element or because you have denoted the wrong selector (i.e --> you are getting error element not found). If I was you I will use xpath as the selector as it seems to be the most reliable locator out there. Let's take for example Google's search box as an element. You have the following html code for the box:

<input type="text" name="q" value="" id="searchText" maxlength="256"/>

The way you will form your selenium element locator using the html code above will be like this..:

driver.find_element(:xpath, "//input[@name='q']")

However this is not enough as I've noticed in your description above; you've tried setting the implicit wait. A better way of achieving the effect you want is this..

!30.times { if (driver.find_element(:xpath, "//input[@name='q']") rescue false) then break else sleep 1; end }

The code above will try 30 times, waiting 1 sec before each attempt to reach the desired element (if it fails you can capture the error by using begin/rescue clause as such:

begin
   .    
   .
 [your code]
   .
   .
!30.times { if (driver.find_element(:xpath, "//input[@name='q']") rescue false) then break else sleep 1; end }    
   .
   .
driver.find_element(:xpath, "//input[@name='q']") #so you cause an error that u can capture
   .
   .
rescue    
puts "A time-out error occurred or you have used an invalid element locator"
   .
   .
end

Hope that helps!

I figured it out. The trick was to download the certificate to the site, and save it somewhere, then go back into Firefox settings (with the Selenium Profile loaded), and manually upload the certificate, then "Edit Trust" to trust the certificate.

This worked for me :

   @profile=Selenium::WebDriver::Firefox::Profile.from_name "default"
   @profile.assume_untrusted_certificate_issuer=false
   @profile.secure_ssl = true 
   browser = Watir::Browser.new :firefox, :profile => @profile

Can you try something like this?

selenium.getEval("selenium.browserbot.isNewPageLoaded()");