e2e: Verify Traditional Page Updates in UVE
Open
Nobody has claimed this yet.
dotCMS : Technical Debt
OKR : Quality Assurance
Team : Scout
Type : Task
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Task
Create an automated End-to-End (E2E) test to verify that updates made to Traditional Pages via the Universal Visual Editor (UVE) are correctly saved and reflected.
For more information, you can refer to: Slack Channel
Proposed Objective
Quality Assurance
Proposed Priority
Priority 3 - Average
Acceptance Criteria
- [ ] An automated E2E test script is created and integrated into the existing test suite/framework.
- [ ] The test script successfully simulates and validates the following scenarios for Traditional Pages in UVE:
- [ ] Modifying a text field, saving, and verifying the change.
- [ ] Adding a new contentlet/widget, saving, and verifying its presence.
- [ ] Modifying an existing contentlet/widget, saving, and verifying the modifications.
- [ ] Removing a contentlet/widget, saving, and verifying its removal.
- [ ] The E2E test runs reliably and passes in the target testing environment.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing UVE and Traditional Page E2E tests and the test-suite integration point. Run the relevant suite in the target environment, then cover text updates, widget addition, modification, and removal, verifying each saved result and ensuring the test passes reliably.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100