cypress-on-rails 1.10.1 → 1.15.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 19c6280b01cef6fe5088f9a3d1098acf69a116f6118e219992f961f7af7f1a6d
-  data.tar.gz: 8408f84cf6d400a87136243c34c49ed228ccde27f14e824aa88d053bf435ad78
+  metadata.gz: 9cb0dd8412c42d59d5c687cd911a1a41819296f0fd8c8796e58365620be94897
+  data.tar.gz: 0baeb4e448a0f7e069f0774caadb0829f6ecd710f38ef06942674c2114cd9244
 SHA512:
-  metadata.gz: d72faf8adc3ed46442e0bcd91b5420d3dda942192ba014f4ce435284448e06a44de95f72c5d5a007357902eab0d64a7f4965da839c966243997a56ebcecab3e9
-  data.tar.gz: 25e8fad0237b6e3f0a891a4d202273257210e42a0056db6026a70a3cbc0c6851a3763e7c2e70016ab76ec3efc7586d786741e271cd0855d52741e6387d6064ed
+  metadata.gz: 2836bd208f1cb49b4ad0e25c2bd20cfe6b7fcaaac97fa739e7dc10516fb291b0a220a6bab3678f05329c104bf0f596fb4ec8e9fb2f2d28fade4d59299e1c7169
+  data.tar.gz: 783e8a833f7dd2e386b7fa0b245c1ce9c039835a1600e511148f0cb76a584819f5a1a9af88d1681bbd86a8dfefa4a43a389ea871dce18a30224791f0b6e7cd2f

data/.github/workflows/ruby.yml

@@ -0,0 +1,63 @@
+name: Ruby
+
+on:
+  push:
+    branches: [ master ]
+  pull_request:
+    branches: [ master ]
+
+jobs:
+  rails_3_2:
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v2
+    - name: Set up Ruby
+      uses: ruby/setup-ruby@v1
+      with:
+        ruby-version: 2.3
+        bundler-cache: true
+    - name: Run tests
+      run: bundle exec rake
+    - run: gem uninstall -v '>= 2' -ax bundler || true
+    - run: gem install bundler -v '< 2'
+    - name: Run interaction tests
+      run: ./specs_e2e/rails_3_2/test.sh
+      env:
+        CYPRESS_RECORD_KEY: ${{ secrets.CYPRESS_RECORD_KEY }}
+
+  rails_4_2:
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v2
+    - name: Set up Ruby
+      uses: ruby/setup-ruby@v1
+      with:
+        ruby-version: 2.5
+        bundler-cache: true
+    - name: Run tests
+      run: bundle exec rake
+    - run: gem uninstall -v '>= 2' -ax bundler || true
+    - run: gem install bundler -v '< 2'
+    - name: Run interaction tests
+      run: ./specs_e2e/rails_4_2/test.sh
+      env:
+        CYPRESS_RECORD_KEY: ${{ secrets.CYPRESS_RECORD_KEY }}
+
+  rails_5_2:
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v2
+    - name: Set up Ruby
+      uses: ruby/setup-ruby@v1
+      with:
+        ruby-version: 2.6
+        bundler-cache: true
+    - name: Run tests
+      run: bundle exec rake
+    - name: Run interaction tests
+      run: ./specs_e2e/rails_5_2/test.sh
+      env:
+        CYPRESS_RECORD_KEY: ${{ secrets.CYPRESS_RECORD_KEY }}

data/.gitignore

