{"id":4307,"date":"2021-10-04T08:00:33","date_gmt":"2021-10-04T07:00:33","guid":{"rendered":"https:\/\/www.diogonunes.com\/blog\/?p=4307"},"modified":"2021-10-30T12:04:37","modified_gmt":"2021-10-30T11:04:37","slug":"ama-e2e-tests","status":"publish","type":"post","link":"https:\/\/www.diogonunes.com\/blog\/ama-e2e-tests\/","title":{"rendered":"7 questions we all had about end-to-end tests"},"content":{"rendered":"

The summary of an Ask Me Anything session I hosted at my company<\/h3>\n
\n

\ud83c\udfc6 This post was featured<\/strong> in Software Testing Weekly, #92<\/a> and Software Testing Notes, #28<\/a><\/p>\n<\/blockquote>\n

<\/p>\n

\"\"<\/p>\n

What\u2019s the definition of E2E in frontend?<\/h3>\n

I don’t think there’s a definition specific to frontend (BE). An end-to-end test interacts with your system as a user would, they are not aware of front or backend boundaries.<\/p>\n

An E2E exercises your system in terms of “width” and “depth”. These tests exercises the width<\/strong> of your system by checking the behaviour of a user journey from start to end, across multiple pages. While they do so, they are also exercising the depth<\/strong> of your system by checking all the tech layers, across frontend and backend.<\/p>\n

\"\"<\/p>\n

How does a test survive the \u201ctest of time\u201d?<\/h3>\n

First we need to define what the test of time is. In my opinion, that’s an automated check that remains reliable<\/em> and relevant<\/em> through time. To achieve that, I suggest three guidelines:<\/p>\n