dotCMS / dotCMS/core

JVM Unit Flaky Tests

Open
#30,604 1 comment 0 reactions 1 assignee View on GitHub

@victoralfaro-dotcms is already working on this.

Since Nov 7, 2024.

Team : Falcon Type : New Functionality
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

User Story

As a Java developer, I want to fix a flaky JVM unit test in the HTMLPageAssetRenderedAPIImplTest class so that it passes consistently, ensuring more reliable test outcomes and faster feedback loops.

Acceptance Criteria
  • The flaky test(s) in HTMLPageAssetRenderedAPIImplTest are identified and fixed.
  • Tests pass consistently across different environments and executions.
  • Code is reviewed and approved by the Quality Assurance team.
dotCMS Version

master

Proposed Objective

Quality Assurance

Proposed Priority

Priority 2 - Important

External Links
Assumptions & Initiation Needs
  • Access to the existing test suite for HTMLPageAssetRenderedAPIImplTest.
  • Test environments where the flaky behavior is observed.
  • Coordination with QA for validation of the fix.
Quality Assurance Notes & Workarounds
  • If possible, implement mock or stub strategies to isolate the test environment and avoid external dependencies that may cause flakiness.
  • Ensure tests are executed in multiple environments to confirm reliability.
Sub-Tasks & Estimates
  • Identify root cause of test flakiness: 4 hours
  • Implement fix for test(s): 6 hours
  • Review and validation by QA: 2 hours
  • Final documentation and code check-in: 1 hour

Contributor guide

Open the contributing guide

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.