README

This is just a sandbox project used while learning ruby/rails. Do not trust this code too much...

TravisCI

Coverage

• Simplecov doesnt play well with spring

    export COVERAGE=true
    export DISABLE_SPRING=true

Notes about running system tests

• I have multiple network interfaces and the rails/selenium/proxy servers may end up not seen each other. Depending on the configuration used, the correct interface to use may not be autodetected. It is possible to force the address to use by setting a few envvars. By default, it is assumed all the services are running on localhost.

  # used by development server (rails s)
  export RAILS_WEBSERVER_HOST="10.26.0.2"
  # used by test runner (rails spec)
  export RAILS_TEST_WEBSERVER_HOST="10.26.0.3"
  # used to intercept external request while testing and mock
  # 3rd party js service api
  export RAILS_TEST_PROXY_HOST="10.26.0.4"

• stripe api will require a salt to encrypt the tested event production server are setup with Stripe generated keys, for the test environment I just set some random value so the event can be generated/decoded without issue

  export STRIPE_ENDPOINT_SECRET="abc123"

• selenium containers config in docker compose

  selenium-hub:
     image: selenium/hub:latest
     container_name: selenium-hub
     networks:
       selenium:
         aliases:
           - selenium-server
     ports:
       - 4444:4444
     environment:
       GRID_MAX_SESSION: 10
  
   selenium-chrome:
     image: selenium/node-chrome:latest
     depends_on:
       - selenium-hub
     networks:
       - selenium
     environment:
       HUB_HOST: selenium-hub
       NODE_MAX_INSTANCES: 10
       NODE_MAX_SESSION: 10
  
   selenium-chrome-standalone:
     image: selenium/standalone-chrome-debug:latest
     ports:
       - 4444:4444
       - 5900:5900
     networks:
       selenium:
         aliases:
           - selenium-server

• single container with vncserver

    export USE_SELENIUM_CONTAINERS=true
    # edit spec/support/capybara.rb => using: :chrome instead of :headless_chrome
    docker-compose up -d selenium-chrome-standalone
    vncviewer {selenium-chrome-standalone ip} &
    rails spec

• or with a workers pool

    export USE_SELENIUM_CONTAINERS=true
    docker-compose up -d selenium-hub
    docker-compose up -d --scale selenium-chrome=4 selenium-chrome
    rails parallel:spec

• or local chrome

    unset USE_SELENIUM_CONTAINERS
    # edit spec/support/capybara.rb => driven_by using: :headless_chrome or :chrome
    rails spec