Blog # 6 : Why Login Testing Isn’t as Boring as You Think

Login forms seem simple, but they’re deceptively fragile. A tiny typo in a button’s ID, a misplaced error message, or a password field that doesn’t mask input can turn your app into a user-unfriendly nightmare.

With Playwright, I set out to automate three make-or-break login scenarios. Here’s what broke (a lot), what worked (eventually), and why you should care.

🚀 Scenario 1: When Everything Works (Eventually)

The first thing I wanted to test was the happy path—when a user enters valid credentials, clicks login, and lands where they should.

Sounds simple, right? Well, my first attempt failed spectacularly. Turns out, I forgot to wait for the page to load fully before checking the URL. Rookie mistake. 😅

Fixed Code:

What Broke?

I wasn’t waiting for the navigation properly.

What Worked?

await expect(page).toHaveURL(...) ensures the redirect actually happened before the test continues.

✅ Lesson Learned: Just because a button is clicked doesn’t mean the page has changed yet.

🚨 Scenario 2: When Login Fails (And Error Messages Matter)

Next, I wanted to test invalid logins. If a user enters the wrong credentials, the app should clearly tell them what went wrong.

I assumed the error message would show up instantly. Turns out, some apps animate them in with a delay, and my test was checking too soon. 🤦♂️

Fixed Code:

What Broke?

My test checked for the error before it was visible.

What Worked?

Playwright waits automatically for elements, but adding explicit expectations helped.

✅ Lesson Learned: Always wait for elements to fully load before asserting their text.

🔒 Scenario 3: The Eye Icon that Didn’t Blink

Ever typed your password in a crowded café and felt paranoid? That’s why login forms mask passwords by default.

Many apps let you toggle password visibility using an eye icon 👁️. My test? Verify that:

The password is hidden by default.
Clicking the eye icon reveals it.

Here’s the Code:

What Broke?

The eye icon had a tiny delay before changing the field type.

What Worked?

Adding await expect(passwordField).toHaveAttribute(...) ensures the test doesn’t check too soon.

✅ Lesson Learned: Tiny UI details matter. Don’t assume things update instantly.

💡 Key Takeaways (A.K.A What I Wish I Knew Earlier)

🔹 Clicking a button ≠ instant navigation. Always verify page transitions properly.

🔹 Error messages don’t always appear instantly. Wait before asserting them.

🔹 UI elements can have small delays. Be patient with expectations.

🎯 What’s Next?

I finally got these tests working (after breaking them a few times first 😆), but I’m excited to explore more. Stay tuned! 🚀

Have you ever struggled with login automation? What’s the weirdest login bug you’ve seen? Let’s chat in the comments! 👇

Comments

Software Testing Heuristics and mnemonics.

Software Testing Heuristics Heuristics are simply experience-based techniques for problem-solving, learning, and discovery. Where an exhaustive search is impractical, heuristic methods are used to speed up the process of finding a satisfactory solution. Examples of this method include using a rule of thumb, an educated guess, an intuitive judgment, or common sense. When you face a problem, you try some solutions that may work. For instance, if you suddenly find your mobile hang, what do you do? You may restart your mobile first. If that doesn’t work, then you may check & update the latest software and uninstall suspicious apps.if that also doesn’t work, then you reset your phone setting ( Factory reset). Most of us try a number of steps to solve our problems. These steps may not always work but we try them because we know that they may work. Following heuristics can apply to absolutely any kind of system with any kind of interface. 1.Abstract Remove details in a model. S...

Blog # 9: Say Hello to Alerts! Handling Dialog Boxes in Playwright

Alerts and dialogs are common elements in web applications that can interrupt automated test flows if not handled properly. Playwright provides straightforward methods to manage these interruptions, ensuring your tests run smoothly. In this guide, I’ll share how I learned handling three types of dialogs—simple alerts, confirmation boxes, and prompts—using Playwright’s built-in features. Why Handle Dialogs? Dialogs often appear during critical user interactions, such as form submissions, error notifications, or data input requests. If ignored, they can cause tests to freeze or fail. Playwright’s dialog-handling capabilities allow you to: Validate dialog messages. Accept, dismiss, or respond to prompts programmatically. Keep tests resilient and predictable. Let’s explore how to tackle each type of dialog. 1. Simple Alerts: The One-Way Notification A simple alert is a basic pop-up with an "OK" button. Example Scenario : A basic alert appears, shouting, "I am an alert box!...

