Interface concept · Metrics and logs are illustrative · Custom development on Playwright.
Website Monitoring and Browser Automation / PLAYWRIGHT
A website cannot tell you what broke Make every inspection replayable
Yuqi works with websites, forms and business entry points , developing checks on Playwright to turn a page visit into an executable, verifiable and versioned inspection workflow. The proposed system makes results reviewable.
Agreed scope
Example entry-point coverage
COVERAGE / ENTRYPOINTS
Configured
Example execution window
RUN WINDOW / CYCLE
On demand
Scheduling to suit your needs
SCHEDULE / ON DEMAND
4 modules
Planned delivery modules
PROJECT MODULES
EXAMPLE RUN #084 · Illustrated inspection
38 / 38 PASS
Homepage · Forms · Sign-in · Business portals
DRIFT WATCH · Locator changes
2 PENDING
Illustrative changes awaiting human review
EVIDENCE · Retained artifacts
Screenshots + video + logs
Evidence can be linked to individual browser actions
OBSERVATION TARGET / Example homepage
Illustrating 38 assertions
and their evidence
and their evidence
- 01 Homepage rendering PASS
- 02 Navigation and key links PASS
- 03 Form field accessibility PASS
- 04 Submission and receipt text PASS
- 05 Locator drift review REVIEW
- 06 Business entry redirects PASS
ENGINE Playwright / Chromium
TRACE ON
SCREENSHOT ON FAILURE
38 PASSED · 0 FAILED · 2 REVIEW
01 / WHY · From assumptions to evidence
Inspection should give you more than a report: a repeatable, reviewable and versioned workflow
When websites and forms support leads and transactions, availability needs explicit checks, independent review and a maintained test baseline.
THE PREMISE / What matters
Loading a page is just the beginning.
Business continuity also depends on knowing where a failure started, who reviews it and how to restore the test baseline 。
The proposed workflow connects scripts, task settings, schedules, notifications and evidence. Each component has agreed deliverables and responsibilities.
Website
Lead forms
Sign-in and access
Business queries
Downloads and receipts
SCENE / Operations and IT review OBSERVE 01
GATE 01 / REPEATABLE
Rehearse before release
Write browser actions and assertions for agreed journeys. Run them before releases, redesigns or campaigns in the appropriate test environment.
GATE 02 / REVIEWABLE
Evidence for each conclusion
Attach configured screenshots, videos and logs to results. Route exceptions to the appropriate reviewer.
GATE 03 / VERSIONED
Maintain a verified test baseline
Version scripts, cases and settings. After page changes, review locators and rerun checks before accepting a revised baseline.
GAP 01
Manual discovery
Customers may discover broken forms before internal teams do.
GAP 02
Different definitions
Business, development and operations may disagree about what counts as normal.
GAP 03
Hard to reproduce
A screenshot alone does not explain the actions or execution environment.
GAP 04
Notification fatigue
Without severity levels and quiet periods, useful alerts can be lost.
02 / ARCHITECTURE · Clear responsibilities
Five layers: from business entry points to evidence review , with explicit responsibilities
Separate scripts, settings, schedules and runtime operations so changes can be maintained and handed over independently.
ARCH / INSPECTION PIPELINE · 5 LAYERS
● TRACE ENABLED · RUN #084
Checks and execution
Orchestration and feedback
Schedules and review queues
Verified test baseline
Assertion failure
L1 · TARGET
Business entry inventory
Agree the pages, forms and redirects that matter and record them as identifiable inspection targets.
L2 · ENGINE
Playwright scripts
Write actions and assertions with shared waiting, retry and evidence settings.
L3 · CONFIG
Settings and result views
Develop task, history and exception views that business users can understand.
L4 · SCHEDULE
Scheduling and messaging
Integrate scheduling and notification channels with agreed severity and escalation rules.
L5 · OPERATE
Environment and ownership
Define runtime hosts, access, credential custody, diagnosis and maintenance responsibilities.
ENV / Private deployment or hosting by agreement ARCH 02
DESIGN PRINCIPLE 01
Separate concerns
Page changes affect cases; channels, schedules and runtime settings can be maintained separately.
DESIGN PRINCIPLE 02
Keep failure context
Retain configured steps, screenshots, console output and traces to support investigation.
DESIGN PRINCIPLE 03
Version code and documentation
Plan source, parameters, deployment and operating guides so the customer can maintain the system.
03 / PROJECT 01 · CHECK SCRIPT
Write checks for agreed business journeys
Develop scripts on Playwright using semantic locators and explicit expectations. Website code changes are outside the default inspection scope.
specs / lead-form.spec.ts
● 38 ASSERTIONS / PASS
01020304050607080910111213141516
import { test, expect } from '@playwright/test';
// Example: visibility, submission, receipt and evidence
// Website / Lead form · Example journey 01
test('lead-form happy path', async ({ page }) => {
await page.goto(env.BASE_URL + '/contact');
await expect(page).toHaveTitle( /contact/ );
await expect(page.locator('[data-qa=lead-form]'))
.toBeVisible({ timeout: 8000 });
await page.getByLabel( 'Name' ).fill( 'Inspection example' );
await page.getByLabel( 'Phone' ).fill('13800000000');
await page.getByRole('button', { name: 'Submit' }).click();
await expect(page.locator('[data-qa=success]'))
.toContainText( 'Received' );
await page.screenshot({ path: trace('lead-form.ok') });
});
Last run 00:42.318 · trace.zip + video.webm + console.log retained
01
Homepage and hero
Heading, key blocks, resources and console errors
8 PASS
02
Navigation and key links
Reachability, status codes, external links and anchors
6 PASS
03
Lead form
Fields, validation, submission and receipt
7 PASS
04
Sign-in and access
Redirects, errors and isolated test accounts
5 PASS
05
Queries and downloads
Results, files and empty states
7 PASS
06
Receipts and next steps
Confirmation screens and return journeys
5 PASS · 2 REVIEW
WHAT WE BUILD / Custom work
Scripts describe business actions
Use semantic locators and stable conventions. Keep cases separate from settings and configure waits, retries, screenshots and tracing.
Assertion layers
- Presence : key elements, messages and sections
- Reachability : status, redirects and resources
- Journeys : input → submit → receipt
- Consistency : agreed environments and viewports
SPEC / Cases mapped to business journeys 01 / SCRIPT
Operating boundaries
Use read-only checks where possible. Write actions require prior authorization, test accounts, an appropriate environment and cleanup rules.
Read-only first
Isolated test accounts
Keep credentials out of source
04 / PROJECT 02 · INSPECTION CONFIG
Inspection settings: task parameters, history and exceptions in one workspace
Develop views for business, operations and development around shared definitions and records.
yq-inspector / Interface concept · Task T-014 · Website and forms
RUN #084ENV / PROD-READONLY● ONLINE
BASE_URL
https://www.example-corp.com
BROWSER
Chromium / headless
VIEWPORT
1440×900 · 390×844
CONCURRENCY
3 workers
TIMEOUT
8 000 ms
RETRY
1 / on failure
SCREENSHOT
on failure + on review
TRACE
retain-on-failure
SUITE
38 assertions / 6 flows
CADENCE
every 15 min · 07–23
NOTIFY LEVEL
P1 immediate / P2 digest
EVIDENCE TTL
90 days
EXAMPLE EXECUTION LOG
8 illustrative runs
| RUN ID | Time | Scenario | Duration | Assertions | Outcome | Reviewer |
|---|---|---|---|---|---|---|
| #084 | 11-14 08:42 | Website / Forms / Redirects | 42.3s | 38/38 | PASS | Automatic |
| #083 | 11-14 08:27 | Website / Forms / Redirects | 41.8s | 38/38 | PASS | Automatic |
| #082 | 11-14 08:12 | Website / Forms / Redirects | 43.1s | 37/38 | REVIEW | Example operator |
| #081 | 11-14 07:57 | Website / Forms / Redirects | 42.0s | 38/38 | PASS | Automatic |
| #080 | 11-14 07:42 | Sign-in / Queries | 38.6s | 36/38 | FAIL | Example developer |
| #079 | 11-14 07:27 | Website / Forms / Redirects | 42.7s | 38/38 | PASS | Automatic |
| #078 | 11-14 07:12 | Downloads / Receipts | 39.4s | 38/38 | PASS | Automatic |
| #077 | 11-14 06:57 | Website / Forms / Redirects | 41.5s | 38/38 | PASS | Automatic |
EXAMPLE EXCEPTION · RUN #080 · Business query
Assertions
toContainText('Query results') timed out. The example trace indicates that [data-qa=result-panel] was replaced. The example illustrates baseline review and locator maintenance; it is not an actual run.
REVIEW / Exceptions require an assigned reviewer 02 / CONFIG
Business users see outcomes
Show key entry status, scope and follow-up without requiring knowledge of script implementation.
Operations sees schedules and records
Review execution windows, retries, notifications and evidence retention.
Developers see context
Use configured failure steps, locators, console output, traces and screenshots for investigation.
05 / PROJECT 03 · SCHEDULE & NOTIFY
Scheduling and alerts: connect scheduled tasks and messaging to reach the right person
Agree inspection windows and notification severity, then integrate the customer's task and messaging services.
CRON / Business hours
*/15 7-23 * * 1-6
Extra checks around releases
on: deploy / config-change
● NEXT RUN 09:12
WeCom / Group bot
Example P0 / P1 immediate alerts
Assigned on-call contact
Assigned on-call contact
Email summaries
Example P2 daily summary
Evidence links and trends
Evidence links and trends
Webhooks / Task systems
Create issues through integration
Update follow-up status
Update follow-up status
SMS / Phone escalation
Unacknowledged notifications
Escalation by agreement
Escalation by agreement
NOTIFICATION CONCEPT / WeCom P1 · 08:12 · RUN #082
[Inspection review example] Website lead form 2 illustrative REVIEW assertions
Possible structure change:
→ Run history / Assign / Mark false positive
Possible structure change:
[data-qa=success] was not found. Example evidence includes a screenshot and trace. Review timing and baseline handling are agreed per project. → Run history / Assign / Mark false positive
P0 Critical entry unavailable
Example policy: notify the assigned contact and escalate according to the agreed response window.
P1 Single failure / Needs review
A retry or locator change can enter a review queue instead of closing automatically.
P2 Performance and trends
Summarize slow responses or intermittent failures according to agreed thresholds.
Quiet periods Releases and planned maintenance
Suppress repeated notifications during agreed windows while retaining configured records.
ESCALATION / Named owners and actions 03 / NOTIFY
06 / PROJECT 04 · RUN & MAINTAIN
Runtime operations: make environment, access, diagnosis and maintenance explicit responsibilities
Inspection software also needs maintenance. Define its environment and operating responsibilities before delivery.
Runtime environment
- Deployment : private host, hosted VM or containers, subject to network requirements
- Browser dependencies : pin versions and validate upgrades
- Network routes : allowlists, proxies and DNS prerequisites
- Resource planning : CPU, memory, disk and evidence storage
Access and credentials
- Least privilege : only required page access and approved test writes
- Credential custody : customer-managed secrets, never plaintext in scripts or repositories
- Role separation : settings, review and releases have agreed owners
- Audit records : log who changed settings, when and why
Diagnosis
- Identify the failure source : target page, network, browser runtime or script
- Evidence bundles : configured traces, video, console output, requests and screenshots by run ID
- Retries and suppression : reduce repeated alerts from transient dependencies
- Regression checks : rerun the same agreed cases after fixes
Script maintenance
- Version management : version cases, settings and documentation together
- Locator changes : review page changes and validate revisions
- Release coordination : include inspection case maintenance in release planning
- Knowledge transfer : source, deployment and operating guides for the customer's team
OPERATE / Explicit environment, access and diagnosis owners 04 / OPS
MAINTENANCE CADENCE / Proposed rhythm
D
Review run samples
Check notifications, ownership and evidence access
DAILY
W
Review cases and thresholds
Tune false positives, timeouts, retries and quiet periods
WEEKLY
M
Review runtime dependencies
Browser versions, storage, certificates and credential expiry
MONTHLY
C
Release rehearsal and baseline review
Run agreed journeys after changes and validate the test baseline
ON CHANGE
Security and governance
Read-only first
Isolated test accounts
Customer-managed credentials
Configurable evidence retention
Audit records
No production code changes by default
07 / DELIVERABLES · Agreed completion criteria
Plan delivery of runnable, reviewable software and documentation
Agree outputs and acceptance criteria for each phase, including source, settings, records, guides and rehearsal findings.
| Phase | Module | Outputs | Acceptance criteria |
|---|---|---|---|
| D00 | Consultation and inventory | Page inventory, journey map, exception levels and acceptance criteria | Joint approval |
| D01 | Check scripts · PROJECT 01 | Custom Playwright source, case notes, assertions and locator conventions | Agreed journeys repeatable in the target environment |
| D02 | Task configuration · PROJECT 02 | Parameters, run history, exception views and setting guides | Business, operations and developers can review results |
| D03 | Schedules and alerts · PROJECT 03 | Scheduling settings, notification integrations and escalation policies | Delivery and escalation rehearsed |
| D04 | Runtime maintenance · PROJECT 04 | Deployment guide, access matrix, credential policy and diagnosis guide | Validate the agreed migration scenario |
| D05 | Pilot and rehearsal | Run records, exception handling and baseline validation | Repeatable / Reviewable / Versioned |
| D06 | Knowledge and handover | Operating guide, training, transfer checklist and extension notes | Customer team can take ownership |
From consultation to implementation
A report → An operating workflow
Translate findings into inspection targets, assertions, schedules and ownership. Delivery is subject to implementation and agreed acceptance tests.
Inventory: which entry points matter
Define: normal, failure and review
Assign: execution, confirmation and baseline ownership
Retain: evidence for review and reuse
HANDOVER / Source, documentation and training DELIVER 07
08 / VALUE · Intended outcomes
The intended result: a reviewable availability process
These are planned outcomes tied to agreed deliverables, not measured customer results or performance guarantees.
VALUE 01
From observation to evidence
Retain configured steps, screenshots, video and logs so others can review the findings.
EVIDENCE / Run records and artifacts
VALUE 02
Shared definitions across teams
Agree normal, failure and review states across business, development and operations.
DEFINITION / Acceptance criteria
VALUE 03
Connect discovery to diagnosis
Use failure context to support investigation rather than relying on a single screenshot.
TRACE / Failure context
VALUE 04
Manage changes deliberately
Rehearse releases, rerun checks and version the inspection baseline.
ROLLBACK / Test baseline
VALUE 05
Turn findings into a workflow
Translate inventory, criteria, ownership and schedules into project-specific software.
SYSTEM / Executable workflow
VALUE 06
Keep knowledge with the customer
Plan source, parameter guides, deployment and operations manuals and training for handover.
HANDOVER / Source and guides
BEFORE / Common gaps
- Customers or sales discover failures first
- Screenshots lack steps and context
- Different teams define normal differently
- Unprioritized alerts get ignored
AFTER / Intended project outcomes
- Scheduled checks and assigned exception owners
- Configured traces, screenshots, video and logs
- Written criteria shared across three roles
- Notification levels, quiet periods and maintained baselines
4 / PROJECT
Planned project modules
SCRIPT · CONFIG · SCHEDULE · OPS
7 phases
Proposed acceptance phases
D00 → D06 / WITH SIGN-OFF
3 roles
Shared records
BUSINESS · OPS · DEV
6 types
Inspection target categories
EXTENSIBLE / ON DEMAND
09 / ROADMAP · Assessment to operations
Six implementation stages, each with agreed outputs
Define acceptance criteria before scripting and scheduling. Automating unclear rules can create repeated false positives.
01
Assess and inventory
Identify websites, forms, key journeys and business impact.
02
Agree criteria
Define normal, failure, review, severity and quiet periods.
03
Develop and review scripts
Write Playwright actions and assertions with stable locator and evidence conventions.
04
Integrate settings and schedules
Connect task parameters, history, exception views and messaging.
05
Pilot and rehearsal
Rehearse agreed journeys, alerts and baseline maintenance.
06
Handover and operations
Transfer source and guides and agree a maintenance cadence.
APPLICABLE SCOPE / Possible inspection targets
Website portals and sections
Hero, navigation and content reachability
Campaign landing pages
Campaign links, tracking redirects and receipts
Lead and contact forms
Field validation, submission and receipts
Sign-in and single sign-on
Redirects, errors and session state
Queries and downloads
Results, files and empty-state text
Bookings and registrations
Step completeness, confirmation and return paths
Languages and multiple sites
Group runs by region and time window
Post-release regression
Compare results and review the test baseline

Public and enterprise portals SCENE 01

Manufacturing / Business portals SCENE 02

Services / Booking forms SCENE 03

Retail / Lead generation SCENE 04
10 / NEXT STEP · Start with an assessment
See where your inspection
workflow needs attention
Inventory business entry points, agree criteria and ownership, then plan scripts, settings, schedules and operations in phases.
No production code changes by default
Private deployment by agreement
Source and documentation handover
ASSESSMENT SCOPE / What we discuss
Critical entry points Website / Forms / Sign-in / Queries
How failures are found today Manual checks / Monitoring / Feedback
Exception follow-up Notification owners and escalation rules
Runtime constraints Private network / Hosting / Access
Page change frequency Case maintenance and baseline needs
Output Phased plan and acceptance criteria
Playwright / GitHubDocumentationApache-2.0All solutionsPhotos: illustrative Unsplash imagery, not customer cases.