Cypress E2E Testing and Component Testing

[emilyjiji]

Use Cypress to create E2E testing for Sprint 2

[emilyjiji]

Test1 with Cypress

[emilyjiji]

Testing login page redirects to landing page-- test successful

[emilyjiji]

Test Complete:
Redirect to login page from landing page after clicking 'login'
email without a password will fail to login and ask user for password

[Brian-Magnuson]

Sprint 2 is now complete. This issue should be renamed to better suit its purpose

[Brian-Magnuson]

Several cypress tests now exist:

Component tests

components/dash-budgets - Tests if it can add tables, add to existing tables, delete data from tables, delete tables, and edit table entries.
Changed to be compatible with the current version that uses an API to calculate period information.

components/dash-transactions - Tests if it has a table, has a button that opens a modal, can display entries from the mock service, has a detail row that pops out, can add transactions, can edit transactions, and can delete transactions.
Changed to test the component more thoroughly with add, edit, and delete functions.

components/event-card - Tests how it displays information in each of its states, including "On Track", "Upcoming", "Overspent", and "Completed".

components/dash-calendar - Tests if it can display the current month and can navigate between months.

components/alert - Tests how it displays colors, text, and icons.

components/dash-home - Tests if it can mount

components/dash-settings - Tests if the delete user button behaves as it should and calls a function.

components/page-not-found - Tests if it has a button and if that button calls a function when clicked.

routes/landing - Tests if it can mount

routes/dashboard - Tests if it has visible buttons, it calls a function immediately, and it calls a function upon clicking log out.

routes/login - Tests if it automatically attempts to log in and tests various inputs to see what will permit the user to log in.

routes/signup - Tests various inputs to see what will allow the user to log in.

End-to-End tests

dashboard

• Tests that it opens when the user is logged in.
• Tests if the buttons link to different parts of the app.
• Tests if the 404 page works.
• Tests the logout button and checks that the user cannot easily log back in.
• Changed to account for new button for progress page.

transactions

• Tests if the user can access the transaction page and transaction modal.
• Tests if the user can add data to the table.
• Tests if the user will still have their data after logging out and logging back in.
• Tests if old data does not appear when the user recreates their account after deletion.
• Changed to account for the new method for selecting transaction categories.

budgets

• Tests if the user can access the budget page and budget modal.
• Tests if the user can add data to the table.
• Tests if the user will still have their data after logging out and logging back in.
• Tests if old data does not appear when the user recreates their account after deletion.
• Changed to now test how adding budget categories influences the category options in transactions.
• Now tests how renaming/deleting budget categories influence existing transactions.

calendar

• Tests if the user can access the calendar page.
• Tests if the user can add budgets and have them appear as calendar events.
• Tests if the user can add transactions and have them count toward calendar events.

login

• Runs several tests to see what permits the user to log in.
• Logs the user in and tests if the user is directed to the dashboard.
• Tests if going to the login page when already logged in will redirect the user.
• Tests user registration and user deletion.