DEV Community

Styrow.dev
Styrow.dev

Posted on Originally published at styrow.dev

How do you perform content validation on dynamically generated PDF reports within an E2E Playwright test?

⚠️ 90% of Playwright engineers struggle with this E2E challenge:
How do you validate content within dynamically generated PDF reports using Playwright?

📌 Problem Statement
Playwright excels at browser automation, but it doesn't inherently read PDF file content. When your application generates a PDF, Playwright can handle the download, but direct internal validation requires an external approach.
❌ Relying solely on Playwright for PDF content assertions.
✅ Integrating a Node.js PDF parsing library for file introspection.
• The challenge: Intercepting download, saving locally, parsing, then asserting.

💡 Solution & Code Walkthrough
We leverage pdf-parse (a Node.js library) to extract text from downloaded PDFs, combining it with Playwright's robust download handling.

First, install pdf-parse and @playwright/test:
npm install pdf-parse @playwright/test

Here's a concise Playwright test example:

import { test, expect } from '@playwright/test';
import * as path from 'path';
import * as fs from 'fs/promises';
import pdfParse from 'pdf-parse';

test('validate content of generated PDF report', async ({ page }) => {
  const downloadPath = path.join(__dirname, 'temp_report.pdf');

  // 1. Navigate and trigger PDF download
  await page.goto('https://example.com/reports'); // Your app URL
  const [download] = await Promise.all([
    page.waitForEvent('download'),
    page.locator('#generatePdfButton').click(), // Your PDF trigger
  ]);

  // 2. Save the downloaded PDF locally
  await download.saveAs(downloadPath);

  // 3. Parse PDF content using pdf-parse
  const data = await pdfParse(downloadPath);
  const pdfText = data.text; // Extracted text content

  // 4. Assert specific content
  expect(pdfText).toContain('Invoice No: INV-XYZ-123');
  expect(pdfText).toContain('Total Amount: $199.99');
  expect(pdfText).not.toContain('DRAFT'); // Example: ensure not a draft

  // 5. Clean up the temporary file
  await fs.unlink(downloadPath);
});
Enter fullscreen mode Exit fullscreen mode

🔑 Key Takeaways
• Playwright handles browser interactions and file downloads perfectly.
• For non-browser content validation (like PDFs), integrate purpose-built external libraries.
• Always clean up temporary files created during tests to maintain a clean environment.
• This pattern extends to other file types (e.g., CSV, XLSX) using appropriate parsers.

❓ Quick Summary Q&A
• Q: Why can't Playwright read PDF content directly?
A: Playwright interacts with the browser's DOM; PDFs are external file formats.
• Q: What is pdf-parse?
A: A Node.js library to extract text and metadata from PDF files.
• Q: Is cleanup important?
A: Yes, to avoid clutter and ensure test environment consistency.

TAGS: playwright, e2e testing, pdf validation, javascript, typescript, automation, qa

────────────────────────────────────────
Unlock advanced E2E testing strategies!
Download our app for exclusive guides & cheatsheets.

────────────────────────────────────────

📲 𝐅𝐑𝐄𝐄 𝐌𝐎𝐁𝐈𝐋𝐄 𝐀𝐏𝐏 — 𝟔𝟎𝟎+ 𝐒𝐃𝐄𝐓 𝐐&𝐀𝐬
Practice real-world interview scenarios offline on the free QA Automation & SDET Prep app:

🤖 𝐆𝐨𝐨𝐠𝐥𝐞 𝐏𝐥𝐚𝐲 (𝐀𝐧𝐝𝐫𝐨𝐢𝐝):
https://play.google.com/store/apps/details?id=com.app.seleniuminterviewquestions&referrer=utm_source%3Ddevto%26utm_medium%3Darticle%26utm_campaign%3Dselenium_20261118

🍎 𝐀𝐩𝐩 𝐒𝐭𝐨𝐫𝐞 (𝐢𝐎𝐒):
https://apps.apple.com/app/id6786760948?pt=128640464&ct=devto_selenium_20261118&mt=8

────────────────────────────────────────
────────────────────────────────────────

Top comments (0)