From the course: Learning Playwright
Join today to access over 24,800 courses taught by industry experts.
Introduction to maintaining tests with Playwright
From the course: Learning Playwright
Introduction to maintaining tests with Playwright
- [Instructor] From my experience, the time maintaining an automated test is close to equal of the time it takes to create a specific test. Writing the test is only the first step in the automation journey. Once written, the test is there to provide the testers and developers on the team feedback automatically. It's still up to us to take that feedback, the passing or the failing of a test and doing something with it. Typically, most of this maintaining time is looking into failed tests. I found that failed tests typically fall into four different categories: A bug. The code that we are testing is broken. A bug was introduced that failed our assertion or prevented automation actions from occurring. An intended change. The code that we are testing has changed. A change to the system was made, but it was intended, and we need to go update our automated tests to account for it. Before we go too much further, flaky pie crust is good. Flakey test? Not so good, they're bad. Let's define…
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.