Rebalance Postman groups: move ContentTypeResourceTests out of category-content
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Problem
Postman Tests - Category Content is one of the slowest CI jobs (~40 min) and sits on the pipeline critical path. Per-collection timings from run 31054926456:
| Collection | Duration |
|---|---|
| setup + dotCMS boot | ~12 min |
| Category.postman_collection | 2m16s |
| ContentResourceV1.postman_collection | 4m23s |
| ContentTypeResourceTests | 14m37s |
| Content_Resource.postman_collection | ~6m |
Meanwhile Postman Tests - Template finishes in ~10 min (mostly boot overhead).
Fix
Move ContentTypeResourceTests from the category-content group to the template group in dotcms-postman/config.json. Expected: Category Content ~25 min, Template ~25 min — no new job, no additional boot overhead, and the Postman critical path drops ~15 min.
Related: #36910, #36912 (test speed initiative).
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
Open dotcms-postman/config.json and locate the category-content and template groups. Move ContentTypeResourceTests to template, then verify the resulting Postman CI groups and their durations match the expected rebalancing without adding a new job.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postman
- Domain
- ci-cd, testing
- Issue type
- Refactor
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100