wp-media / wp-media/wp-rocket-e2e

As a QA eng, I'd like to validate that no error with different scenarios related to AS

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

Nobody has claimed this yet.

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

Description

@actionscheduler
Scenario Should open scheduled actions page without having any error with 3rd parties
Given old action scheduler is installed and activated i.e version 3.8.2
And WPR is installed and activated
When visit the scheduled actions page
Then no error in debug.log

Scenario Shouldn't cause error when rucss is enabled while old AS is used
Given old action scheduler is installed and activated i.e version 3.8.2
And WPR is installed and activated
When enable rucss
And clear cache
And visit home page
Then Used CSS is added to the page
And no error in debug.log

scenario Shouldnot cause error if AS table was deleted
Given wpr is installed and activated
And AS actions table is deleted from DB
When enable rucss
And visit home page
then no error in debug.log
And AS actions table is recreated

Scenario Should prevent notice undefined AS property
Given Woocommerce is enabled
And wpr is installed and activated
When enable rucss
And Add product to cart
When delete item from cart as admin
And visit this URL domain/?wc-ajax=get_refreshed_fragments
Then no error in debug.log

Scenario Should hide past-due tab at AS
Given AS latest is installed and activatedd
And WPR is installed and activated
When clear and preload cache
And visit scheduled actions page
And refresh
Then no past due tab is there
And no error in debug.log

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.

Research direction

Start with the repository's Playwright E2E test setup and identify the entry points for scheduled actions, debug.log checks, cache controls, and database-table setup. Reproduce the five listed Action Scheduler and WPR conditions, then confirm the expected absence of errors, Used CSS behavior, table recreation, and hidden past-due tab.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.