EPMRPP-113709 || Introduce the retry_of property for JS agents

[maria-hambardzumian]

EPMRPP-113709 — Introduce the retry_of property for JS agents

Verdict: PASS
Branch: feat/EPMRPP-113709 → develop

Auto-generated by ai-workflow pipeline.

Summary by CodeRabbit

New Features

• Added automatic linking of retried test items to their original attempts, enabling improved tracking of test retry patterns and providing more accurate performance metrics, comprehensive insights, and detailed reporting capabilities for test execution analysis and monitoring.

Documentation

• Updated changelog to document the newly introduced test item retry linking functionality and supported features.

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: a4fd3291-8eb4-4fb2-845f-38b12faf5e97

📥 Commits

Reviewing files that changed from the base of the PR and between f14c46d and f24d255.

⛔ Files ignored due to path filters (2)

• package-lock.json is excluded by !**/package-lock.json
• test-output.log is excluded by !**/*.log

📒 Files selected for processing (3)

• CHANGELOG.md
• __tests__/report-portal-client.spec.js
• lib/report-portal-client.js

---

Walkthrough

The PR adds support for the retry_of property in test item start requests. When a test item is retried, the client now resolves the predecessor from the retry chain map, conditionally includes retry_of in the API payload if a predecessor exists, and updates storage to keep full item objects instead of only promises.

Changes

Retry-linked test item tracking

Layer / File(s)	Summary
Retry item chain resolution and retry_of payload lib/report-portal-client.js, __tests__/report-portal-client.spec.js, CHANGELOG.md	When testItemDataRQ.retry is set, startTestItem resolves the previous retry-linked item from itemRetriesChainMap and conditionally includes retry_of in the REST API payload. The chain map now stores the full item object. Two test cases verify that retry_of is included when a predecessor exists and omitted when it does not. The feature is documented in the changelog.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Poem

🐰 A retry chain now holds its tale,
With links to kin that came before,
Each test knows where its twin may pale,
Predecessor tracked evermore!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: introducing the retry_of property for JavaScript agents, which aligns with the core modifications across CHANGELOG, tests, and implementation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/EPMRPP-113709

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[maria-hambardzumian]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.