@@ -5,4 +5,8 @@ spec/examples.txt
 .idea
 spec/test.log
 pkg/*.gem
-vendor/bundle
+vendor/bundle
+.vscode
+node_modules
+package-lock.json
+yarn.lock

data/CHANGELOG.md

@@ -1,5 +1,68 @@
-## [1.10.0]
-[Compare]: https://github.com/shakacode/cypress-on-rails/compare/v1.9.1...v1.10.0
+## [1.15.1]
+[Compare]: https://github.com/shakacode/cypress-on-rails/compare/v1.15.0...v1.15.1
+
+### Fixed
+* fix cypress_folder deprecation warning by internal code [PR 136](https://github.com/shakacode/cypress-on-rails/pull/136)
+
+## [1.15.0]
+[Compare]: https://github.com/shakacode/cypress-on-rails/compare/v1.14.0...v1.15.0
+
+### Changed
+* Add support for any e2e testing framewrok starting with Playwright [PR 131](https://github.com/shakacode/cypress-on-rails/pull/131) by [KhaledEmaraDev]
+
+## [1.14.0]
+[Compare]: https://github.com/shakacode/cypress-on-rails/compare/v1.13.1...v1.14.0
+
+### Changed
+* Add support for proxy routes through `api_prefix` [PR 130](https://github.com/shakacode/cypress-on-rails/pull/130) by [RomainEndelin]
+
+### Fixed
+* Properly copies the cypress_helper file when running the update generator [PR 117](https://github.com/shakacode/cypress-on-rails/pull/117) by [alvincrespo]
+
+### Tasks
+* pass cypress record key to github action [PR 110](https://github.com/shakacode/cypress-on-rails/pull/110)
+
+## [1.13.1]
+[Compare]: https://github.com/shakacode/cypress-on-rails/compare/v1.13.0...v1.13.1
+
+### Fixed
+* use_vcr_middleware disabled by default [PR 109](https://github.com/shakacode/cypress-on-rails/pull/109)
+
+## [1.13.0]
+[Compare]: https://github.com/shakacode/cypress-on-rails/compare/v1.12.1...v1.13.0
+
+### Changed
+* Add support for matching npm package and VCR
+* generate for cypress 10 [PR 108](https://github.com/shakacode/cypress-on-rails/pull/108)
+
+## [1.12.1]
+[Compare]: https://github.com/shakacode/cypress-on-rails/compare/v1.12.0...v1.12.1
+
+### Tasks
+* Documenting how to setup Factory Associations [PR 100](https://github.com/shakacode/cypress-on-rails/pull/100)
+
+### Fixed
+* keep track of factory manual reloads to prevent auto_reload from reloading again [PR 98](https://github.com/shakacode/cypress-on-rails/pull/98)
+
+## [1.12.0]
+[Compare]: https://github.com/shakacode/cypress-on-rails/compare/v1.11.0...v1.12.0
+
+### Changed
+* only reload factories on clean instead of every factory create request [PR 95](https://github.com/shakacode/cypress-on-rails/pull/95)
+* alternative command added for get tail of logs [PR 89](https://github.com/shakacode/cypress-on-rails/pull/89) by [ccrockett]
+
+### Tasks
+* switch from travis to github actions [PR 96]
+
+## [1.11.0]
+[Compare]: https://github.com/shakacode/cypress-on-rails/compare/v1.10.1...v1.11.0
+
+### Changed
+* improve app command logging on cypress
+* Allow build and build_list commands to be executed against factory bot [PR 87](https://github.com/shakacode/cypress-on-rails/pull/87) by [Alexander-Blair]
+
+## [1.10.1]
+[Compare]: https://github.com/shakacode/cypress-on-rails/compare/v1.9.1...v1.10.1
 
 ### Changed
 * improve error message received from failed command

data/README.md

@@ -1,24 +1,34 @@
 # CypressOnRails
 
-[![Build Status](https://travis-ci.com/shakacode/cypress-on-rails.svg?branch=master)](https://travis-ci.org/shakacode/cypress-on-rails) [![Gem Version](https://badge.fury.io/rb/cypress-on-rails.svg)](https://badge.fury.io/rb/cypress-on-rails)
+![Build Status](https://github.com/shakacode/cypress-on-rails/actions/workflows/ruby.yml/badge.svg)
+[![cypress-on-rails](https://img.shields.io/endpoint?url=https://dashboard.cypress.io/badge/simple/2b6cjr/master&style=plastic&logo=cypress)](https://dashboard.cypress.io/projects/2b6cjr/runs)
+[![Gem Version](https://badge.fury.io/rb/cypress-on-rails.svg)](https://badge.fury.io/rb/cypress-on-rails)
 
 ----
 
-This project is sponsored by the software consulting firm [ShakaCode](https://www.shakacode.com), creator of the [React on Rails Gem](https://github.com/shakacode/react_on_rails). We focus on React front-ends, often with Ruby on Rails or Gatsby. The best way to see what we do is to see the details of [our recent work](https://www.shakacode.com/recent-work). Feel free to engage in discussions around this gem at our [forum category for Cypress](https://forum.shakacode.com/c/cypress-on-rails/55).
+This project is sponsored by the software consulting firm [ShakaCode](https://www.shakacode.com), creator of the [React on Rails Gem](https://github.com/shakacode/react_on_rails). We focus on React (with TS or ReScript) front-ends, often with Ruby on Rails or Gatsby. See [our recent work](https://www.shakacode.com/recent-work) and [client engagement model](https://www.shakacode.com/blog/client-engagement-model/). Feel free to engage in discussions around this gem at our [Slack Channel](https://join.slack.com/t/reactrails/shared_invite/enQtNjY3NTczMjczNzYxLTlmYjdiZmY3MTVlMzU2YWE0OWM0MzNiZDI0MzdkZGFiZTFkYTFkOGVjODBmOWEyYWQ3MzA2NGE1YWJjNmVlMGE) or our [forum category for Cypress](https://forum.shakacode.com/c/cypress-on-rails/55).
+
+Interested in joining a small team that loves open source? Check our [careers page](https://www.shakacode.com/career/).
+
+Need help with cypress-on-rails? Contact [ShakaCode](mailto:justin@shakacode.com).
 
 ----
 
 # Totally new to Cypress?
 Suggest you first learn the basics of Cypress before attempting to integrate with Ruby on Rails
 
-* [Good start Here](https://docs.cypress.io/examples/examples/tutorials.html#Best-Practices)
+* [Good start Here](https://docs.cypress.io/examples/tutorials.html#Best-Practices)
+
+# Totally new to Playwright?
+Suggest you first learn the basics of Playwright before attempting to integrate with Ruby on Rails
+
+* [Good start Here](https://playwright.dev/docs/writing-tests)
 
 ## Overview
 
-Gem for using [cypress.io](http://github.com/cypress-io/) in Rails and ruby rack applications
-with the goal of controlling State as mentioned in [Cypress Best Practices](https://docs.cypress.io/guides/references/best-practices.html#Organizing-Tests-Logging-In-Controlling-State)
+Gem for using [cypress.io](http://github.com/cypress-io/) or [playwright.dev](https://playwright.dev/) in Rails and Ruby Rack applications with the goal of controlling state as mentioned in [Cypress Best Practices](https://docs.cypress.io/guides/references/best-practices.html#Organizing-Tests-Logging-In-Controlling-State)
 
-It allows to run code in the application context when executing cypress tests.
+It allows you to run code in the application context when executing cypress or playwright tests.
 Do things like:
 * use database_cleaner before each test
 * seed the database with default data for each test
@@ -37,7 +47,7 @@ Has examples of setting up state with:
 
 ## Installation
 
-Add this to your Gemfile:
+Add this to your `Gemfile`:
 
 ```ruby
 group :test, :development do
@@ -48,11 +58,21 @@ end
 Generate the boilerplate code using:
 
 ```shell
+# by default installs only cypress
 bin/rails g cypress_on_rails:install
 
 # if you have/want a different cypress folder (default is cypress)
 bin/rails g cypress_on_rails:install --cypress_folder=spec/cypress
 
+# to install both cypress and playwright
+bin/rails g cypress_on_rails:install --install_cypress --install_playwright --playwright_folder=playwright
+
+# to change where the Ruby files reside (default is e2e)
+bin/rails g cypress_on_rails:install --install_folder=test/e2e
+
+# if you target the Rails server with a path prefix to your URL
+bin/rails g cypress_on_rails:install --api_prefix=/api
+
 # if you want to install cypress with npm
 bin/rails g cypress_on_rails:install --install_cypress_with=npm
 
@@ -64,27 +84,27 @@ bin/rails g cypress_on_rails:update
 ```
 
 The generator modifies/adds the following files/directory in your application:
-* `config/environments/test.rb`
-* `config/initializers/cypress_on_rails` used to configure CypressDev
-* `spec/cypress/integrations/` contains your cypress tests
-* `spec/cypress/support/on-rails.js` contains CypressDev support code
-* `spec/cypress/app_commands/scenarios/` contains your CypressDev scenario definitions
-* `spec/cypress/cypress_helper.rb` contains helper code for CypressDev app commands
+* `config/initializers/cypress_on_rails.rb` used to configure Cypress on Rails
+* `spec/cypress/e2e/` contains your cypress tests
+* `spec/playwright/e2e/` contains your playwright tests
+* `spec/cypress/support/on-rails.js` contains Cypress on Rails support code
+* `spec/playwright/support/on-rails.js` contains Playwright on Rails support code
+* `spec/e2e/app_commands/scenarios/` contains your Cypress on Rails scenario definitions
+* `spec/e2e/cypress_helper.rb` contains helper code for Cypress on Rails app commands
 
-if you are not using database_cleaner look at `spec/cypress/app_commands/clean.rb`.
-if you are not using factory_bot look at `spec/cypress/app_commands/factory_bot.rb`.
+If you are not using `database_cleaner` look at `spec/e2e/app_commands/clean.rb`.
+If you are not using `factory_bot` look at `spec/e2e/app_commands/factory_bot.rb`.
 
-Now you can create scenarios and commands that are plain ruby files that get loaded through middleware, the ruby sky is your limit.
+Now you can create scenarios and commands that are plain Ruby files that get loaded through middleware, the ruby sky is your limit.
 
 ### Update your database.yml
 
-When writing cypress test on your local it's recommended to start your server in development mode so that changes you
-make are picked up without having to restart the server. 
-It's recommend you update your database.yml to check if the CYPRESS environment variable is set and switch it to the test database
+When running `cypress test` or `playwright test` on your local computer it's recommended to start your server in development mode so that changes you
+make are picked up without having to restart the server.
+It's recommended you update your `database.yml` to check if the `CYPRESS` environment variable is set and switch it to the test database
 otherwise cypress will keep clearing your development database.
 
-for example:
-
+For example:
 ```yaml
 development:
   <<: *default
@@ -107,11 +127,15 @@ Getting started on your local environment
 CYPRESS=1 bin/rails server -p 5017
 
 # in separate window start cypress
-yarn cypress open 
+yarn cypress open
 # or for npm
-node_modules/.bin/cypress open 
+node_modules/.bin/cypress open
 # or if you changed the cypress folder to spec/cypress
 yarn cypress open --project ./spec
+# or for playwright
+yarn playwright test --ui
+# or using npm
+npx playwright test --ui
 ```
 
 How to run cypress on CI
@@ -122,28 +146,17 @@ How to run cypress on CI
 
 yarn run cypress run
 # or for npm
-node_modules/.bin/cypress run 
+npx cypress run
 ```
 
 ### Example of using factory bot
 
 You can run your [factory_bot](https://github.com/thoughtbot/factory_bot) directly as well
 
-```ruby
-# spec/cypress/app_commands/factory_bot.rb
-require 'cypress_on_rails/smart_factory_wrapper'
-
-CypressOnRails::SmartFactoryWrapper.configure(
-  always_reload: !Rails.configuration.cache_classes,
-  factory: FactoryBot,
-  files: Dir['./spec/factories/**/*.rb']
-)
-```
-
 ```js
