As a QA engineer, I'd like to validate that edge cases templates won't cause fatal error with beacon script

Open
#206 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
php, playwright, typescript, wordpress
Domain
testing

Research direction

Locate the listed PHP templates and the Playwright end-to-end scenario that installs and activates WPR. Run each template case after clearing the cache and revisiting the page; done means no fatal error appears in debug.log and there is no visual regression.

Written by the indexing model from the issue text.

Description

Scenario shouldn't cause fatal error with invalid templates
Given WPR is installed and activated
And visit page template x
When clear cache
And revisit page template
Then no error indebug.log
And no visual regression

templates:
htmlWithDuplicatedBody.php
htmlwithduplicateheader.php
htmlwithoutbody.php
htmlwithouttitle.php
htmlwithspaceinbodytag.php
htmwithouthtmlclosure.php
htmlwithacceptablespaceintag.php
html_withoutbodynothtmlclosure.php
html_withoutbodyclosure.php

Dominant language
TypeScript
Stars
1
Forks
1
Avg merge
3d 22h
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from wp-media/wp-rocket-e2e

All issues in wp-media/wp-rocket-e2e

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.