Blog # 4 : A Deep Dive into Playwright Assertions

Ever spent hours debugging a test only to realize you forgot to check if a button was actually clickable? In web testing, the devil's in the details—and that's where assertions become your best friend. Let's explore how Playwright's assertion library can transform your testing strategy, using the popular The Internet testing playground. Why Assertions Matter Assertions are the backbone of any meaningful test. They're the checkpoints that scream, "This works!" or "Something's broken here!" Playwright's built-in expect library shines when testing real-world scenarios like authentication flows and dynamic content. Let's Start Testing: A Real-World Scenario We'll be testing key features of The Internet playground. Here's our foundation: Now let's add powerful assertions. Validating Content: Is What You See What You Get? 1. Page Titles: Your First Line of Defense Verify you're on the correct page immediately after na...

Day 15 Name five different online payment methods.

Most modern online payment services offer easy-to-use, fast and secure ways to pay Here’s a list of some of the most popular online payment services: Digital Wallet ( E wallet) A digital wallet refers to software, an electronic device, or an online service that enables individuals or businesses to make transactions electronically. It stores the payment information of users for different payment modes on various websites. PayPal PayPal is one of the most dominant payment methods available today. over 20 million UK shoppers use PayPal each year in the UK and 7 million businesses worldwide use their platform to accept payments. PayPal is an eCommerce payment processing company that allows users to set up a PayPal account and pay a fee for each cash transaction. Many customers prefer to checkout with PayPal because it’s so simple and quick to use. Amazon Pay Amazon Pay is another ...

What is Agile?

Recently I did a presentation after almost 20 years at a Bootcamp showcase on Agile. As Agile celebrated its 20th anniversary this year I decided to talk on what Agile is? Below are the few drops from Agile's ocean which I managed to pour during my showcase. What is Agile Software Development? Agile is a time boxed, iterative approach to software delivery that builds software incrementally from the start of the project, instead of trying to deliver it all at once near the end. It works by breaking projects down into little bits of user functionality called user stories, prioritizing them, and then continuously delivering them in short time cycles called iterations. In iterative development, feature code is designed, developed and tested in repeated cycles. With each iteration, additional features can...

What is Quality

✨ What is Quality? Quality means different things to different people. For some, the brand Apple 🍏 is synonymous with quality. For others, it’s difficult to define quality, but surprisingly easy to recognize based on their experiences. A quality product or service is one that satisfies customer needs and meets (or even exceeds!) their expectations. When you receive quality, in whatever form, you're eager to get more. You want to return for another purchase, refer the product to friends, and talk about it publicly. Quality is what we should aim for to ensure returning customers and a strong brand as a company. According to IEEE , quality is defined as “The degree to which a component, system, or process meets specified requirements and/or user/customer needs and expectations.” 📈 👥 Who is Responsible for Software Quality? Everyone involved in a software project—including the Product Owner , Scrum Master , Developer , Tester , and other stakeholders such as the Business ...

Risk Storming for Vending Machine

In the 4th session of Testing Bootcamp Beth Marshall introduced us to a very interesting game of Risk Storming. It's a collaborative and visual technique for identifying risk and planning the Test Strategy accordingly .You can use a Test Sphere card deck from Ministry of Testing or go to https://riskstormingonline.com/ Risk Storming takes you through three phases to get the answers. Which quality aspects matter most for your product? What risks could impact these important aspects? How can you test to make sure those risks don’t happen? Our task was to risk storming to test the Vending Machine . And here is my take on it. Quality Aspect Functionality Does it accept and return both coin and cash correctly? BOUNDARY VALUE TESTING Does it drop the selected product correctly? INTEGRATION TESTING , BUSINESS SCENARIOS , PURPOSE Is the k...

Yogita Lad

Search This Blog