Added 3 docs for Test Capture #120
Merged
Merged
Conversation
Added New Section & docs for Test Capture
📝 WalkthroughWalkthroughThis PR consolidates navigation mappings for Azure DevOps CI/CD integration, remaps it under the existing integrations group, and systematically updates the order sequencing of documentation pages across test management sections. It also introduces three new Test Capture documentation pages. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~22 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 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 |
Abdul-jailani
approved these changes
Mar 25, 2026
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 8
♻️ Duplicate comments (3)
src/pages/docs/test-management/test-capture/capture-logs.md (2)
1-21:⚠️ Potential issue | 🟠 MajorAdd navigation entries and pagination fields.
This page has the same missing navigation and pagination issue as flagged in
overview.md. The page needs entries insrc/left-nav-title.jsonand prev/next pagination fields in the frontmatter.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/pages/docs/test-management/test-capture/capture-logs.md` around lines 1 - 21, The page frontmatter lacks prev/next pagination fields and the left-nav is missing an entry; add prev and next keys to this file's frontmatter (use the existing page_id 'capture-logs' and title 'Capture Logs Using Test Capture' to determine ordering) and add a corresponding entry in src/left-nav-title.json mapping 'capture-logs' (or its title) into the appropriate section so the page appears in the left navigation; ensure the pagination values match the neighboring pages used by overview.md so links resolve correctly.
92-92:⚠️ Potential issue | 🟡 MinorFix grammar error in section heading.
The section heading has the same grammar error as flagged in the table of contents (line 19).
📝 Proposed fix
-## **Capture Logs from a Directly Website** +## **Capture Logs Directly from a Website**Also update the anchor reference in the contextual_links (line 20):
- url: '#capture-logs-from-a-directly-website' + url: '#capture-logs-directly-from-a-website'🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/pages/docs/test-management/test-capture/capture-logs.md` at line 92, Fix the grammar in the section heading "## **Capture Logs from a Directly Website**" by changing it to a correct form (e.g., "## **Capture Logs Directly from a Website**" or "## **Capture Logs from a Direct Website**") and ensure the change is applied to the heading text in capture-logs.md; then update the corresponding anchor reference used in the contextual_links entry so the link matches the new heading slug (the contextual_links key/anchor for this section).src/pages/docs/test-management/test-capture/install-and-configure.md (1)
1-33:⚠️ Potential issue | 🟠 MajorAdd navigation entries and pagination fields.
This page has the same missing navigation and pagination issue as flagged in
overview.md. The page needs entries insrc/left-nav-title.jsonand prev/next pagination fields in the frontmatter.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/pages/docs/test-management/test-capture/install-and-configure.md` around lines 1 - 33, The frontmatter for the "Install & Configure Test Capture" page is missing navigation and pagination entries: add a corresponding navigation entry to the left-nav title JSON (matching page_id 'install-test-capture-extension' and page_title/title) and add prev and next pagination fields to the page frontmatter (e.g., prev: { title: ..., url: ... } and next: { title: ..., url: ... }) so the page appears in the site navigation and has proper prev/next links; update the contextual_links/order/page_id/title fields as needed to match the new left-nav entry.
🧹 Nitpick comments (1)
src/pages/docs/test-management/test-capture/overview.md (1)
34-34: Clarify the distinction between "screen recordings" and "video logs".The introduction mentions both "screen recordings" and "video logs" as separate items. If these refer to the same thing, consider using consistent terminology throughout the document. If they're different features, add a brief clarification explaining the distinction.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/pages/docs/test-management/test-capture/overview.md` at line 34, The intro sentence in overview.md currently lists both "screen recordings" and "video logs" as if they are distinct; either use one consistent term (e.g., replace "video logs" with "screen recordings" everywhere) or explicitly clarify the difference in that sentence by adding a short parenthetical or clause (e.g., "screen recordings (a continuous video of the UI) and video logs (annotated or event-synced video files)") so readers know whether these are the same artifact or different features — update the sentence that begins "It automatically captures..." and any other occurrences to use the chosen terminology consistently or include the clarification.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/pages/docs/test-management/test-capture/capture-logs.md`:
- Line 4: Fix the typo in the frontmatter meta description: update the metadesc
value in capture-logs.md so "Tshis" is corrected to "This" (i.e., change "Tshis
article discusses..." to "This article discusses...") to ensure the descriptive
metadata is accurate.
- Around line 100-101: Replace the incorrect phrase "Instant Reply" with
"Instant Replay" in the text and update the image alt text currently reading
"Instant Reply" to "Instant Replay" (the line containing Select **Instant
Reply** and the following image markdown). Do not change the existing image
filename in the URL unless you re-upload a corrected image; if you re-upload,
update the URL accordingly and ensure both the visible text and the alt text
reflect "Instant Replay".
- Line 19: Update the title string "name: 'Capture Logs from a Directly
Website'" to correct grammar (e.g., "Capture Logs Directly from a Website" or
"Capture Logs from a Website Directly") and make the same change to the section
heading referenced in the page (the heading currently at line 92) plus update
any anchor URL(s) that use the old phrasing so they match the new title. Ensure
the exact phrase in the YAML/name field and the Markdown heading are identical
and that any internal links/anchors are updated accordingly.
In `@src/pages/docs/test-management/test-capture/install-and-configure.md`:
- Line 4: Update the frontmatter metadesc value to correct the typo by replacing
"author" with "authorize" in the metadesc string (the metadesc key shown in the
diff); ensure the new line reads: metadesc: 'Learn how to install, authorize,
and configure the Test Capture Chrome extension to execute tests and capture
logs during manual execution in Test Management by Testsigma'.
- Line 117: Replace the duplicated option label "Record Current Tab/Current Tab"
with the correct singular option name "Record Current Tab" in the markdown
content so the option matches the rest of the document.
In `@src/pages/docs/test-management/test-capture/overview.md`:
- Line 52: In the sentence "log that is captured frequently lacks sufficient
execution and technical context...", fix subject-verb agreement by replacing
"log that is captured frequently lacks" with "logs that are captured frequently
lack" (or "captured logs frequently lack") so the plural subject matches the
plural verb; update the sentence in overview.md accordingly.
- Line 26: Replace the malformed anchor URL literal
'#where-does-this-log-appear?' in the frontmatter with a valid anchor by either
removing the trailing question mark (use '#where-does-this-log-appear') or
percent-encoding it (use '#where-does-this-log-appear%3F'), updating the url
value accordingly so the navigation link works; the target string to change is
the url entry that currently equals '#where-does-this-log-appear?'.
- Around line 1-30: The left-nav JSON is missing entries for the Test Capture
docs; open src/left-nav-title.json and add three entries with keys
"test-capture-overview", "install-test-capture-extension", and "capture-logs"
mapping their respective URLs to titles (Overview: Test Capture; Install &
Configure Test Capture; Capture Logs Using Test Capture) so the pages
/docs/test-management/test-capture/overview/,
/docs/test-management/test-capture/install-and-configure/, and
/docs/test-management/test-capture/capture-logs/ appear in the left navigation.
---
Duplicate comments:
In `@src/pages/docs/test-management/test-capture/capture-logs.md`:
- Around line 1-21: The page frontmatter lacks prev/next pagination fields and
the left-nav is missing an entry; add prev and next keys to this file's
frontmatter (use the existing page_id 'capture-logs' and title 'Capture Logs
Using Test Capture' to determine ordering) and add a corresponding entry in
src/left-nav-title.json mapping 'capture-logs' (or its title) into the
appropriate section so the page appears in the left navigation; ensure the
pagination values match the neighboring pages used by overview.md so links
resolve correctly.
- Line 92: Fix the grammar in the section heading "## **Capture Logs from a
Directly Website**" by changing it to a correct form (e.g., "## **Capture Logs
Directly from a Website**" or "## **Capture Logs from a Direct Website**") and
ensure the change is applied to the heading text in capture-logs.md; then update
the corresponding anchor reference used in the contextual_links entry so the
link matches the new heading slug (the contextual_links key/anchor for this
section).
In `@src/pages/docs/test-management/test-capture/install-and-configure.md`:
- Around line 1-33: The frontmatter for the "Install & Configure Test Capture"
page is missing navigation and pagination entries: add a corresponding
navigation entry to the left-nav title JSON (matching page_id
'install-test-capture-extension' and page_title/title) and add prev and next
pagination fields to the page frontmatter (e.g., prev: { title: ..., url: ... }
and next: { title: ..., url: ... }) so the page appears in the site navigation
and has proper prev/next links; update the contextual_links/order/page_id/title
fields as needed to match the new left-nav entry.
---
Nitpick comments:
In `@src/pages/docs/test-management/test-capture/overview.md`:
- Line 34: The intro sentence in overview.md currently lists both "screen
recordings" and "video logs" as if they are distinct; either use one consistent
term (e.g., replace "video logs" with "screen recordings" everywhere) or
explicitly clarify the difference in that sentence by adding a short
parenthetical or clause (e.g., "screen recordings (a continuous video of the UI)
and video logs (annotated or event-synced video files)") so readers know whether
these are the same artifact or different features — update the sentence that
begins "It automatically captures..." and any other occurrences to use the
chosen terminology consistently or include the clarification.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 3f0949fa-304d-4942-9d61-b42705f8a718
📒 Files selected for processing (66)
src/left-nav-title.jsonsrc/pages/docs/test-management/api-reference/modules.mdsrc/pages/docs/test-management/api-reference/overview.mdsrc/pages/docs/test-management/atto/best-practices/generating-test-cases.mdsrc/pages/docs/test-management/atto/best-practices/writing-best-prompts.mdsrc/pages/docs/test-management/atto/bug-reporter-agent/report-bugs.mdsrc/pages/docs/test-management/atto/executor-agent/download.mdsrc/pages/docs/test-management/atto/executor-agent/execute-test-runs.mdsrc/pages/docs/test-management/atto/generator-agent/generate-tests-from-azure-devops.mdsrc/pages/docs/test-management/atto/generator-agent/generate-tests-from-clickup.mdsrc/pages/docs/test-management/atto/generator-agent/generate-tests-from-confluence.mdsrc/pages/docs/test-management/atto/generator-agent/generate-tests-from-figma.mdsrc/pages/docs/test-management/atto/generator-agent/generate-tests-from-files.mdsrc/pages/docs/test-management/atto/generator-agent/generate-tests-from-images.mdsrc/pages/docs/test-management/atto/generator-agent/generate-tests-from-jira.mdsrc/pages/docs/test-management/atto/generator-agent/generate-tests-from-recording.mdsrc/pages/docs/test-management/atto/generator-agent/generate-tests-with-prompts.mdsrc/pages/docs/test-management/atto/overview.mdsrc/pages/docs/test-management/atto/sprint-planner/manage-azure-devops-work-items.mdsrc/pages/docs/test-management/atto/sprint-planner/manage-clickup-tasks.mdsrc/pages/docs/test-management/atto/sprint-planner/manage-linear-cycles.mdsrc/pages/docs/test-management/atto/sprint-planner/manage-sprints.mdsrc/pages/docs/test-management/ci-cd-integrations/azure-devops.mdsrc/pages/docs/test-management/ci-cd-integrations/circleci.mdsrc/pages/docs/test-management/ci-cd-integrations/github.mdsrc/pages/docs/test-management/ci-cd-integrations/gitlab.mdsrc/pages/docs/test-management/ci-cd-integrations/jenkins.mdsrc/pages/docs/test-management/ci-cd-integrations/travis-ci.mdsrc/pages/docs/test-management/integrations/azure-devops.mdsrc/pages/docs/test-management/integrations/azure-two-way-integration/manage-test-cases-in-azure-devops.mdsrc/pages/docs/test-management/integrations/azure-two-way-integration/manage-test-runs-in-azure-devops.mdsrc/pages/docs/test-management/integrations/azure-two-way-integration/testsigma-integration-app-for-azuredevops.mdsrc/pages/docs/test-management/integrations/clickup.mdsrc/pages/docs/test-management/integrations/confluence.mdsrc/pages/docs/test-management/integrations/figma.mdsrc/pages/docs/test-management/integrations/jira-two-way-integration/install-and-connect-testsigma.mdsrc/pages/docs/test-management/integrations/jira-two-way-integration/manage-test-cases-in-jira.mdsrc/pages/docs/test-management/integrations/jira-two-way-integration/manage-test-runs-in-jira.mdsrc/pages/docs/test-management/integrations/jira.mdsrc/pages/docs/test-management/integrations/linear.mdsrc/pages/docs/test-management/manage-users/invite-users.mdsrc/pages/docs/test-management/reports/create-report.mdsrc/pages/docs/test-management/reports/dashboard-reports.mdsrc/pages/docs/test-management/reports/requirement-traceability-report.mdsrc/pages/docs/test-management/reports/view-reports.mdsrc/pages/docs/test-management/settings/api-keys.mdsrc/pages/docs/test-management/settings/audit-logs.mdsrc/pages/docs/test-management/settings/custom-fields.mdsrc/pages/docs/test-management/settings/labels.mdsrc/pages/docs/test-management/settings/manage-access.mdsrc/pages/docs/test-management/settings/manage-properties.mdsrc/pages/docs/test-management/settings/notifications/email.mdsrc/pages/docs/test-management/settings/notifications/microsoft-teams.mdsrc/pages/docs/test-management/settings/notifications/overview.mdsrc/pages/docs/test-management/settings/notifications/slack.mdsrc/pages/docs/test-management/settings/smtp-configuration.mdsrc/pages/docs/test-management/test-capture/capture-logs.mdsrc/pages/docs/test-management/test-capture/install-and-configure.mdsrc/pages/docs/test-management/test-capture/overview.mdsrc/pages/docs/test-management/testsigma-two-way-integration/automate-manual-test-cases.mdsrc/pages/docs/test-management/testsigma-two-way-integration/connect-testsigma.mdsrc/pages/docs/test-management/testsigma-two-way-integration/create-and-sync-test-cases.mdsrc/pages/docs/test-management/testsigma-two-way-integration/execute-test-plans.mdsrc/pages/docs/test-management/testsigma-two-way-integration/link-test-cases.mdsrc/pages/docs/test-management/testsigma-two-way-integration/link-test-plans.mdsrc/pages/docs/test-management/testsigma-two-way-integration/manage-user.md
| --- | ||
| title: 'Capture Logs Using Test Capture' | ||
| page_title: 'Capture Logs Using Test Capture' | ||
| metadesc: 'Test Capture lets you record execution logs during manual testing. Tshis article discusses capturing and reviewing execution evidence using Test Capture during manual test runs.' |
There was a problem hiding this comment.
Fix typo in metadesc: "Tshis" should be "This".
✏️ Proposed fix
-metadesc: 'Test Capture lets you record execution logs during manual testing. Tshis article discusses capturing and reviewing execution evidence using Test Capture during manual test runs.'
+metadesc: 'Test Capture lets you record execution logs during manual testing. This article discusses capturing and reviewing execution evidence using Test Capture during manual test runs.'📝 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
| metadesc: 'Test Capture lets you record execution logs during manual testing. Tshis article discusses capturing and reviewing execution evidence using Test Capture during manual test runs.' | |
| metadesc: 'Test Capture lets you record execution logs during manual testing. This article discusses capturing and reviewing execution evidence using Test Capture during manual test runs.' |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/pages/docs/test-management/test-capture/capture-logs.md` at line 4, Fix
the typo in the frontmatter meta description: update the metadesc value in
capture-logs.md so "Tshis" is corrected to "This" (i.e., change "Tshis article
discusses..." to "This article discusses...") to ensure the descriptive metadata
is accurate.
| name: 'View Captured Logs in Test Runs' | ||
| url: '#view-captured-logs-in-test-runs' | ||
| - type: link | ||
| name: 'Capture Logs from a Directly Website' |
There was a problem hiding this comment.
Fix grammar error in section title.
The phrase "from a Directly Website" should be "Directly from a Website" or "from a Website Directly".
📝 Proposed fix
- type: link
- name: 'Capture Logs from a Directly Website'
+ name: 'Capture Logs Directly from a Website'
url: '#capture-logs-from-a-directly-website'Note: You'll also need to update the actual section heading on line 92 and the anchor URL to match.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/pages/docs/test-management/test-capture/capture-logs.md` at line 19,
Update the title string "name: 'Capture Logs from a Directly Website'" to
correct grammar (e.g., "Capture Logs Directly from a Website" or "Capture Logs
from a Website Directly") and make the same change to the section heading
referenced in the page (the heading currently at line 92) plus update any anchor
URL(s) that use the old phrasing so they match the new title. Ensure the exact
phrase in the YAML/name field and the Markdown heading are identical and that
any internal links/anchors are updated accordingly.
Comment on lines
+100
to
+101
| 4. Select **Instant Reply**. This will open a new tab. | ||
|  |
There was a problem hiding this comment.
Fix typo: "Instant Reply" should be "Instant Replay".
The text and image alt text use "Reply" instead of "Replay". This appears throughout the section and should be corrected.
✏️ Proposed fix
-4. Select **Instant Reply**. This will open a new tab.
- 
+4. Select **Instant Replay**. This will open a new tab.
+ Note: The image filename itself contains "Reply" but changing the filename would break the link. You may want to re-upload the image with the correct filename or just update the alt text.
📝 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
| 4. Select **Instant Reply**. This will open a new tab. | |
|  | |
| 4. Select **Instant Replay**. This will open a new tab. | |
|  |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/pages/docs/test-management/test-capture/capture-logs.md` around lines 100
- 101, Replace the incorrect phrase "Instant Reply" with "Instant Replay" in the
text and update the image alt text currently reading "Instant Reply" to "Instant
Replay" (the line containing Select **Instant Reply** and the following image
markdown). Do not change the existing image filename in the URL unless you
re-upload a corrected image; if you re-upload, update the URL accordingly and
ensure both the visible text and the alt text reflect "Instant Replay".
| --- | ||
| title: 'Install & Configure Test Capture' | ||
| page_title: 'Install & Configure Test Capture Extension' | ||
| metadesc: 'Learn how to install, author, and configure the Test Capture Chrome extension to execute tests and capture logs during manual execution in Test Management by Testsigma' |
There was a problem hiding this comment.
Fix typo in metadesc: "author" should be "authorize".
The metadesc contains a typo.
✏️ Proposed fix
-metadesc: 'Learn how to install, author, and configure the Test Capture Chrome extension to execute tests and capture logs during manual execution in Test Management by Testsigma'
+metadesc: 'Learn how to install, authorize, and configure the Test Capture Chrome extension to execute tests and capture logs during manual execution in Test Management by Testsigma'📝 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
| metadesc: 'Learn how to install, author, and configure the Test Capture Chrome extension to execute tests and capture logs during manual execution in Test Management by Testsigma' | |
| metadesc: 'Learn how to install, authorize, and configure the Test Capture Chrome extension to execute tests and capture logs during manual execution in Test Management by Testsigma' |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/pages/docs/test-management/test-capture/install-and-configure.md` at line
4, Update the frontmatter metadesc value to correct the typo by replacing
"author" with "authorize" in the metadesc string (the metadesc key shown in the
diff); ensure the new line reads: metadesc: 'Learn how to install, authorize,
and configure the Test Capture Chrome extension to execute tests and capture
logs during manual execution in Test Management by Testsigma'.
|  | ||
| - **Instant Replay** | ||
| - **Take Screenshot** | ||
| - **Record Current Tab/Current Tab** |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Search for references to "Record Current Tab" to verify the correct option name
echo "=== Searching for 'Record Current Tab' references ==="
rg -i "record current tab" --type md -C 2Repository: testsigmahq/TMSDocs
Length of output: 1030
Remove redundant text from option name.
Line 117 has "Record Current Tab/Current Tab" which duplicates "Current Tab". The correct option name is "Record Current Tab" (as shown elsewhere in the document). Update line 117 to remove the duplication.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/pages/docs/test-management/test-capture/install-and-configure.md` at line
117, Replace the duplicated option label "Record Current Tab/Current Tab" with
the correct singular option name "Record Current Tab" in the markdown content so
the option matches the rest of the document.
Comment on lines
+1
to
+30
| --- | ||
| title: 'Overview: Test Capture' | ||
| page_title: 'Overview of Test Capture in Test Management by Testsigma' | ||
| metadesc: 'Test Capture runs alongside manual test execution. This article provides an overview of Test Capture in Test Management by Testsigma.' | ||
| noindex: false | ||
| order: 9.1 | ||
| page_id: 'test-capture-in-testsigma-test-management' | ||
| warning: false | ||
| contextual_links: | ||
| - type: section | ||
| name: 'Contents' | ||
| - type: link | ||
| name: 'What Test Capture Does' | ||
| url: '#what-test-capture-does' | ||
| - type: link | ||
| name: 'Problems Addressed' | ||
| url: '#problems-addressed' | ||
| - type: link | ||
| name: 'Key Capabilities' | ||
| url: '#key-capabilities' | ||
| - type: link | ||
| name: 'Captured Log Details' | ||
| url: '#captured-log-details' | ||
| - type: link | ||
| name: 'Where Does this Log Appear?' | ||
| url: '#where-does-this-log-appear?' | ||
| - type: link | ||
| name: 'Prerequisite' | ||
| url: '#prerequisite' | ||
| --- |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Verify that Test Capture pages are missing from left-nav-title.json
echo "=== Checking for Test Capture navigation entries ==="
if grep -q "test-capture" src/left-nav-title.json; then
echo "✓ Found test-capture entries"
grep "test-capture" src/left-nav-title.json
else
echo "✗ No test-capture entries found in left-nav-title.json"
fi
echo ""
echo "=== Checking for overview page entry ==="
if grep -q "test-capture-in-testsigma-test-management" src/left-nav-title.json; then
echo "✓ Found overview page entry"
else
echo "✗ Overview page entry missing"
fi
echo ""
echo "=== Checking for install page entry ==="
if grep -q "install-test-capture-extension" src/left-nav-title.json; then
echo "✓ Found install page entry"
else
echo "✗ Install page entry missing"
fi
echo ""
echo "=== Checking for capture-logs page entry ==="
if grep -q "capture-logs" src/left-nav-title.json; then
echo "✓ Found capture-logs page entry"
else
echo "✗ Capture-logs page entry missing"
fiRepository: testsigmahq/TMSDocs
Length of output: 392
🏁 Script executed:
# Check if the other two Test Capture pages exist
echo "=== Checking for Test Capture markdown files ==="
find src/pages/docs/test-management/test-capture -name "*.md" 2>/dev/null | sortRepository: testsigmahq/TMSDocs
Length of output: 296
🏁 Script executed:
# Check the structure and pattern in left-nav-title.json for test-management section
echo "=== Examining test-management entries in left-nav-title.json ==="
rg -A 2 'test-management' src/left-nav-title.json | head -50Repository: testsigmahq/TMSDocs
Length of output: 1834
🏁 Script executed:
# Check if similar documentation pages have pagination fields in their frontmatter
echo "=== Checking pagination fields in other test-management docs ==="
rg -l "^prev:|^next:" src/pages/docs/test-management --type md | head -5 | xargs -I {} sh -c 'echo "File: {}" && head -25 {}'Repository: testsigmahq/TMSDocs
Length of output: 127
🏁 Script executed:
# Check if prev/next pagination fields are used anywhere in the documentation
echo "=== Searching for prev/next fields across ALL docs ==="
rg "^prev:|^next:" src/pages/docs --type md | head -20Repository: testsigmahq/TMSDocs
Length of output: 117
🏁 Script executed:
# Check how subsection pages are handled in left-nav-title.json (e.g., test-cases and manage-test-cases)
echo "=== Checking structure for nested/subsection entries ==="
rg '"test-cases":|"manage-test-cases":' src/left-nav-title.json -A 1Repository: testsigmahq/TMSDocs
Length of output: 297
🏁 Script executed:
# Check if there are similar subsection groupings in test-management
echo "=== Looking for parent-child section patterns in test-management ==="
rg 'test-management.*test-' src/left-nav-title.json | head -20Repository: testsigmahq/TMSDocs
Length of output: 1515
Add missing navigation entries for Test Capture pages to src/left-nav-title.json.
The three Test Capture documentation pages are missing from src/left-nav-title.json, preventing them from appearing in the site's left navigation menu despite building successfully.
Add the following entries to src/left-nav-title.json:
"test-capture-overview": {
"/docs/test-management/test-capture/overview/": "Overview: Test Capture"
},
"install-test-capture-extension": {
"/docs/test-management/test-capture/install-and-configure/": "Install & Configure Test Capture"
},
"capture-logs": {
"/docs/test-management/test-capture/capture-logs/": "Capture Logs Using Test Capture"
}🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/pages/docs/test-management/test-capture/overview.md` around lines 1 - 30,
The left-nav JSON is missing entries for the Test Capture docs; open
src/left-nav-title.json and add three entries with keys "test-capture-overview",
"install-test-capture-extension", and "capture-logs" mapping their respective
URLs to titles (Overview: Test Capture; Install & Configure Test Capture;
Capture Logs Using Test Capture) so the pages
/docs/test-management/test-capture/overview/,
/docs/test-management/test-capture/install-and-configure/, and
/docs/test-management/test-capture/capture-logs/ appear in the left navigation.
| url: '#captured-log-details' | ||
| - type: link | ||
| name: 'Where Does this Log Appear?' | ||
| url: '#where-does-this-log-appear?' |
There was a problem hiding this comment.
Fix malformed anchor URL containing a question mark.
The anchor URL '#where-does-this-log-appear?' contains a literal ? character, which is a URL query delimiter and will likely break the navigation link to the corresponding heading.
🔗 Proposed fix
- type: link
name: 'Where Does this Log Appear?'
- url: '#where-does-this-log-appear?'
+ url: '#where-does-this-log-appear'Alternatively, if you want to preserve the question mark in the URL, properly encode it:
- type: link
name: 'Where Does this Log Appear?'
- url: '#where-does-this-log-appear?'
+ url: '#where-does-this-log-appear%3F'🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/pages/docs/test-management/test-capture/overview.md` at line 26, Replace
the malformed anchor URL literal '#where-does-this-log-appear?' in the
frontmatter with a valid anchor by either removing the trailing question mark
(use '#where-does-this-log-appear') or percent-encoding it (use
'#where-does-this-log-appear%3F'), updating the url value accordingly so the
navigation link works; the target string to change is the url entry that
currently equals '#where-does-this-log-appear?'.
|
|
||
| ## **Problems Addressed** | ||
|
|
||
| Manual test execution often relies on separate tools and manual steps to capture log. This leads to interrupted execution flow, missed failure moments, incomplete recordings, and repeated test execution only to collect proof. log that is captured frequently lacks sufficient execution and technical context for effective defect analysis. |
There was a problem hiding this comment.
Fix subject-verb agreement.
The phrase "log that is captured frequently lacks" should use plural form for consistency with the context.
📝 Proposed fix
-Manual test execution often relies on separate tools and manual steps to capture log. This leads to interrupted execution flow, missed failure moments, incomplete recordings, and repeated test execution only to collect proof. log that is captured frequently lacks sufficient execution and technical context for effective defect analysis.
+Manual test execution often relies on separate tools and manual steps to capture logs. This leads to interrupted execution flow, missed failure moments, incomplete recordings, and repeated test execution only to collect proof. Logs that are captured frequently lack sufficient execution and technical context for effective defect analysis.📝 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
| Manual test execution often relies on separate tools and manual steps to capture log. This leads to interrupted execution flow, missed failure moments, incomplete recordings, and repeated test execution only to collect proof. log that is captured frequently lacks sufficient execution and technical context for effective defect analysis. | |
| Manual test execution often relies on separate tools and manual steps to capture logs. This leads to interrupted execution flow, missed failure moments, incomplete recordings, and repeated test execution only to collect proof. Logs that are captured frequently lack sufficient execution and technical context for effective defect analysis. |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/pages/docs/test-management/test-capture/overview.md` at line 52, In the
sentence "log that is captured frequently lacks sufficient execution and
technical context...", fix subject-verb agreement by replacing "log that is
captured frequently lacks" with "logs that are captured frequently lack" (or
"captured logs frequently lack") so the plural subject matches the plural verb;
update the sentence in overview.md accordingly.
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
2 participants
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.
Overview: Test Capture
Install & Configure Test Capture
Capture Logs Using Test Capture
Summary by CodeRabbit
New Features
Documentation