Skip to main content

Blog #27: 🛒💻 A Tale of Dynamic Pages & Adaptive Code - Helping a Friend Debug a Playwright Test

The other day, a friend messaged me, a bit stuck on a Playwright test:
“I’m trying to add all 3 products to the cart, but only 2 are getting added, and then it crashes! 🤯”

I couldn’t resist helping out and it turned into a fun little debugging adventure. Let me share how we cracked it!

🌟 The Scenario

It was a practice website with exactly 3 products. My friend’s mission:

👉 Log in
👉 Add all 3 items to the cart
👉 Validate that everything worked smoothly.

Sounds simple, right? But the page had a dynamic twist!


🐛 The Initial Problem

Here’s what he was using at first:
const addToCartButtons = page.locator('button:has-text("Add to Cart")');
    for (let i = 0; i < 3; i++) {
        await addToCartButtons.nth(i).click();
    }

But… it would only add 2 items and then fail with a timeout error!
Turns out, Playwright was trying to click a button that no longer existed after the page updated.

🔍 What Was Happening?

When you click “Add to Cart” on a product, the page dynamically removes that product from the list. But the for loop was working with the original static list of buttons — which quickly became outdated.

💡 The Fix: Fresh Searches with a while Loop

I explained to my friend:
Dynamic pages require dynamic approaches! Instead of relying on a stale list, let’s search fresh for the button each time we want to click.

Here’s what we changed it to:

let added = 0;

  while (added < 3) {
    await page.locator('button:has-text("Add to Cart")').first().click({ force: true });
    added++;
  }

✅ Why the while Loop Worked

🔹 Fresh search every time
Playwright looked at the page as it was in that moment, clicking the first visible “Add to Cart” button each time.
🔹 No stale references
No more “clicking” on buttons that had been removed.
🔹 Perfect for dynamic UIs
This makes it robust for dynamic sites where the UI updates after each interaction.

🎉 The Win!

With this simple tweak, we got the script working perfectly:

✅ All 3 products added!
✅ No timeouts!
✅ And a happy friend! 😁

💻 Here’s the Full Working Script
const { test, expect } = require('@playwright/test');

test('Add 3 items to cart using while loop', async ({ page }) => {
  await page.goto("https://freelance-learn-automation.vercel.app/login");

  // Login
  await page.getByPlaceholder('Enter Email').fill('example@example.com');
  await page.getByPlaceholder('Enter Password').fill('example');
  await page.getByRole('button', { name: 'Sign in' }).click();

  // Wait for page to load
  await page.waitForLoadState('networkidle');
  await expect(page).toHaveURL("https://freelance-learn-automation.vercel.app/");

  // Wait for products to load
  await page.locator('button:has-text("Add to Cart")').first().waitFor({ state: 'visible' });

  let added = 0;

  while (added < 3) {
    await page.locator('button:has-text("Add to Cart")').first().click({ force: true });
    added++;
  }

  console.log(`Added ${added} items to the cart.`);

  //  Check that the number of items in the cart is 3
  await page.locator('span.count').waitFor({ state: 'visible' });
  const countText = await page.locator('span.count').textContent();
  console.log("the count is " + countText);
  const count = parseInt(countText.trim(), 10);
  expect(count).toBe(3);

  //Go to cart
  await page.locator('.cartBtn').click();
  await expect(page).toHaveURL('https://freelance-learn-automation.vercel.app/cart');
  await page.locator('button:has-text("Enroll Now")').click();
  await page.locator('textarea#address').fill('Bingley');
  await page.locator('input#phone').fill('0123456789');
  await page.locator('button.action-btn').last().click();
 
  //capture the text
  const text = await page.locator('h4.uniqueId').textContent();
  console.log(text);

  // Assert that the uniqueId is not empty
  expect(text).toBeTruthy();

  //Click on cancel button
  await page.locator('button.action-btn.white-action-btn', { hasText: 'Cancel' }).click();
   

});

Final Takeaways

✅ Dynamic pages? Dynamic tests!
✅ Always think about how the DOM changes after each action.
✅ And don’t be afraid to swap out a for loop for a fresh approach like while!

Have you faced similar challenges testing dynamic pages?
Drop a comment below and let’s chat about it — I’d love to hear your tips and tricks!
 

Comments

Popular posts from this blog

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 # 20 :🎪 Playwright Hooks: Your Test Suite’s Best Friends!

🎩 Why Hooks? The Magic Behind the Scenes When writing automated tests, especially for web applications, repetitive tasks like logging in before each test or cleaning up after the test run can quickly clutter your code. If you've found yourself copying the same setup code into multiple tests, you're not alone! Luckily, Playwright offers a powerful feature to solve this — hooks . Imagine you’re hosting a party 🥳. You wouldn’t clean the house after every guest leaves, right? Instead, you’d: 🏗️  Setup once (decorate, cook food) → beforeAll 🗑️ Clean as you go (refill snacks, wipe spills) → beforeEach/afterEach 💣Nuclear cleanup after everyone leaves → afterAll In testing terms: Hooks automate repetitive tasks so your tests can focus on what matters. 🔮 Meet the 4 Hooks 🚀 Your Code in Action: Login/Logout Flow Let’s automate a shopping site test (your code!). Step 1: beforeEach – The “Welcome Mat” Why it rocks: Every test starts fresh, logged in, and cookie-free! test. beforeEa...

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 # 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 ...

Blog # 16: Diving into Screenshots with Playwright — Let’s Get Snapping! 🚀

Hi everyone! 👋  I’ve been exploring more of what Playwright has to offer, and I recently discovered an exciting feature—screenshots! Whether you're validating UI elements, documenting test results, or just sprinkling some eye candy into your reports 😄, screenshots can truly elevate your testing game. Let me share my recent adventures in capturing various types of screenshots using Playwright! Here’s what I tried out: A quick snapshot of the web page 🖼️ A comprehensive full-page capture, scroll and all! 📜 A focused screenshot of a specific element — like that one product image you love! 🔍 Let’s dive in! ✨ 1. Quick Page Screenshot const { test, expect } = require ( '@playwright/test' ); test ( 'Save a dated screenshot for future-you' , async ({ page }) => { await page. goto ( 'https://www.demoblaze.com/' ); // Pro move: Use ISO date (no messy slashes!) const today = new Date (). toISOString (). split ( 'T' )[0]; // "2023-09...

✍️ Blog #23: What I Learned About Annotations in Playwright

When I started, I thought writing tests was just about getting them to pass. But as the number of tests grew, I realized that being able to control which ones run, which to skip, and how to debug easily — is just as important. Let me take you through everything I’ve learned so far about Playwright’s annotations. 🔍 What Are Annotations? Annotations are special helpers in Playwright that let you modify test behavior without changing the actual logic of the test. They're great for: Focusing on a single test ( test.only ) Skipping unfinished or flaky ones ( test.skip ) Flagging tests that need fixing  ( test.fixme ) Allowing known failures  ( test.fail ) Marking slow tests  ( test.slow ) Think of them like post-it notes or switches you can stick on your tests to manage them better during testing. ✅ Test-Level Annotations These annotations go directly on individual tests. 🧪 test.only – Focus on One Test test. only ( 'run this test only' , async ...