Skip to content

joanna-konopacka/qa_cypress_e2e_project

 
 

Repository files navigation

Drash Example App

Workflow

  1. Fork the repo.
  2. Clone your forked repository.
  3. Run npm i.
  4. Create a new branch git checkout -b e2e_testing.
  5. Run the app.
  6. Resolve tasks.
  7. Check yourself before submitting the task with a Cypress checklist.
  8. Create a pull request.
  9. Do not forget to click on Re-request review if you submit the homework after previous review.

Task

Go to e2e folder and cover listed functionality with e2e tests:

  • creating an article;
  • editings an article;
  • deleting an article;
  • sign in (positive);
  • sign in (invalid credentials);
  • sign up (positive);
  • sign up (negative);
  • following/unfollowing the user;
  • updating bio;
  • updating username;
  • updating email;
  • updating password.

Basics level

  1. Clear all data from the database before the test.
  2. Add data-qa attributes for all elements you are working with in tests.
  3. Use faker and custom methods to generate a fake data in tests.

Advanced level

Use PageObject pattern for your tests:

  1. Create a files with POM classes for your pages in cypress/support/pages.
  2. Use PageObject.js file for the common for the whole app elements.

Observe an example in cypress/e2e/signIn.cy.js.
Find and additinoanl about Page Object in the Cypress topic.

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • TypeScript 58.4%
  • JavaScript 20.4%
  • Vue 20.0%
  • HTML 0.6%
  • Dockerfile 0.5%
  • Makefile 0.1%