Intelligent Quality engineering blog

Ivan Davidov and Stefan Minchev examine the architecture behind a Playwright testing framework used by five QA teams. They discuss documentation, test-data isolation, design patterns, linting, technical debt, and turning a framework into an understood, reusable scaffold rather than blindly copying one.

Ivan Davidov introduces Agentic Playwright, an open-source Playwright and TypeScript scaffold for AI-assisted test automation. It combines page objects, API contracts, fixtures, CI, repository-based AI rules, and enforcement hooks to produce more reliable tests without XPath, hard waits, or untyped assertions.

This article explains how the scaffold’s orchestration structure mirrors a technical book: a back cover, a preface, a table of contents, chapters, and an appendix. It frames this as progressive disclosure for AI agents, where metadata loads first, skills load on demand, and reference files are opened only when needed.

This article explains the `ai-native-workflow` meta skill as the operating manual for an AI-assisted QA scaffold. It walks through how tasks are routed to specialized skills, the audit-then-edit conversation contract, the seven-phase task rhythm, and the principles that keep the workflow consistent and non-guessy.

This guide covers the fundamentals of thorough REST API testing beyond checking status codes. It explains HTTP methods, headers, query parameters, payload validation, boundary cases, and how to verify response structure, authentication, and error handling in a way that catches real regressions.

After writing 30+ articles about Playwright and TypeScript, the author felt articles alone were missing deeper explanations and richer context. This post introduces the new YouTube channel and the motivation behind expanding into video tutorials.

This post continues the agentic QA series by showing how a good project scaffold enables AI-assisted testing workflows. It focuses on moving from a prompt to a passing test and emphasizes the difference between simple code suggestion and genuinely useful AI support.

This article explains an agent workflow where the browser or agent explores the application before writing code or tests. It frames exploration as a prerequisite for reliable agentic QA behavior.

This post discusses adding domain-specific skills to an AI-assisted QA workflow so the agent can apply expertise on demand. It is part of the broader agentic QA series and focuses on making AI behavior more capable and context-aware.

This article covers using a CLAUDE.md file to encode project-specific rules and guidance for an AI agent. The goal is to make AI-assisted work more consistent by giving the model explicit instructions.

This post introduces agentic QA and explains why it represents a major shift in how quality assurance can be approached. It positions AI agents as active participants in testing workflows rather than passive assistants.

This article describes a Playwright project structure designed to work well with AI-assisted development. It focuses on organizing selectors, page objects, and test data so the project is easier for both humans and agents to navigate.

This roadmap post introduces a structured path for mastering test automation, TypeScript for automation QA, and quality engineering strategies. It is meant as a starting point for readers looking to progress through the broader quality engineering series.

This article argues that specialized AI models are becoming the next important wave for development teams. It compares the current AI moment to earlier shifts such as cloud computing and mobile-first approaches.

This post focuses on building a strong test automation strategy using frameworks, CI/CD practices, and end-to-end testing. It frames these practices as part of a larger quality process before releasing software publicly.

This article explores how to maintain quality within the sprint through CI, code reviews, and collaboration. It builds on earlier cultural and planning articles to show how quality can be integrated into day-to-day delivery.

This post discusses planning practices that help prevent quality issues before development starts. It emphasizes clear requirements, well-written stories, and upfront planning as part of quality engineering.

This article explains how the TypeScript mixin pattern can improve Playwright test architecture. It addresses the limitations of a monolithic BasePage object and offers a more modular approach.

This post lays out the cultural and organizational foundation needed for sustainable software quality. It treats quality as a shared responsibility across roles rather than the job of a single testing team.

This roadmap explains what quality engineering is and how teams can build quality into products from the beginning. It argues against relying on testing alone and introduces a multi-phase approach to quality.