dotCMS / dotCMS/core

M4 — Testing & tooling gap backlog

Open
#37,580 0 comments 0 reactions 1 assignee View on GitHub

@fabrizzio-dotCMS is already working on this.

Since Sep 16, 2026.

dotCMS : Technical Debt Team : Scout
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Sub-issue of #37124. Scout half of the Rock — pairs with Jose's M4 (#37129).

Description

Draft the testing/tooling half of next quarter's context-gap backlog: missing context in Fabrizzio's slice, plus anything found during M0–M3 that's out of scope for this Rock. Merges with Jose's backend half into one document.

Acceptance Criteria
  • Backlog entry for each testing-context gap found in M0
  • Backlog entry for .cursor/rules/ and .claude/commands/ upkeep — no process keeps them in sync with docs/ today, which is how they drifted in the first place
  • Backlog entry for the ownership of docs/cli/, docs/claude/ and docs/test-cases/ if M0's decision defers rather than resolves it
  • Each entry has a one-line problem statement and a rough size estimate (S/M/L), not just a title
  • Merged with Jose's half (#37129) into one document
  • Reviewed with the team and confirmed ready to become next quarter's Rock
Priority

Medium

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.