diff --git a/prevent-push-when-skipping-cypress-tests-pt-2/.gitignore b/prevent-push-when-skipping-cypress-tests-pt-2/.gitignore new file mode 100644 index 0000000..c2658d7 --- /dev/null +++ b/prevent-push-when-skipping-cypress-tests-pt-2/.gitignore @@ -0,0 +1 @@ +node_modules/ diff --git a/prevent-push-when-skipping-cypress-tests-pt-2/.husky/pre-push b/prevent-push-when-skipping-cypress-tests-pt-2/.husky/pre-push new file mode 100755 index 0000000..0745e73 --- /dev/null +++ b/prevent-push-when-skipping-cypress-tests-pt-2/.husky/pre-push @@ -0,0 +1,4 @@ +#!/bin/sh +. "$(dirname "$0")/_/husky.sh" + +npx stop-only --folder cypress/integration diff --git a/prevent-push-when-skipping-cypress-tests-pt-2/README.md b/prevent-push-when-skipping-cypress-tests-pt-2/README.md new file mode 100644 index 0000000..4569135 --- /dev/null +++ b/prevent-push-when-skipping-cypress-tests-pt-2/README.md @@ -0,0 +1,8 @@ +# Prevent push when skipping Cypress tests pt.2 + +Make sure your Cypress testing pipeline never let's you push broken code +when accidentally skipping tests. + +Full details are described in the post: + + diff --git a/prevent-push-when-skipping-cypress-tests-pt-2/cypress.json b/prevent-push-when-skipping-cypress-tests-pt-2/cypress.json new file mode 100644 index 0000000..0967ef4 --- /dev/null +++ b/prevent-push-when-skipping-cypress-tests-pt-2/cypress.json @@ -0,0 +1 @@ +{} diff --git a/prevent-push-when-skipping-cypress-tests-pt-2/cypress/fixtures/example.json b/prevent-push-when-skipping-cypress-tests-pt-2/cypress/fixtures/example.json new file mode 100644 index 0000000..02e4254 --- /dev/null +++ b/prevent-push-when-skipping-cypress-tests-pt-2/cypress/fixtures/example.json @@ -0,0 +1,5 @@ +{ + "name": "Using fixtures to represent data", + "email": "hello@cypress.io", + "body": "Fixtures are a great way to mock data for responses to routes" +} diff --git a/prevent-push-when-skipping-cypress-tests-pt-2/cypress/integration/1-getting-started/todo.spec.js b/prevent-push-when-skipping-cypress-tests-pt-2/cypress/integration/1-getting-started/todo.spec.js new file mode 100644 index 0000000..6b3219a --- /dev/null +++ b/prevent-push-when-skipping-cypress-tests-pt-2/cypress/integration/1-getting-started/todo.spec.js @@ -0,0 +1,145 @@ +/// + +// 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") + }) + + 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