From 90352b5655b44a24a342dd18685926a69f52f152 Mon Sep 17 00:00:00 2001
From: helena <48861601+helenanull@users.noreply.github.com>
Date: Wed, 17 Mar 2021 23:37:59 +0200
Subject: [PATCH] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 44a451e..4fe43c3 100644
--- a/README.md
+++ b/README.md
@@ -43,7 +43,7 @@ Selectors are located in `cypress/selectors` folder [only difference from cypres
 ## :grey_question: Q&A
 1. Why keep selectors separately (not hard-coded to tests)
     - selector and test logic is separated - when selector is updated, we just need to update selector file and not tests
-    - css selectors are by nature hard to read - even if we add data-test attributes. We might need 2nd child or want to verify that selector is a child for another element, like `.class2 > ul:nth-child(2)` (alternative `get().find()` or `get().parent()` is bad practice because of [this](https://docs.cypress.io/guides/core-concepts/retry-ability.html#Only-the-last-command-is-retried)
+    - css selectors are by nature hard to read - even if we add data-test attributes. We might need 2nd child or want to verify that selector is a child for another element, like `.class2 > ul:nth-child(2)` (alternative `get().find()` or `get().parent()` is bad practice because of [this](https://docs.cypress.io/guides/core-concepts/retry-ability.html#Only-the-last-command-is-retried) )
     - in large projects, we might need to re-use the same selectors. Example: in login test, we want to verify that login was successful and we check settings link in header. But the same settings link is also tested in header test.
 3. Why mobile view is in config and not in test (like cy.viewport())?
     - we can't change userAgent in the middle of the test: