An Intro to Agentic Testing : Overview and the PRP System

August 30, 2025

Contents : Module 1 Lesson 1

This Module

Module 1 – Building an Automation Framework with the PRP System

  • Lesson 1 : Overview and the PRP System (this document)
  • Lesson 2 : Pre-requisites and Setup
  • Lesson 3 : Step-by-step Build and Execute
  • Lesson 4 : Documentation and Debugging
  • Bonus Lesson : Getting Started with Claude Code

New Modules Comming Soon

Module 2: Developing your PRP Process to Add Tests
Module 3: Using MCPs to build a better Automation Framework
Module 4: PTP System for Test Case Creation
Module 5: Executing and Running Tests with PTP
Module 6: Agentic Test Maintenance

Introduction

The high-level architecture we’re working with is based around three core components: PRD, PRP, and the PTP.

image

PRD : Product Requirements Document — it defines WHAT to build. In our case this will be our “Playwright Test Automation Framework”.

PRP : Product Requirement Prompts – These are prompts that expand on the PRD to provide detailed instructions on HOW to build the application that your team are developing.

PTP : Product Testing Prompts – These are the HOW to test the product (we cover this in a later module)

These three components come together to provide us with this agentic product development and testing framework that works so well together.

For now though our initial focus for this particular lesson is based around just the PRD and the PRP because what we’re going to do is take that concept, extract it, and use it to build our automated test framework.

So think of the testing framework as the product we’re building. Later we’ll combine our Framework as part of the PTP in a complete systems for building and testing a web application.

This PRP system is an approach to software development that’s gaining ground fast. There’s various variations on this theme but it’s focus is on building comprehensive prompts that deliver well built working software.

 

What is the PRP Methodology

The PRP methodology, or system, is basically a library of assets and templates used for agenetic engineering or developing products and code with AI tools like Core Claude Code.

image

Provided below is a link to the original repository that Rasmus Wielding has built. This enables you to take a product requirement document, create product requirement prompts, and then execute those prompts with a coding tool like Claude Code to build a product.

If you want to go deeper then I’d recommend exploring his GitHub repo here..

https://github.com/Wirasm/PRPs-agentic-eng

I’ve starting using this methodology successfully to build test automation harnesses and then built on a PTP (Product Testing Prompts) methodology and embeds that into the whole system to create this whole agentic development and testing loop. But first, we need to understand the PRP methodology, and the best way to do that is to use it to build test automation framework and we’re going to do that with a framework built around Playwright.

What we’re going to do is take the core most important parts from this system and we’re going to use those to build our test automation framework. We have Playwright-orientated prompts and examples that we plug into this framework that enable us to easily and quickly build out a Playwright project with no coding.

Course GitHub Repository

We get into the details of how to use this in the next lesson.

For now though i want to describe the high level components and process. Show you how to modify and apply this system to building a framework with Playwright.

In later modules in this course I’m going to introduce you to the PTP (Product Testing Prompts) methodology that slots into this PRP (Product Requirements Prompt) methodlogy.

PRD – Product REquirements Document
PRP – Product Requirement Prompts
PTP – Product Testing Prompts

For now though  one step at a time let’s focus on one aspect, the PRD and PRP steps to build a Playwright automation framework.

How Does the PRP System Work?

How does this system work? How do the different parts connect? What do you need to do to use it?

The Process

The overall workflow is like this.

image

You’d start with an idea (possibly working with an AI chatbot like Claude Code or ChatGPT to develop and work through your idea).

Then we create a product requirements document. This is the high-level “what to build” document. What I’ve done for this course is already gone through the idea and the AI chat to create the PRD on the main branch. You’ll find the PRD document in the repository. It’s been honed to help provide the basis for a well-structured, well-designed Playwright test automation framework in TypeScript.

Now that PRD, along with the PRP README.md which outlines the process for Claude Code, the PRP template which gives an example of what to create, the Claude.md (which contains these high-level instructions that guide Claude Code when it’s working). Then with the Claude Code slash command, the PRP create command, all of those components come together to create your specific PRP document. You just run the create PRP slash command in Claude Code. The output from this is the PRP document

You now have a VERY detailed how-to-build-the-playwright-framework document.

There’s an example PRP document that I’ve created on the main branch of the code repo. I’ve used this to build my own Playwright frameworks.

Once you have the PRP document, we want to execute on it to build our Playwright framework. The execute PRP slash command takes in the PRP document, the PRP README, which provides the overview of the whole process to your code instance, and of course the Claude.md file, which Claude code uses as high-level instructions and a guide to any coding project it’s working on. We run the PRP execute command with all those inputs, and from that, Claude code will go away and build you your Playwright framework in TypeScript.

Some key bits to understand here

  1. the PRP ReadMe, the Claude.md, and the create PRP commands are specific to the overall PRP system.
  2. the PRD, the PRP templates and our AUT (Applicaiton Under Test) that we feed in, are what guide this system to build our “Specific” Playwright framework PRP document. It’s then executing on that PRP document, which is our very detailed “How to build” Playwright frameworks, that results in us getting our working TypeScript playwright framework for OUR application.

How do all of these components fit together then?

The Components

So there are a number of parts to this system.

image

It consists of some templates, PRP templates that Claude Code can use as an example to create your specific PRP. Secondly, there are a number of key slash commands that Claude Code will understand to help you generate your PRP and to help you execute on your PRP to create your actual coded framework.

The three core commands you’ll use are: PRP PlanningPRP base and PRP execute.

Now I have modified these commands specifically to enhance them to create test automation frameworks. I will take you through these commands so that you understand how to use them and how to update them when you need to. These commands are designed to leverage the PRP template that we use to create the PRP specifically for YOUR implmentation of a Playwright framework.

There is also a PRP README.md file that provides an overview of the whole process. That’s useful for you too, but it’s also useful for the AI coding agent so that it understands the context and the whole end-to-end process.

Thirdly, there’s the global rules directory or claude.md file that acts as a high-level directive or memory for Claude code when it’s working on your project. Again, I’ve customized this for your project for the building of test automation frameworks.

Another key input to this whole system and methodology are tehe example templates. AI loves examples to help it see what it’s output is expected to look like. I’ve created a PRD template and a PRP template specifically around a Playwright framework. This gives Claude Code loads of context when it comes to creating our speicifc version of the PRD and PRP documents.

Finally we’ll key Claude Code into the actual application we want to design our Playwright automation framework to test. In this instance we’ll provide the source code to our application in our repo. You’ll find the directory APP-UNDER-TEST in the course github repo. This could also be a direct pointer to a running instance of the application you’re testing. We’ll stick to teh soruce code for now. This will help Claude Code create a Playwright Framework specific to our application that we wan’t to test.

What We’re Going To Do Next

If you want to go deep into the PRP system, then I would go to this Git repo, clone it and work through a lot of the examples here.

PRP Agentic Engineering Repo

This framework/repo from Rasmus will enable you to build TypeScript, Python applications from scratch using this system. And within this repo are templates for building many different types of applications.

If you want to keep things simple to start with use our course repo here

Course GitHub Repository

What I’ve done in our repo for this course, is take the core parts of this PRP system and built templates and commands specifically for building test automation frameworks in TypeScript for Playwright.

Over the duration of this six-module course, you will find examples, templates, and architecture documents to help you build both UI and API test automation frameworks.

Next, in Lesson 2, I’m going to walk you through setting up your system and the tools you need.

Then, in Lesson 3, I want to take you through, step by step, this process to build your first framework with the PRP system.

I’m going to walk you through a 5 step process

​​​​1. Define your idea
​​​​2. Turn your idea in to a PRD
​​​​3. Develop your idea into a comprehensive PRP
​​​​4. Feed the PRP into Claude Code to build your Playwright framework
​​​​5. Test your finished framework

Remember – learn this and you’ll have a system at your finger tips for building all sorts of test tools and testing frameworks!!!