Release 26.0.3#1119
Closed
maria-hambardzumian wants to merge 1 commit into
Closed
Conversation
maria-hambardzumian
requested review from
pressayuliya and
siarheirazuvalau
as code owners
WalkthroughThis PR updates documentation across seven files to describe new dashboard widget behaviors, test execution features, and a launch type classification system. Changes cover drill-down interactions, result pagination, filtering options, export capabilities, and the introduction of agentic versus automation launch categorization. ChangesFeature Documentation Updates
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 7
🧹 Nitpick comments (1)
docs/dashboards-and-widgets/TestCaseSearch.mdx (1)
89-89: ⚡ Quick winClarify/standardize “Test Executions” internal link
docs/dashboards-and-widgets/TestCaseSearch.mdx:89links to/features/TestExecutions/, which is the same target used elsewhere (e.g.,docs/FAQ/index.md:92). Other pages also link to/features/TestExecutions(without the trailing slash), so this isn’t an isolated/likely broken route—only a trailing-slash consistency issue; consider standardizing on one form.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/dashboards-and-widgets/TestCaseSearch.mdx` at line 89, The internal link in TestCaseSearch.mdx uses a trailing slash variant "/features/TestExecutions/" which is inconsistent with other pages that link to "/features/TestExecutions"; update the link text in docs/dashboards-and-widgets/TestCaseSearch.mdx to the canonical form "/features/TestExecutions" (remove the trailing slash) to standardize routing, and quickly search for and normalize any other occurrences of "/features/TestExecutions/" to the chosen canonical form to keep links consistent across the repo.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/dashboards-and-widgets/CumulativeTrendChart.mdx`:
- Around line 79-81: Update the user-facing visualization mode label(s) that are
misspelled: change "Staked" to "Stacked" wherever it appears in the
CumulativeTrendChart content (e.g., the heading "Staked area / Separate bars"
and the descriptive line "Staked area chart - is shown..."). Ensure both the
heading and description use "Stacked" consistently so the labels read "Stacked
area / Separate bars" and "Stacked area chart - is shown...".
In `@docs/dashboards-and-widgets/TestCaseSearch.mdx`:
- Line 20: Update the incomplete sentence describing the "Test name" text field
so it clearly states the default condition; replace the fragment 'By default –
starts with' with a full phrase such as: "Condition dropdown is disabled.
Default condition: 'Starts with' (case-insensitive)." Ensure this text appears
with the "Test name" field description so users understand the default behavior.
In `@docs/test-executions/index.mdx`:
- Around line 322-334: Replace the inconsistent label "Ignore in AA" in the "Add
Column" dropdown list with the existing terminology "Ignored in AA" so the page
uses the same label as elsewhere; locate the string "Ignore in AA" in the
docs/test-executions/index.mdx (the list under "Add Column") and change it to
"Ignored in AA".
- Around line 416-420: Rewrite the export section text for clarity: change the
first sentence "You can export Tests executions report into two formats XLS and
PDF." to "You can export Test Executions reports in XLS or PDF format." Update
the second sentence to "The report mirrors the configured columns on the Test
Executions page; if filters are applied, the exported data will reflect those
filters." Rephrase the "Include attachments" sentence to "When the \"Include
attachments\" option is enabled, the export is downloaded as a ZIP archive
containing the XLS or PDF report and any attachments related to the exported
results." Finally, make the last sentence explicit: "If no attachments are
found, the archive contains only the report file."
In `@docs/work-with-reports/FilteringLaunches.mdx`:
- Around line 37-42: Add the missing direct-link URL parameter for the
"Execution type" filter by documenting the query parameter (e.g., executionType)
in the "all parameters" direct-link table: list allowed values ("all",
"agentic", "automation"), describe what each value does, and state the default
behavior when omitted; also update the other occurrence of the same table (the
section you noted applies) so both tables include the same executionType
parameter and value descriptions.
In `@docs/work-with-reports/ViewLaunches.mdx`:
- Around line 31-32: Update the AGENTIC bullet to show the attribute as inline
code with proper spacing: replace the prose fragment "'isAgentic':true" with an
inline code snippet like `isAgentic: true` so it is formatted as code and reads
clearly in the AGENTIC description (refer to the AGENTIC bullet in
ViewLaunches.mdx).
- Line 36: The MediaViewer is using the wrong image
(require('./img/view-launches/FilterLatestRun.png')) for the Agentic badge
section; replace that require with a dedicated screenshot file (e.g.,
require('./img/view-launches/AgenticBadge.png') or a clearly named file you
add), update the alt text to describe the Agentic badge (e.g., "Agentic badge in
test automation dashboard"), and ensure the new image is committed to the same
img/view-launches folder so the MediaViewer renders the correct screenshot.
---
Nitpick comments:
In `@docs/dashboards-and-widgets/TestCaseSearch.mdx`:
- Line 89: The internal link in TestCaseSearch.mdx uses a trailing slash variant
"/features/TestExecutions/" which is inconsistent with other pages that link to
"/features/TestExecutions"; update the link text in
docs/dashboards-and-widgets/TestCaseSearch.mdx to the canonical form
"/features/TestExecutions" (remove the trailing slash) to standardize routing,
and quickly search for and normalize any other occurrences of
"/features/TestExecutions/" to the chosen canonical form to keep links
consistent across the repo.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 15ddce55-004e-437f-9154-549a1eaf72f5
⛔ Files ignored due to path filters (20)
docs/dashboards-and-widgets/img/widget-types/OverallStatisticsInterrupted1.pngis excluded by!**/*.pngdocs/dashboards-and-widgets/img/widget-types/OverallStatisticsInterrupted2.pngis excluded by!**/*.pngdocs/dashboards-and-widgets/img/widget-types/TestCaseSearch1.pngis excluded by!**/*.pngdocs/dashboards-and-widgets/img/widget-types/TestCaseSearch10.pngis excluded by!**/*.pngdocs/dashboards-and-widgets/img/widget-types/TestCaseSearch11.pngis excluded by!**/*.pngdocs/dashboards-and-widgets/img/widget-types/TestCaseSearch12.pngis excluded by!**/*.pngdocs/dashboards-and-widgets/img/widget-types/TestCaseSearch13.pngis excluded by!**/*.pngdocs/dashboards-and-widgets/img/widget-types/TestCaseSearch14.pngis excluded by!**/*.pngdocs/dashboards-and-widgets/img/widget-types/TestCaseSearch15.pngis excluded by!**/*.pngdocs/dashboards-and-widgets/img/widget-types/TestCaseSearch16.pngis excluded by!**/*.pngdocs/dashboards-and-widgets/img/widget-types/TestCaseSearch2.pngis excluded by!**/*.pngdocs/dashboards-and-widgets/img/widget-types/TestCaseSearch3.pngis excluded by!**/*.pngdocs/dashboards-and-widgets/img/widget-types/TestCaseSearch4.pngis excluded by!**/*.pngdocs/dashboards-and-widgets/img/widget-types/TestCaseSearch5.pngis excluded by!**/*.pngdocs/dashboards-and-widgets/img/widget-types/TestCaseSearch6.pngis excluded by!**/*.pngdocs/dashboards-and-widgets/img/widget-types/TestCaseSearch7.pngis excluded by!**/*.pngdocs/dashboards-and-widgets/img/widget-types/TestCaseSearch8.pngis excluded by!**/*.pngdocs/dashboards-and-widgets/img/widget-types/TestCaseSearch9.pngis excluded by!**/*.pngdocs/test-executions/img/Export.pngis excluded by!**/*.pngdocs/work-with-reports/img/view-launches/AgenticLaunches.pngis excluded by!**/*.png
📒 Files selected for processing (8)
docs/dashboards-and-widgets/CumulativeTrendChart.mdxdocs/dashboards-and-widgets/FlakyTestCasesTableTop50.mdxdocs/dashboards-and-widgets/OverallStatistics.mdxdocs/dashboards-and-widgets/TestCaseSearch.mdxdocs/test-executions/index.mdxdocs/work-with-reports/FilteringLaunches.mdxdocs/work-with-reports/OperationsUnderLaunches.mdxdocs/work-with-reports/ViewLaunches.mdx
Comment on lines
+79
to
81
| **Staked area / Separate bars**<br /> | ||
| Staked area chart - is shown one bar for statuses, and one bar for defect types for each sample. | ||
| Separate bars - is shown a separate bar for each status, and each defect type group. |
There was a problem hiding this comment.
Fix typo in visualization mode label ("Staked" → "Stacked").
This heading/text is user-facing and currently misspelled.
Proposed fix
-**Staked area / Separate bars**<br />
-Staked area chart - is shown one bar for statuses, and one bar for defect types for each sample.
+**Stacked area / Separate bars**<br />
+Stacked area chart - one bar for statuses and one bar for defect types is shown for each sample.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| **Staked area / Separate bars**<br /> | |
| Staked area chart - is shown one bar for statuses, and one bar for defect types for each sample. | |
| Separate bars - is shown a separate bar for each status, and each defect type group. | |
| **Stacked area / Separate bars**<br /> | |
| Stacked area chart - one bar for statuses and one bar for defect types is shown for each sample. | |
| Separate bars - is shown a separate bar for each status, and each defect type group. |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/dashboards-and-widgets/CumulativeTrendChart.mdx` around lines 79 - 81,
Update the user-facing visualization mode label(s) that are misspelled: change
"Staked" to "Stacked" wherever it appears in the CumulativeTrendChart content
(e.g., the heading "Staked area / Separate bars" and the descriptive line
"Staked area chart - is shown..."). Ensure both the heading and description use
"Stacked" consistently so the labels read "Stacked area / Separate bars" and
"Stacked area chart - is shown...".
| ### Refine section: | ||
|
|
||
| - "Test name" text field. Condition dropdown is disabled. By default – cnt (contains) | ||
| - "Test name" text field. Condition dropdown is disabled. By default – starts with |
There was a problem hiding this comment.
Clarify the default condition wording for "Test name".
Current wording is incomplete and ambiguous.
Proposed fix
-- "Test name" text field. Condition dropdown is disabled. By default – starts with
+- "Test name" text field. Condition dropdown is disabled. Default condition: **Starts with**.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| - "Test name" text field. Condition dropdown is disabled. By default – starts with | |
| - "Test name" text field. Condition dropdown is disabled. Default condition: **Starts with**. |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/dashboards-and-widgets/TestCaseSearch.mdx` at line 20, Update the
incomplete sentence describing the "Test name" text field so it clearly states
the default condition; replace the fragment 'By default – starts with' with a
full phrase such as: "Condition dropdown is disabled. Default condition: 'Starts
with' (case-insensitive)." Ensure this text appears with the "Test name" field
description so users understand the default behavior.
Comment on lines
+322
to
+334
| "Add Column" dropdown contains the following columns: | ||
|
|
||
| - Analyzed by AA | ||
| - Attributes | ||
| - Custom attribute | ||
| - Description | ||
| - Duration | ||
| - Execution type | ||
| - Ignore in AA | ||
| - Issue in BTS | ||
| - Method type | ||
| - Test ID | ||
|
|
There was a problem hiding this comment.
Align AA column label with existing terminology.
Line 330 uses "Ignore in AA", but the same page already uses "Ignored in AA" (Line 158). Keep one label to avoid user confusion.
Suggested fix
-- Ignore in AA
+- Ignored in AA📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| "Add Column" dropdown contains the following columns: | |
| - Analyzed by AA | |
| - Attributes | |
| - Custom attribute | |
| - Description | |
| - Duration | |
| - Execution type | |
| - Ignore in AA | |
| - Issue in BTS | |
| - Method type | |
| - Test ID | |
| "Add Column" dropdown contains the following columns: | |
| - Analyzed by AA | |
| - Attributes | |
| - Custom attribute | |
| - Description | |
| - Duration | |
| - Execution type | |
| - Ignored in AA | |
| - Issue in BTS | |
| - Method type | |
| - Test ID |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/test-executions/index.mdx` around lines 322 - 334, Replace the
inconsistent label "Ignore in AA" in the "Add Column" dropdown list with the
existing terminology "Ignored in AA" so the page uses the same label as
elsewhere; locate the string "Ignore in AA" in the
docs/test-executions/index.mdx (the list under "Add Column") and change it to
"Ignored in AA".
Comment on lines
+416
to
+420
| You can export Tests executions report into two formats XLS and PDF. The report itself will mirror the configured columns on Test Executions page and in case the filters are applied, then the exported data will also be filtered in the report. | ||
|
|
||
| When the **"Include attachments" option** is enabled, the exported result is downloaded as a ZIP archive containing XLS or PDF report and all available attachments related to the exported results. | ||
|
|
||
| If no attachments are found, the archive contains only the report file. |
There was a problem hiding this comment.
Tighten export section wording for clarity.
The opening export sentence has grammar issues (“Tests executions”, missing separators) that make the instruction harder to parse.
Suggested fix
-You can export Tests executions report into two formats XLS and PDF. The report itself will mirror the configured columns on Test Executions page and in case the filters are applied, then the exported data will also be filtered in the report.
+You can export the Test Executions report in two formats: XLS and PDF. The exported report mirrors the configured columns on the Test Executions page, and applied filters are also reflected in the exported data.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| You can export Tests executions report into two formats XLS and PDF. The report itself will mirror the configured columns on Test Executions page and in case the filters are applied, then the exported data will also be filtered in the report. | |
| When the **"Include attachments" option** is enabled, the exported result is downloaded as a ZIP archive containing XLS or PDF report and all available attachments related to the exported results. | |
| If no attachments are found, the archive contains only the report file. | |
| You can export the Test Executions report in two formats: XLS and PDF. The exported report mirrors the configured columns on the Test Executions page, and applied filters are also reflected in the exported data. | |
| When the **"Include attachments" option** is enabled, the exported result is downloaded as a ZIP archive containing XLS or PDF report and all available attachments related to the exported results. | |
| If no attachments are found, the archive contains only the report file. |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/test-executions/index.mdx` around lines 416 - 420, Rewrite the export
section text for clarity: change the first sentence "You can export Tests
executions report into two formats XLS and PDF." to "You can export Test
Executions reports in XLS or PDF format." Update the second sentence to "The
report mirrors the configured columns on the Test Executions page; if filters
are applied, the exported data will reflect those filters." Rephrase the
"Include attachments" sentence to "When the \"Include attachments\" option is
enabled, the export is downloaded as a ZIP archive containing the XLS or PDF
report and any attachments related to the exported results." Finally, make the
last sentence explicit: "If no attachments are found, the archive contains only
the report file."
Comment on lines
+37
to
+42
| - **Execution type** – allows filtering launches by the way of their execution. The following options are available: | ||
|
|
||
| * *All* – shows all launches regardless of execution type; | ||
| * *Agentic* – shows only agentic launches; | ||
| * *Automation* – shows only automation launches. | ||
|
|
There was a problem hiding this comment.
Document the direct-link URL parameter for “Execution type” as well.
You added the UI filter, but the “all parameters” direct-link table doesn’t include it. That creates a contract gap for users automating/share-link filtering.
Also applies to: 297-315
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/work-with-reports/FilteringLaunches.mdx` around lines 37 - 42, Add the
missing direct-link URL parameter for the "Execution type" filter by documenting
the query parameter (e.g., executionType) in the "all parameters" direct-link
table: list allowed values ("all", "agentic", "automation"), describe what each
value does, and state the default behavior when omitted; also update the other
occurrence of the same table (the section you noted applies) so both tables
include the same executionType parameter and value descriptions.
Comment on lines
+31
to
+32
| * AGENTIC – launches reported via AI agent (by adding system attribute 'isAgentic':true on Agent side on launch start request) | ||
| * AUTOMATION - launches reported via Test frameworks agents |
There was a problem hiding this comment.
Format the isAgentic attribute example as code and with standard spacing.
The current text 'isAgentic':true is harder to parse in prose. Prefer inline code like isAgentic: true to avoid ambiguity in setup instructions.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/work-with-reports/ViewLaunches.mdx` around lines 31 - 32, Update the
AGENTIC bullet to show the attribute as inline code with proper spacing: replace
the prose fragment "'isAgentic':true" with an inline code snippet like
`isAgentic: true` so it is formatted as code and reads clearly in the AGENTIC
description (refer to the AGENTIC bullet in ViewLaunches.mdx).
|
|
||
| Agentic launches are visually marked on the Launches page with an **Agentic** badge. | ||
|
|
||
| <MediaViewer src={require('./img/view-launches/FilterLatestRun.png')} alt="Agentic launches in our test automation dashboard" /> |
There was a problem hiding this comment.
Use a dedicated screenshot for the Agentic badge section.
Line 36 references FilterLatestRun.png, which appears to document a different feature ("Latest Launches") and can mislead readers in this new "Agentic badge" context.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/work-with-reports/ViewLaunches.mdx` at line 36, The MediaViewer is using
the wrong image (require('./img/view-launches/FilterLatestRun.png')) for the
Agentic badge section; replace that require with a dedicated screenshot file
(e.g., require('./img/view-launches/AgenticBadge.png') or a clearly named file
you add), update the alt text to describe the Agentic badge (e.g., "Agentic
badge in test automation dashboard"), and ensure the new image is committed to
the same img/view-launches folder so the MediaViewer renders the correct
screenshot.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary by CodeRabbit