You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -42,7 +42,7 @@ There is also a `Makefile` to run via the CLI which is used by CI (GitHub Action
42
42
Running UI tests can suffer from a number of issues:
43
43
44
44
1. Flakiness - UI tests can be notoriously flakey if they are run against a real provider, due to the need to manage test data and mutations.
45
-
1. Managing test environments and test data itself can be a huge burdon on a team, resulting in reducing the size of the UI test suite to assist with maintenance.
45
+
1. Managing test environments and test data itself can be a huge burden on a team, resulting in reducing the size of the UI test suite to assist with maintenance.
46
46
1. Reliability - Often times to address (1) and (2), test authors will stub out endpoints to make the tests faster and more reliable
47
47
48
48
In order to combat some of the issues from above, teams may choose to fake out a backend.
0 commit comments