From 97236a422a65a3a3f4f3ce9e448239fc59232dfd Mon Sep 17 00:00:00 2001
From: Matvey <40901939+matvelius@users.noreply.github.com>
Date: Thu, 8 Oct 2020 15:13:01 -0500
Subject: [PATCH] Update testing.md
add the missing name (E2E)
---
src/v2/guide/testing.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/v2/guide/testing.md b/src/v2/guide/testing.md
index adbe7ecc78..7375c43615 100644
--- a/src/v2/guide/testing.md
+++ b/src/v2/guide/testing.md
@@ -116,7 +116,7 @@ While end-to-end (E2E) testing on the web has gained a negative reputation for u
One of the primary benefits that end-to-end (E2E) testing is known for is its ability to test your application across multiple browsers. While it may seem desirable to have 100% cross-browser coverage, it is important to note that cross browser testing has diminishing returns on a team's resources due the additional time and machine power required to run them consistently. As a result, it is important to be mindful of this trade-off when choosing the amount of cross-browser testing your application needs.
-A recent development in for catching browser-specific issues is using application monitoring and error reporting tools (e.g., Sentry, LogRocket, etc.) for browsers that are not as commonly used (e.g., < IE11, older Safari versions, etc.).
+A recent development in E2E for catching browser-specific issues is using application monitoring and error reporting tools (e.g., Sentry, LogRocket, etc.) for browsers that are not as commonly used (e.g., < IE11, older Safari versions, etc.).
#### Faster feedback loops