diff --git a/Gemfile b/Gemfile index ed3b0fb6..b12ba19c 100644 --- a/Gemfile +++ b/Gemfile @@ -61,7 +61,6 @@ gem "standard_deviation" group :development, :test do # Call 'byebug' anywhere in the code to stop execution and get a debugger console gem "byebug", platform: :mri - gem "cypress-rails" gem "dotenv-rails" gem "factory_bot_rails" gem "parallel_tests" diff --git a/Gemfile.lock b/Gemfile.lock index 5a1caa97..f43cdae3 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -130,9 +130,6 @@ GEM cuprite (0.15) capybara (~> 3.0) ferrum (~> 0.14.0) - cypress-rails (0.6.1) - puma (>= 3.8.0) - railties (>= 5.2.0) database_cleaner (2.0.2) database_cleaner-active_record (>= 2, < 3) database_cleaner-active_record (2.1.0) @@ -491,7 +488,6 @@ DEPENDENCIES capybara cssbundling-rails cuprite - cypress-rails database_cleaner devise! dotenv-rails diff --git a/config/initializers/cypress_rails.rb b/config/initializers/cypress_rails.rb deleted file mode 100644 index 015ca8e4..00000000 --- a/config/initializers/cypress_rails.rb +++ /dev/null @@ -1,14 +0,0 @@ -return unless Rails.env.test? - -Rails.application.load_tasks unless defined?(Rake::Task) -CypressRails.hooks.before_server_start do - Rake::Task["db:seed"].invoke - Seeders::Journey.new.seed -end -CypressRails.hooks.after_transaction_start do -end -CypressRails.hooks.after_state_reset do -end -CypressRails.hooks.before_server_stop do - Rake::Task["db:test:prepare"].invoke -end diff --git a/cypress/example_tests/1-getting-started/todo.cy.js b/cypress/example_tests/1-getting-started/todo.cy.js deleted file mode 100644 index 7d013aac..00000000 --- a/cypress/example_tests/1-getting-started/todo.cy.js +++ /dev/null @@ -1,144 +0,0 @@ -/// - -// Welcome to Cypress! -// -// This spec file contains a variety of sample tests -// for a todo list app that are designed to demonstrate -// the power of writing tests in Cypress. -// -// To learn more about how Cypress works and -// what makes it such an awesome testing tool, -// please read our getting started guide: -// https://on.cypress.io/introduction-to-cypress - -describe('example to-do app', () => { - beforeEach(() => { - // Cypress starts out with a blank slate for each test - // so we must tell it to visit our website with the `cy.visit()` command. - // Since we want to visit the same URL at the start of all our tests, - // we include it in our beforeEach function so that it runs before each test - // cy.visit('https://example.cypress.io/todo') - cy.visit(`${Cypress.env('host')}`) - }) - - it('displays two todo items by default', () => { - // We use the `cy.get()` command to get all elements that match the selector. - // Then, we use `should` to assert that there are two matched items, - // which are the two default items. - cy.get('.todo-list li').should('have.length', 2) - - // We can go even further and check that the default todos each contain - // the correct text. We use the `first` and `last` functions - // to get just the first and last matched elements individually, - // and then perform an assertion with `should`. - cy.get('.todo-list li').first().should('have.text', 'Pay electric bill') - cy.get('.todo-list li').last().should('have.text', 'Walk the dog') - }) - - it('can add new todo items', () => { - // We'll store our item text in a variable so we can reuse it - const newItem = 'Feed the cat' - - // Let's get the input element and use the `type` command to - // input our new list item. After typing the content of our item, - // we need to type the enter key as well in order to submit the input. - // This input has a data-test attribute so we'll use that to select the - // element in accordance with best practices: - // https://on.cypress.io/selecting-elements - cy.get('[data-test=new-todo]').type(`${newItem}{enter}`) - - // Now that we've typed our new item, let's check that it actually was added to the list. - // Since it's the newest item, it should exist as the last element in the list. - // In addition, with the two default items, we should have a total of 3 elements in the list. - // Since assertions yield the element that was asserted on, - // we can chain both of these assertions together into a single statement. - cy.get('.todo-list li') - .should('have.length', 3) - .last() - .should('have.text', newItem) - }) - - it('can check off an item as completed', () => { - // In addition to using the `get` command to get an element by selector, - // we can also use the `contains` command to get an element by its contents. - // However, this will yield the