[TE-8730] Document Execution Progress & Test Execution Burndown widgets

[sandeepyadav-lt]

Summary

Adds documentation for the two new Test Manager dashboard widgets shipped for Ascension (Zephyr replacement deal, ~2000 licenses): Execution Progress and Test Execution Burndown. Both are now live under Analytics → Test Manager and need customer-facing docs.

• Adds Execution Progress section — gauge + Total/Executed/Remaining side counters, completion formula, filtering.
• Adds Test Execution Burndown section — three trend lines (Actual / Expected / Projected), Today marker, hover tooltip (Remaining, Ideal, Gap, Executed today, 7-day avg), footer strip (Total, Executed, Remaining, Complete %, Status, Velocity, Finish, Pace needed), date range picker + filter icon.
• Adds Drill down into remaining instances subsection describing the burndown drill-down modal (Project / Test Run Instance Name / Milestone Name filters, paginated list, export).
• Embeds a combined screenshot assets/images/analytics/tms-execution-progress-burndown.webp under the Execution Progress heading (the image shows both widgets side-by-side).
• Updates frontmatter keywords with the new widget names.

Related ticket: TE-8730
Feature PR: LambdatestIncPrivate/analytics#5654

Test plan

• npm install --legacy-peer-deps + npm start -- --port 3030 — dev server compiles successfully
• Page renders at /support/docs/analytics-modules-test-manager-widgets/ with both new sections and the embedded image
• Image require() resolves (verified via hot-reload compile — no broken-image/link warnings)
• Copy reviewed against the shipped UI (verified from screenshots of live widgets)
• Reviewer to verify copy matches the widget behavior end-to-end

Notes for reviewers

• Base is stage per the repo convention.
• The screenshot is a single combined image placed once under Execution Progress rather than duplicated under each widget — happy to split if preferred.
• The burndown copy describes three lines (Actual / Expected / Projected). The Projected line is the forward-looking dashed blue extrapolation from Today to the end date based on current velocity — please confirm that's the correct framing.

🤖 Claude conversation log

User: can you update the "documentation" repo related to the new widgets we delivered here, make sure you take latest pull of the required changes — https://lambdatest.atlassian.net/browse/TE-8730

Claude: Checked memory for TE-8730 context (two widgets, Ascension deal, analytics PR #5654). Ran git status on the documentation repo — it was on branch TE-6599. Fetched origin, saw origin/stage was 4 commits ahead of the local view and already contained refined Test Manager widgets copy (Milestone Trends, Test Runs Summary rename, tip admonitions) from a prior "TMS ATX widgets doc - part 2" commit. Fetched the TE-8730 Jira ticket via MCP to confirm widget specs: Progress Gauge (formula: (Total - Not Started) / Total) and Burndown Chart (Actual vs Expected lines, Not Started instances on Y-axis, days on X-axis, filter by test run/phase/stage). Confirmed Progress Gauge and Burndown Chart were NOT yet documented on origin/stage.

Claude: Created a worktree documentation-te-8730 on a new branch te-8730-tms-progress-gauge-burndown-docs from origin/stage, per the project's "one worktree per ticket" workflow. Edited docs/analytics-modules-test-manager-widgets.md to add two new sections (Progress Gauge / Burndown Chart) after Test Cases Types, following the existing ## widget → ### How it works? → ### Value Proposition structure, and updated the frontmatter keywords list. Asked whether to run npm run build, commit, or add per-widget screenshots.

User: first npm start locally

Claude: Ran npm install --legacy-peer-deps in the fresh worktree (no node_modules yet — 2507 packages, 42s). Started npm start, hit "port 3000 is already in use" (user's dev proxy for dev.lambdatestinternal.com points there). Restarted on port 3030 in the background. Monitor fired [SUCCESS] Docusaurus website is running at: http://localhost:3030/support/. Navigated in the Chrome extension to /support/docs/analytics-modules-test-manager-widgets and confirmed both new sections rendered cleanly with no broken markdown.

User: [Shared 3 screenshots of the actual shipped widgets — Execution Progress (with Total/Executed/Remaining side counters), Test Execution Burndown (with Actual/Expected lines, Today marker, footer strip showing Total/Executed/Remaining/Complete%/Status/Velocity/Finish/Pace needed, and a hover tooltip showing Remaining/Ideal/Gap/Executed today/7-day avg), and the drill-down modal with Project/Test Run Instance Name/Milestone Name filters]. these are the widgets so think accordingly

Claude: Realised the widget names in Jira (Progress Gauge / Burndown Chart) are NOT the shipped names. Shipped names are Execution Progress and Test Execution Burndown. Also realised my original copy missed a lot of the actual UI: the side-panel counters on the gauge, the Today marker, the rich hover tooltip, the footer metric strip, and the drill-down modal flow. Rewrote both sections:

• Renamed Progress Gauge → Execution Progress, added description of the Total/Executed/Remaining side counters.
• Renamed Burndown Chart → Test Execution Burndown, documented the Today marker, the hover tooltip fields, and the footer metric strip.
• Added a new ### Drill down into remaining instances subsection describing the modal (filters, paginated list, export).
• Updated frontmatter keywords with the corrected names.

Verified the rebuild via Chrome extension — both sections rendered with all the new sub-content intact.

User: code .

Claude: Opened the worktree in VS Code so the user could review in their editor.

User: [Shared another screenshot showing a refined version of both widgets with a third trend line in the burndown — "Projected" (dashed blue) — plus a new filter icon next to the "Test Manager" badge in each widget header]. this is the image that I want to use, give me the image name which you want to use

Claude: Checked existing naming convention in assets/images/analytics/ (tms-widgets-dashboard.webp, test-case-widgets-dashboard.webp, etc.). Suggested tms-execution-progress-burndown.webp to match the tms-* prefix pattern. Flagged that the new screenshot shows a third trend line (Projected) and a new filter icon — both of which my current copy didn't describe — and offered to fix both when wiring the image in.

User: saved file check now, and update the reference in doc

Claude: Verified the file was saved at assets/images/analytics/tms-execution-progress-burndown.webp (48 KB). Embedded an <img> tag under the Execution Progress heading (placed once, since the image shows both widgets side-by-side). Updated the Burndown copy:

• Changed "Two trend lines" → "Three trend lines"
• Added the Projected (dashed blue) line description — "forward-looking extrapolation from today to the end date based on your current velocity"
• Updated the Today marker description to mention the Actual→Projected handoff
• Added the filter icon next to the Test Manager badge to the filtering bullet

Tried to verify in Chrome again but the extension was disconnected, so fell back to reading the file and the dev server output directly — last webpack compile was 882ms with compiled successfully, confirming the image require() resolved and there were no markdown errors.

User: /commit-push-pr

Claude: Ran git status + git diff — 2 files changed (docs markdown + new webp), no debug/TODO/credentials. Staged both files, committed with conventional-commit format referencing TE-8730 and the Ascension context, pushed to the sky fork (sandeepyadav-lt/documentation), and opened this PR against LambdaTest/documentation:stage.

🤖 Generated with Claude Code