From 418c9666abb82c4fc60793406c90ff073b55ea00 Mon Sep 17 00:00:00 2001
From: ThinkTink <50761589+ThinkTink@users.noreply.github.com>
Date: Fri, 19 May 2023 12:43:18 -0400
Subject: [PATCH] Remove test instructions

---
 README.md | 21 ---------------------
 1 file changed, 21 deletions(-)

diff --git a/README.md b/README.md
index 37ac3c3..d59a238 100644
--- a/README.md
+++ b/README.md
@@ -79,24 +79,3 @@ In a separate terminal, start the back end:
 cd server
 npm run dev
 ```
-
-## How to Run E2E Tests
-
-1. Seed the database with `npm run seed` in `server` directory.
-1. Start the backend server with `npm run dev` in `server` directory.
-1. Start the frontend server with `npm start` in `client` directory.
-1. Open Cypress dashboard with `npx cypress open` in `client` directory.
-1. Click on the test suite to run (e.g. `auth.spec.js`).
-
-#### Notes
-
-- You need to seed the database before each run. Because E2E test cases writes data to
-  the actual database, re-seeding is necessary to assure consistent test results.
-- The E2E tests are not comprehensive.
-  There is a test for the authentication pages that should pass with the starting code,
-  and some tests for some of the functionality for some of the tickets you will be assigned.
-- When you push your changes to GitHub, E2E tests are automatically executed on GitHub Actions.
-  You can find test results under Pull request > Checks > test > Cypress (see screenshots below).
-
-![image](https://user-images.githubusercontent.com/8978815/136117299-b45a61ce-0b5c-495f-b572-05ad80b78a28.png)
-![image](https://user-images.githubusercontent.com/8978815/136119935-4b941f87-0015-48c5-b93e-5bd0bcbbd64b.png)