-// spec/cypress/integrations/simple_spec.js
-describe('My First Test', function() {
-  it('visit root', function() {
+// spec/cypress/e2e/simple.cy.js
+describe('My First Test', () => {
+  it('visit root', () => {
     // This calls to the backend to prepare the application state
     cy.appFactories([
       ['create_list', 'post', 10],
@@ -154,7 +167,7 @@ describe('My First Test', function() {
     // Visit the application under test
     cy.visit('/')
 
-    cy.contains("Hello World")
+    cy.contains('Hello World')
 
     // Accessing result
     cy.appFactories([['create', 'invoice', { paid: false }]]).then((records) => {
@@ -163,10 +176,47 @@ describe('My First Test', function() {
   })
 })
 ```
+You can check the [association docs](docs/factory_bot_associations.md) on more ways to setup association with the correct data.
+
+In some cases, using static Cypress fixtures may not provide sufficient flexibility when mocking HTTP response bodies. It's possible to use `FactoryBot.build` to generate Ruby hashes that can then be used as mock JSON responses:
+```ruby
+FactoryBot.define do
+  factory :some_web_response, class: Hash do
+    initialize_with { attributes.deep_stringify_keys }
+
+    id { 123 }
+    name { 'Mr Blobby' }
+    occupation { 'Evil pink clown' }
+  end
+end
+
+FactoryBot.build(:some_web_response => { 'id' => 123, 'name' => 'Mr Blobby', 'occupation' => 'Evil pink clown' })
+```
+
+This can then be combined with Cypress mocks:
+```js
+describe('My First Test', () => {
+  it('visit root', () => {
+    // This calls to the backend to generate the mocked response
+    cy.appFactories([
+      ['build', 'some_web_response', { name: 'Baby Blobby' }]
+    ]).then(([responseBody]) => {
+      cy.intercept('http://some-external-url.com/endpoint', {
+        body: responseBody
+      });
+
+      // Visit the application under test
+      cy.visit('/')
+    })
+
+    cy.contains('Hello World')
+  })
+})
+```
 
-### Example of loading rails test fixtures
+### Example of loading Rails test fixtures
 ```ruby
-# spec/cypress/app_commands/activerecord_fixtures.rb
+# spec/e2e/app_commands/activerecord_fixtures.rb
 require "active_record/fixtures"
 
 fixtures_dir = ActiveRecord::Tasks::DatabaseTasks.fixtures_path
@@ -178,16 +228,16 @@ ActiveRecord::FixtureSet.create_fixtures(fixtures_dir, fixture_files)
 ```
 
 ```js
-// spec/cypress/integrations/simple_spec.js
-describe('My First Test', function() {
-  it('visit root', function() {
+// spec/cypress/e2e/simple.cy.js
+describe('My First Test', () => {
+  it('visit root', () => {
     // This calls to the backend to prepare the application state
     cy.appFixtures()
 
     // Visit the application under test
     cy.visit('/')
 
-    cy.contains("Hello World")
+    cy.contains('Hello World')
   })
 })
 ```
@@ -196,7 +246,7 @@ describe('My First Test', function() {
 
 Scenarios are named `before` blocks that you can reference in your test.
 
-You define a scenario in the `spec/cypress/app_commands/scenarios` directory:
+You define a scenario in the `spec/e2e/app_commands/scenarios` directory:
 ```ruby
 # spec/cypress/app_commands/scenarios/basic.rb
 Profile.create name: "Cypress Hill"
@@ -207,34 +257,34 @@ CypressOnRails::SmartFactoryWrapper.create(:profile, name: "Cypress Hill")
 
 Then reference the scenario in your test:
 ```js
-// spec/cypress/integrations/scenario_example_spec.js
-describe('My First Test', function() {
-  it('visit root', function() {
+// spec/cypress/e2e/scenario_example.cy.js
+describe('My First Test', () => {
+  it('visit root', () => {
     // This calls to the backend to prepare the application state
     cy.appScenario('basic')
 
     cy.visit('/profiles')
 
-    cy.contains("Cypress Hill")
+    cy.contains('Cypress Hill')
   })
 })
 ```
 
 ### Example of using app commands
 
-create a ruby file in `spec/cypress/app_commands` directory:
+Create a Ruby file in the `spec/e2e/app_commands` directory:
 ```ruby
-# spec/cypress/app_commands/load_seed.rb
+# spec/e2e/app_commands/load_seed.rb
 load "#{Rails.root}/db/seeds.rb"
 ```
 
 Then reference the command in your test with `cy.app('load_seed')`:
 ```js
-// spec/cypress/integrations/simple_spec.js
-describe('My First Test', function() {
+// spec/cypress/e2e/simple.cy.js
+describe('My First Test', () => {
   beforeEach(() => { cy.app('load_seed') })
 
-  it('visit root', function() {
+  it('visit root', () => {
     cy.visit('/')
 
     cy.contains("Seeds")
@@ -242,6 +292,109 @@ describe('My First Test', function() {
 })
 ```
 
+### Example of using scenario with Playwright
+
+Scenarios are named `before` blocks that you can reference in your test.
+
+You define a scenario in the `spec/e2e/app_commands/scenarios` directory:
+```ruby
+# spec/e2e/app_commands/scenarios/basic.rb
+Profile.create name: "Cypress Hill"
+
+# or if you have factory_bot enabled in your cypress_helper
+CypressOnRails::SmartFactoryWrapper.create(:profile, name: "Cypress Hill")
+```
+
+Then reference the scenario in your test:
+```js
+// spec/playwright/e2e/scenario_example.spec.js
+import { test, expect } from "@playwright/test";
+import { app, appScenario } from '../../support/on-rails';
+
+test.describe("Rails using scenarios examples", () => {
+  test.beforeEach(async ({ page }) => {
+    await app('clean');
+  });
+
+  test("setup basic scenario", async ({ page }) => {
+    await appScenario('basic');
+    await page.goto("/");
+  });
+});
+```
+
+## Experimental Features (matching npm package)
+
+Please test and give feedback.
+
+Add the npm package:
+
+```
+yarn add cypress-on-rails --dev
+```
+
+### for VCR
+
+This only works when you start the Rails server with a single worker and single thread
+
+#### setup
+
+Add your VCR configuration to your `cypress_helper.rb`
+
+```ruby
+require 'vcr'
+VCR.configure do |config|
+  config.hook_into :webmock
+end
+```
+
+Add to your `cypress/support/index.js`:
+
+```js
+import 'cypress-on-rails/support/index'
+```
+
+Add to your `cypress/app_commands/clean.rb`:
+
+```ruby
+VCR.eject_cassette # make sure we no cassettes inserted before the next test starts
+VCR.turn_off!
+WebMock.disable! if defined?(WebMock)
+```
+
+Add to your `config/cypress_on_rails.rb`:
+
+```ruby
+  c.use_vcr_middleware = !Rails.env.production? && ENV['CYPRESS'].present?
+```
+
+#### usage
+
+You have `vcr_insert_cassette` and `vcr_eject_cassette` available. https://www.rubydoc.info/github/vcr/vcr/VCR:insert_cassette
+
+
+```js
+describe('My First Test', () => {
+  beforeEach(() => { cy.app('load_seed') })
+
+  it('visit root', () => {
+    cy.app('clean') // have a look at e2e/app_commands/clean.rb
+
+    cy.vcr_insert_cassette('cats', { record: "new_episodes" })
+    cy.visit('/using_vcr/index')
+
+    cy.get('a').contains('Cats').click()
+    cy.contains('Wikipedia has a recording of a cat meowing, because why not?')
+
+    cy.vcr_eject_cassette()
+
+    cy.vcr_insert_cassette('cats')
+    cy.visit('/using_vcr/record_cats')
+    cy.contains('Wikipedia has a recording of a cat meowing, because why not?')
+  })
+})
+```
+
 ## Usage with other rack applications
 
 Add CypressOnRails to your config.ru
@@ -259,30 +412,30 @@ use CypressOnRails::Middleware
 run MyApp
 ```
 
-add the following file to cypress
+add the following file to Cypress
 
 ```js
 // test/cypress/support/on-rails.js
-// CypressOnRails: dont remove these command
-Cypress.Commands.add('appCommands', function (body) {
+// CypressOnRails: don't remove these commands
+Cypress.Commands.add('appCommands', (body) => {
   cy.request({
     method: 'POST',
-    url: "/__cypress__/command",
+    url: '/__cypress__/command',
     body: JSON.stringify(body),
     log: true,
     failOnStatusCode: true
   })
 });
 
-Cypress.Commands.add('app', function (name, command_options) {
+Cypress.Commands.add('app', (name, command_options) => {
   cy.appCommands({name: name, options: command_options})
 });
 
-Cypress.Commands.add('appScenario', function (name) {
+Cypress.Commands.add('appScenario', (name) => {
   cy.app('scenarios/' + name)
 });
 
-Cypress.Commands.add('appFactories', function (options) {
+Cypress.Commands.add('appFactories', (options) => {
   cy.app('factory_bot', options)
 });
 // CypressOnRails: end
@@ -293,6 +446,17 @@ beforeEach(() => {
 });
 ```
 
+## API Prefix
+
+If your Rails server is exposed under a proxy, typically https://my-local.dev/api, you can use the `api_prefix` option.
+In `config/initializers/cypress_on_rails.rb`, add this line:
+```ruby
+  CypressOnRails.configure do |c|
+    # ...
+    c.api_prefix = '/api'
+  end
+```
+
 ## Contributing
 
 1. Fork it ( https://github.com/shakacode/cypress-on-rails/fork )
@@ -300,3 +464,38 @@ beforeEach(() => {
 3. Commit your changes (`git commit -am 'Add some feature'`)
 4. Push to the branch (`git push origin my-new-feature`)
 5. Create a new Pull Request
+
+## Supporters
+
+<a href="https://www.jetbrains.com">
+  <img src="https://user-images.githubusercontent.com/4244251/184881139-42e4076b-024b-4b30-8c60-c3cd0e758c0a.png" alt="JetBrains" height="120px">
+</a>
+<a href="https://scoutapp.com">
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="https://user-images.githubusercontent.com/4244251/184881147-0d077438-3978-40da-ace9-4f650d2efe2e.png">
+    <source media="(prefers-color-scheme: light)" srcset="https://user-images.githubusercontent.com/4244251/184881152-9f2d8fba-88ac-4ba6-873b-22387f8711c5.png">
+    <img alt="ScoutAPM" src="https://user-images.githubusercontent.com/4244251/184881152-9f2d8fba-88ac-4ba6-873b-22387f8711c5.png" height="120px">
+  </picture>
+</a>
+<br />
+<a href="https://www.browserstack.com">
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="https://user-images.githubusercontent.com/4244251/184881122-407dcc29-df78-4b20-a9ad-f597b56f6cdb.png">
+    <source media="(prefers-color-scheme: light)" srcset="https://user-images.githubusercontent.com/4244251/184881129-e1edf4b7-3ae1-4ea8-9e6d-3595cf01609e.png">
+    <img alt="BrowserStack" src="https://user-images.githubusercontent.com/4244251/184881129-e1edf4b7-3ae1-4ea8-9e6d-3595cf01609e.png" height="55px">
+  </picture>
+</a>
+<a href="https://railsautoscale.com">
+  <img src="https://user-images.githubusercontent.com/4244251/184881144-95c2c25c-9879-4069-864d-4e67d6ed39d2.png" alt="Rails Autoscale" height="55px">
+</a>
+<a href="https://www.honeybadger.io">
+  <img src="https://user-images.githubusercontent.com/4244251/184881133-79ee9c3c-8165-4852-958e-31687b9536f4.png" alt="Honeybadger" height="55px">
+</a>
+<a href="https://reviewable.io">
+  <img src="https://user-images.githubusercontent.com/20628911/230848305-c94510a4-82d7-468f-bf9f-eeb81d3f2ce0.png" alt="Reviewable" height="55px">
+</a>
+
+<br />
+<br />
+
+The following companies support our open source projects, and ShakaCode uses their products!

data/cypress-on-rails.gemspec

@@ -20,6 +20,7 @@ Gem::Specification.new do |s|
   s.add_development_dependency 'rspec'
   s.add_development_dependency 'railties', '>= 3.2'
   s.add_development_dependency 'factory_bot'
+  s.add_development_dependency 'vcr'
   s.metadata = {
     "bug_tracker_uri"   => "https://github.com/shakacode/cypress-on-rails/issues",
     "changelog_uri"     => "https://github.com/shakacode/cypress-on-rails/blob/master/CHANGELOG.md",