Updated the links as per the SEO guidelines#842
Conversation
WalkthroughThis pull request performs a comprehensive documentation-wide refactoring that systematically converts plain text URLs and Markdown-style links into HTML anchor tags with Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~15 minutes Areas requiring extra attention:
Possibly related PRs
Suggested reviewers
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
Tip 📝 Customizable high-level summaries are now available in beta!You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.
Example instruction:
Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later. 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: 23
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
src/pages/docs/continuous-integration/google-cloud-build-ci.md (1)
79-96: Fix step numbering sequence — conflicting step labels.The step renumbering at line 87 creates a broken sequence with two "Step 1" entries:
- Line 79: Step 1 (Navigate to Cloud Build)
- Line 87: Step 1 (On the Connect repository overlay) — should be Step 2
- Line 93: Step 3 — should be Step 3 ✓
- Line 95: Step 4 — should be Step 4 ✓
The NOTE block (lines 82–85) sits between the two steps and is causing the sequencing issue. Correct the numbering to maintain logical flow for users following the instructions.
Apply this diff to restore correct sequence:
[[info | NOTE:]] | - Ensure the tstrigger.sh file is present in the same repository and marked as executable. For information on the generic shell script, refer to the [documentation on generic Shell script](https://testsigma.com/docs/continuous-integration/shell-script/). | - Ensure you have an API key and a Test Plan ID. For more information, refer to the [documentation on generating API keys](https://testsigma.com/docs/configuration/api-keys/) and <a href="https://docs.testsigma.com/images/azure-devops/get-test-plan-id.png" rel="nofollow">documentation on getting test plan ID</a>. | - - 1. On the **Connect repository** overlay, select your source code management provider from the list (we're selecting **GitHub**), then click **Continue**. + 2. On the **Connect repository** overlay, select your source code management provider from the list (we're selecting **GitHub**), then click **Continue**. <img src="https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/integration/Google_cloud_9.png" style="width: 400px;" /> [[info | NOTE:]] | - **Google Cloud Build** will redirect you to **GitHub**. - 3. Return to **Google Cloud Build**, and it authenticates automatically. + 3. Return to **Google Cloud Build**, and it authenticates automatically.src/pages/docs/integrations/test-management/testrail.md (1)
92-129: Restore correct step numbering in "Steps to Execute Test Plan" section.Line 128 incorrectly renumbers step 4 as step 1, breaking the sequential instruction flow:
- Step 1 (line 94): After linking test cases...
- Step 2 (line 96): In the Test Plan Settings...
- Step 3 (line 99): Enter the project name...
- Step 4 (line 128): Should be "4" but labeled as "1" — Go to Test Plans and click Run Now
This creates confusion for users following the numbered steps. Revert the renumbering.
Apply this diff:
| - Obtain valid Testsigma API Key from **Settings > API** Keys. - 1. Go to **Test Plans** and click **Run Now** to execute the test plan. This will create a duplicate of the test run and display the result once the execution is complete. + 4. Go to **Test Plans** and click **Run Now** to execute the test plan. This will create a duplicate of the test run and display the result once the execution is complete.
🧹 Nitpick comments (12)
src/pages/docs/troubleshooting/general/jenkins-xml-to-html.md (1)
68-68: Link successfully converted to HTML anchor with SEO attributes.The external GitHub repository link is now properly formatted as an HTML anchor tag with
rel="nofollow", aligning with SEO guidelines. The implementation is correct and requires no changes.Optional: Consider using a more descriptive anchor text instead of "git repo" (e.g., "Xml2HtmlPlugin repository") to improve accessibility and user experience.
src/pages/docs/genai-capabilities/generate-tests-from-figma-designs.md (1)
67-67: Inconsistent link handling across the document.Line 67 has been converted to an HTML anchor with
rel="nofollow", but Line 50 contains an external Testsigma link in Markdown format that was not converted. For consistency with the PR's stated goal of applying SEO guidelines systematically, both external links should follow the same pattern.Additionally, since the URL on Line 67 is a template/example containing the
{TEAM_ID}placeholder shown in a blockquote for reference, verify whether making it a clickable anchor is the intended behavior or if it should remain as static example text.src/pages/docs/contributing/open-source-dev-environment-setup/windows-and-intelliJ-ue.md (1)
42-92: Link text clarity issue: use descriptive labels instead of "URL".The HTML anchor tags are consistently formatted with proper
rel="nofollow"attributes across the file. However, line 92 uses a generic "URL" as link text, which reduces discoverability and user clarity. Replace with a more descriptive label.Line 92 improvement:
-Download the ANDROID, APPIUM, DRIVERS, and IOS tools from this <a href="https://github.com/testsigmahq/testsigma/releases" rel="nofollow">URL</a> +Download the ANDROID, APPIUM, DRIVERS, and IOS tools from <a href="https://github.com/testsigmahq/testsigma/releases" rel="nofollow">Testsigma releases</a>Verify that inline HTML anchor tags render correctly in the site's Markdown processor. Some static site generators require configuration to properly render HTML mixed with Markdown.
Also applies to: 188-188
src/pages/docs/contributing/open-source-dev-environment-setup/macos-and-intellij-ue.md (1)
145-145: Replace generic "URL" link text with descriptive label.Line 145 uses "URL" as link text. For consistency with documentation best practices, replace with descriptive text.
Suggested improvement:
-Download the Android, Appium, JRE, and iOS tools from this <a href="https://github.com/testsigmahq/testsigma/releases" rel="nofollow">URL</a> +Download the Android, Appium, JRE, and iOS tools from <a href="https://github.com/testsigmahq/testsigma/releases" rel="nofollow">Testsigma releases</a>src/pages/docs/contributing/open-source-dev-environment-setup/macos-and-intellij-ce.md (1)
160-160: Replace generic "URL" link text with descriptive label.Line 160 uses "URL" as link text. Improve clarity by using descriptive text that identifies what users will find at the link.
Suggested improvement:
-Download the Android, Appium, JRE, and iOS tools from this <a href="https://github.com/testsigmahq/testsigma/releases" rel="nofollow">URL</a> +Download the Android, Appium, JRE, and iOS tools from <a href="https://github.com/testsigmahq/testsigma/releases" rel="nofollow">Testsigma releases</a>src/pages/docs/configuration/generate-wda-file.md (1)
37-37: Fix capitalization of platform name in link text.The link has been correctly converted to HTML format with
rel="nofollow", but the link text contains a capitalization inconsistency. The official name of the platform is "GitHub" (capital H).-1. Download from <a href="https://github.com/appium/WebDriverAgent" rel="nofollow">Appium Github</a>. +1. Download from <a href="https://github.com/appium/WebDriverAgent" rel="nofollow">Appium GitHub</a>.This aligns with the official platform branding and improves documentation quality.
src/pages/docs/continuous-integration/rest-api.md (1)
110-110: Minor escaping inconsistency in placeholder URL. Line 110's href attribute contains escaped underscores (<RUN\_ID>) while the display text shows unescaped (<RUN_ID>). While this doesn't affect rendering, consider removing the unnecessary escaping from the href for clarity and consistency with standard HTML practices.src/pages/docs/troubleshooting/mobile-apps/mobile-recorder-actions-failures.md (1)
147-147: Fix markdown list indentation issues.The link format conversions are correct, but static analysis flags unordered list indentation issues (
markdownlint-cli2MD007) at these lines. List items in this file should have 0-space indentation but are currently indented by 1-2 spaces.For example, lines 147 and 163 should have their bullet points aligned to column 0:
- Solution + * Ping us on the chat widget... + * Email us at... - * Ping us on the chat widget... - * Email us at... * Join the Testsigma community's discord here: <a href="...">...</a>Also applies to: 163-163, 361-361, 381-381, 428-428
src/pages/docs/atto/generative-ai/byok/supported-llms/openai.md (1)
37-37: Remove extra trailing spaces on line 37.The link format conversion is correct, but there are two trailing spaces after the period (markdown line-break indicator) that should be reduced to a single space for consistency with the parallel file
src/pages/docs/genai-capabilities/byok/llms/openai.md.Apply this diff:
-1. Navigate to **OpenAI Platform > <a href="https://platform.openai.com/api-keys" rel="nofollow">API Keys</a>**. +1. Navigate to **OpenAI Platform > <a href="https://platform.openai.com/api-keys" rel="nofollow">API Keys</a>**.src/pages/docs/api/upload-files.md (1)
182-182: Address markdown table formatting issues flagged by linter.The static analysis tool reports missing trailing pipes in table rows at lines 182, 222, and 264 (MD055, table-pipe-style). While these don't break functionality, they violate the markdown style guide. Consider adding trailing pipes to maintain consistent table formatting per your markdown standards.
Also applies to: 222-222, 264-264
src/pages/docs/getting-started/setup/overview.md (1)
51-53: Address markdown linting issues with list indentation.The static analysis tool flags lines 51–53 with unordered list indentation issues (MD007). The list items are indented with 2 spaces instead of 0. This appears to be a pre-existing formatting issue in the file, but it should be resolved for consistency with markdown conventions.
Apply this fix to align all three bullet points to column 0:
- * Learn how to use, build, and extend the platform. Visit [documentation](https://testsigma.com/docs/) - * Connect with product experts on the team and in the Community on our <a href="https://discord.com/invite/5caWS7R6QX" rel="nofollow">discord</a>. - * Troubleshooting problems? Report bugs as <a href="https://github.com/testsigmahq/testsigma/issues" rel="nofollow">github issues</a>. + * Learn how to use, build, and extend the platform. Visit [documentation](https://testsigma.com/docs/) + * Connect with product experts on the team and in the Community on our <a href="https://discord.com/invite/5caWS7R6QX" rel="nofollow">discord</a>. + * Troubleshooting problems? Report bugs as <a href="https://github.com/testsigmahq/testsigma/issues" rel="nofollow">github issues</a>.src/pages/docs/test-data/types/mailbox.md (1)
57-57: Verify rel="nofollow" on internal documentation and address style concern.Three concerns in this file:
Internal link (line 57):
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_Expressionsis external and correctly marked withrel="nofollow".Table example (line 153): The regex example containing an HTML anchor is appropriate for an external example URL, though verify this is intentional within a table cell context.
Static analysis warning (line 57): LanguageTool flagged repetitive sentence beginnings. The line begins "Documentation on..." where prior context also uses "Documentation on". Consider rephrasing for variety:
- Current: "Documentation on regular expressions"
- Suggested: "Guide to regular expressions" or "Reference for regular expressions"
Consider addressing the style warning by rephrasing line 57:
- > 5. <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_Expressions" rel="nofollow">Documentation on regular expressions</a> if necessary. + > 5. <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_Expressions" rel="nofollow">Reference on regular expressions</a> if necessary.Also applies to: 153-153, 216-216
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (105)
src/pages/docs/FAQs/general/why-am-i-unable-to-download-the-xls-file-from-the-edge-browser.md(1 hunks)src/pages/docs/FAQs/general/why-does-test-execution-fail-with-the-error-no-route-to-host.md(1 hunks)src/pages/docs/FAQs/web-apps/basic-authentication.md(1 hunks)src/pages/docs/agent/update-drivers-manually.md(1 hunks)src/pages/docs/api/examples/rerun-test-cases-in-test-run.md(3 hunks)src/pages/docs/api/examples/schedule-test-plan-with-API.md(4 hunks)src/pages/docs/api/examples/update-test-case-results-using-API.md(1 hunks)src/pages/docs/api/examples/values-of-test-data-profile.md(2 hunks)src/pages/docs/api/upload-files.md(5 hunks)src/pages/docs/atto/generative-ai/byok/supported-llms/azure.md(1 hunks)src/pages/docs/atto/generative-ai/byok/supported-llms/openai.md(1 hunks)src/pages/docs/atto/generative-ai/generate-tests/apis.md(1 hunks)src/pages/docs/atto/generative-ai/integrations/figma.md(1 hunks)src/pages/docs/atto/generative-ai/integrations/jira-server.md(1 hunks)src/pages/docs/atto/generative-ai/integrations/qtest.md(1 hunks)src/pages/docs/atto/generative-ai/integrations/xray.md(1 hunks)src/pages/docs/atto/generative-ai/overview.md(2 hunks)src/pages/docs/configuration/generate-wda-file.md(1 hunks)src/pages/docs/configuration/ios-settings.md(2 hunks)src/pages/docs/configuration/security/azure-sso.md(3 hunks)src/pages/docs/configuration/security/okta-sso.md(1 hunks)src/pages/docs/continuous-integration/aws-devops.md(1 hunks)src/pages/docs/continuous-integration/aws-labmda.md(1 hunks)src/pages/docs/continuous-integration/azure-devops.md(1 hunks)src/pages/docs/continuous-integration/bamboo-ci.md(1 hunks)src/pages/docs/continuous-integration/codemagic-ci.md(2 hunks)src/pages/docs/continuous-integration/codeship-ci.md(1 hunks)src/pages/docs/continuous-integration/copado-integration.md(1 hunks)src/pages/docs/continuous-integration/github-cicd.md(3 hunks)src/pages/docs/continuous-integration/google-cloud-build-ci.md(2 hunks)src/pages/docs/continuous-integration/rest-api.md(2 hunks)src/pages/docs/contributing/open-source-dev-environment-setup/macos-and-intellij-ce.md(5 hunks)src/pages/docs/contributing/open-source-dev-environment-setup/macos-and-intellij-ue.md(5 hunks)src/pages/docs/contributing/open-source-dev-environment-setup/windows-and-intelliJ-ue.md(3 hunks)src/pages/docs/contributing/setup-dev-environment-addons.md(2 hunks)src/pages/docs/desired-capabilities/add-chrome-extension.md(1 hunks)src/pages/docs/desired-capabilities/basic-authentication-safari.md(1 hunks)src/pages/docs/desired-capabilities/most-common.md(2 hunks)src/pages/docs/desired-capabilities/set-geo-location.md(1 hunks)src/pages/docs/elements/web-apps/creating-locators-manually-strategies.md(2 hunks)src/pages/docs/elements/web-apps/shadow-dom.md(1 hunks)src/pages/docs/genai-capabilities/byok/llms/azure.md(1 hunks)src/pages/docs/genai-capabilities/byok/llms/openai.md(1 hunks)src/pages/docs/genai-capabilities/generate-tests-from-figma-designs.md(1 hunks)src/pages/docs/genai-capabilities/generate-tests-from-swagger.md(1 hunks)src/pages/docs/getting-started/introduction-cloud.md(1 hunks)src/pages/docs/getting-started/setup/downloadable-package.md(3 hunks)src/pages/docs/getting-started/setup/overview.md(1 hunks)src/pages/docs/getting-started/setup/testsigma-cloud.md(1 hunks)src/pages/docs/getting-started/testsigma-sample-apps.md(1 hunks)src/pages/docs/integrations/bug-reporting/jira.md(1 hunks)src/pages/docs/integrations/bug-reporting/mantis.md(1 hunks)src/pages/docs/integrations/bug-reporting/zepel.md(1 hunks)src/pages/docs/integrations/collaboration/google-chat.md(1 hunks)src/pages/docs/integrations/collaboration/microsoft-teams.md(1 hunks)src/pages/docs/integrations/collaboration/slack.md(1 hunks)src/pages/docs/integrations/test-labs/browserstack.md(1 hunks)src/pages/docs/integrations/test-management/clickup.md(1 hunks)src/pages/docs/integrations/test-management/linear.md(1 hunks)src/pages/docs/integrations/test-management/qtest.md(3 hunks)src/pages/docs/integrations/test-management/testrail.md(3 hunks)src/pages/docs/integrations/test-management/xray.md(4 hunks)src/pages/docs/on-premise-setup/installation-process/setup.md(1 hunks)src/pages/docs/on-premise-setup/post-installation/faqs.md(1 hunks)src/pages/docs/reports/runs/custom-pdf-report.md(1 hunks)src/pages/docs/runs/debug-test-case-failures.md(1 hunks)src/pages/docs/runs/env-config/configure-ie.md(1 hunks)src/pages/docs/runs/env-config/configure-safari.md(1 hunks)src/pages/docs/runs/executing-tests-in-private-grid.md(3 hunks)src/pages/docs/runs/test-locally-hosted-applications.md(2 hunks)src/pages/docs/salesforce-testing/connected-app.md(2 hunks)src/pages/docs/salesforce-testing/sf-test-cases.md(1 hunks)src/pages/docs/salesforce-testing/special-nlps.md(1 hunks)src/pages/docs/sdk/manage-runtime-test-data.md(1 hunks)src/pages/docs/test-cases/create-steps-restapi/adding-parameters.md(1 hunks)src/pages/docs/test-cases/create-steps-restapi/restful-api-overview.md(2 hunks)src/pages/docs/test-cases/create-test-steps/actions-and-options-recorder/multiple-webviews.md(1 hunks)src/pages/docs/test-cases/create-test-steps/overview.md(1 hunks)src/pages/docs/test-cases/manage/import-postman-to-testsigma.md(1 hunks)src/pages/docs/test-cases/step-types/if-condition.md(1 hunks)src/pages/docs/test-cases/step-types/rest-api.md(1 hunks)src/pages/docs/test-cases/step-types/while-loop.md(1 hunks)src/pages/docs/test-data/data-generators/default-list.md(3 hunks)src/pages/docs/test-data/types/mailbox.md(4 hunks)src/pages/docs/test-data/types/phone-number.md(1 hunks)src/pages/docs/test-plans/partial-test-plan-run-via-api.md(2 hunks)src/pages/docs/test-plans/supported-test-lab-types.md(1 hunks)src/pages/docs/test-step-recorder/install-chrome-extension.md(1 hunks)src/pages/docs/test-step-recorder/install-edge-extension.md(1 hunks)src/pages/docs/test-step-recorder/install-firefox-extension.md(1 hunks)src/pages/docs/troubleshooting/agent/mobile-device-not-displayed-recorder.md(1 hunks)src/pages/docs/troubleshooting/general/automating-chrome-extension.md(1 hunks)src/pages/docs/troubleshooting/general/jenkins-xml-to-html.md(1 hunks)src/pages/docs/troubleshooting/mobile-apps/capture-network-logs-in-android-app.md(1 hunks)src/pages/docs/troubleshooting/mobile-apps/failed-to-launch-test-recorder.md(2 hunks)src/pages/docs/troubleshooting/mobile-apps/finding-app-bundle-id-ios.md(1 hunks)src/pages/docs/troubleshooting/mobile-apps/mobile-recorder-actions-failures.md(5 hunks)src/pages/docs/troubleshooting/mobile-apps/why-accessibility-ids-over-others.md(1 hunks)src/pages/docs/troubleshooting/on-prem/general-issues.md(2 hunks)src/pages/docs/troubleshooting/setup/server-docker-deployment-errors.md(1 hunks)src/pages/docs/windows-automation/object-learning.md(1 hunks)src/pages/docs/windows-automation/tsr-tsrx-files.md(2 hunks)src/pages/docs/windows-lite-automation/element-learning.md(1 hunks)src/pages/docs/windows-lite-automation/introduction.md(1 hunks)src/pages/docs/windows-lite-automation/test-cases.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
src/pages/docs/agent/update-drivers-manually.md
[uncategorized] ~57-~57: The official name of this software platform is spelled with a capital “H”.
Context: ...ollow">Firefox - GeckoDriver (Hosted on Github)
* <a href="https://sites.googl...
(GITHUB)
src/pages/docs/troubleshooting/mobile-apps/capture-network-logs-in-android-app.md
[grammar] ~19-~19: Use a hyphen to join words.
Context: ...tation, apps do not trust user/admin added CAs by default. Certificates issue...
(QB_NEW_EN_HYPHEN)
src/pages/docs/continuous-integration/github-cicd.md
[uncategorized] ~26-~26: The official name of this software platform is spelled with a capital “H”.
Context: ...ow">Documentation on quickstarting with github actions. > 2. [Documentation on gen...
(GITHUB)
src/pages/docs/runs/test-locally-hosted-applications.md
[grammar] ~52-~52: Ensure spelling is correct
Context: ... addresses. For more information on IP whiltelisting, refer to the <a href="https://www.link...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
src/pages/docs/configuration/generate-wda-file.md
[uncategorized] ~37-~37: The official name of this software platform is spelled with a capital “H”.
Context: ...m/WebDriverAgent" rel="nofollow">Appium Github. 2. Open WDA Xcode Project...
(GITHUB)
src/pages/docs/getting-started/setup/testsigma-cloud.md
[style] ~44-~44: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...testsigma.com/docs/runs/adhoc-runs/). - To view results & debug errors, refer to <...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[uncategorized] ~52-~52: The official name of this software platform is spelled with a capital “H”.
Context: ...q/testsigma/discussions" rel="nofollow">Github issues - Reach out to us at [suppo...
(GITHUB)
src/pages/docs/getting-started/introduction-cloud.md
[uncategorized] ~67-~67: The official name of this software platform is spelled with a capital “H”.
Context: ...gmahq/testsigma/issues/" rel="nofollow">Github issues. - Refer to our [FAQ](https...
(GITHUB)
src/pages/docs/test-plans/supported-test-lab-types.md
[style] ~55-~55: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...ing it with Testsigma Account. You just need to integrate your Sauce Labs account with ...
(REP_NEED_TO_VB)
[style] ~59-~59: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...option only if the application that you need to test is accessible over the Internet an...
(REP_NEED_TO_VB)
[style] ~63-~63: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...on Test Lab to run your tests. You just need to integrate your Kobiton Test Lab account...
(REP_NEED_TO_VB)
[style] ~65-~65: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...option only if the application that you need to test is accessible over the Internet an...
(REP_NEED_TO_VB)
src/pages/docs/contributing/open-source-dev-environment-setup/windows-and-intelliJ-ue.md
[grammar] ~52-~52: Use a hyphen to join words.
Context: ...must install Node.js and the npm command line interface using either a Node versi...
(QB_NEW_EN_HYPHEN)
src/pages/docs/continuous-integration/codeship-ci.md
[uncategorized] ~31-~31: The official name of this software platform is spelled with a capital “H”.
Context: ..."nofollow">documentation on configuring Github as your SCM in CodeShip. > > ...
(GITHUB)
src/pages/docs/troubleshooting/on-prem/general-issues.md
[style] ~47-~47: Consider an alternative verb to strengthen your wording.
Context: ...
[[info | NOTE:]] | a. If you see any issue, refer to the following link:...
(IF_YOU_HAVE_THIS_PROBLEM)
[uncategorized] ~71-~71: The official name of this software platform is spelled with a capital “H”.
Context: ...|You can also get the specific URL from github docker-compose releases (<a href="https...
(GITHUB)
src/pages/docs/contributing/open-source-dev-environment-setup/macos-and-intellij-ce.md
[uncategorized] ~73-~73: Did you mean Apple’s computer “Mac” (= trademark, capitalized)?
Context: ... - Make sure Xcode is installed on your mac (install it via AppStore or <a href="ht...
(APPLE_PRODUCTS)
[grammar] ~73-~73: Ensure spelling is correct
Context: ...s installed on your mac (install it via AppStore or <a href="https://developer.apple.com...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
src/pages/docs/configuration/security/azure-sso.md
[grammar] ~99-~99: Use a hyphen to join words.
Context: ...lt;id>/metadata. - Sign on URL : <a href="https://id.testsigma...
(QB_NEW_EN_HYPHEN)
src/pages/docs/getting-started/setup/downloadable-package.md
[grammar] ~167-~167: Ensure spelling is correct
Context: .../ 4. Repeat the steps explained in “Step2: Run Services” section 5. Now login to ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
src/pages/docs/contributing/open-source-dev-environment-setup/macos-and-intellij-ue.md
[uncategorized] ~71-~71: Did you mean Apple’s computer “Mac” (= trademark, capitalized)?
Context: ... - Make sure Xcode is installed on your mac (install it via AppStore or <a href="ht...
(APPLE_PRODUCTS)
[grammar] ~71-~71: Ensure spelling is correct
Context: ...s installed on your mac (install it via AppStore or <a href="https://developer.apple.com...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
src/pages/docs/test-data/types/mailbox.md
[style] ~57-~57: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ide/Regular_Expressions" rel="nofollow">Documentation on regular expressions if necessary...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
src/pages/docs/atto/generative-ai/integrations/qtest.md
[grammar] ~47-~47: Ensure spelling is correct
Context: ...ge.htm" rel="nofollow">documentation on donwloading the qTest resources.* | ![Bearer To...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
src/pages/docs/desired-capabilities/add-chrome-extension.md
[uncategorized] ~38-~38: The proper noun “Chrome” (= software from Google) needs to be capitalized.
Context: ...p to the next step. 2. If you have the chrome extension folder(uncompressed) in your ...
(GOOGLE_PRODUCTS)
[uncategorized] ~38-~38: The proper noun “Chrome” (= software from Google) needs to be capitalized.
Context: ...x-crx3-format" rel="nofollow">Compiling chrome extension folder to CRX/CRX3 format...
(GOOGLE_PRODUCTS)
[uncategorized] ~40-~40: The proper noun “Chrome” (= software from Google) needs to be capitalized.
Context: ...format**. 3. If you don't have the chrome extension URL from Chrome Web Store, yo...
(GOOGLE_PRODUCTS)
🪛 markdownlint-cli2 (0.18.1)
src/pages/docs/troubleshooting/mobile-apps/failed-to-launch-test-recorder.md
111-111: Bare URL used
(MD034, no-bare-urls)
src/pages/docs/contributing/open-source-dev-environment-setup/windows-and-intelliJ-ue.md
44-44: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
50-50: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
56-56: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
src/pages/docs/getting-started/setup/overview.md
51-51: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
52-52: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
53-53: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
src/pages/docs/troubleshooting/mobile-apps/mobile-recorder-actions-failures.md
147-147: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
163-163: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
361-361: Unordered list indentation
Expected: 0; Actual: 1
(MD007, ul-indent)
381-381: Unordered list indentation
Expected: 0; Actual: 1
(MD007, ul-indent)
428-428: Unordered list indentation
Expected: 0; Actual: 1
(MD007, ul-indent)
src/pages/docs/contributing/open-source-dev-environment-setup/macos-and-intellij-ue.md
53-53: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
64-64: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
145-145: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
src/pages/docs/api/upload-files.md
182-182: Table pipe style
Expected: leading_and_trailing; Actual: leading_only; Missing trailing pipe
(MD055, table-pipe-style)
222-222: Table pipe style
Expected: leading_and_trailing; Actual: leading_only; Missing trailing pipe
(MD055, table-pipe-style)
264-264: Table pipe style
Expected: leading_and_trailing; Actual: leading_only; Missing trailing pipe
(MD055, table-pipe-style)
src/pages/docs/test-data/types/mailbox.md
196-196: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
199-199: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
src/pages/docs/atto/generative-ai/integrations/jira-server.md
56-56: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
57-57: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
58-58: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: CI
| * [Chrome - ChromeDriver (Hosted on Google Sites)](https://sites.google.com/chromium.org/driver/)<br> | ||
| * [Microsoft Internet Explorer - InternetExplorerDriver](https://www.seleniumhq.org/download/)<br> | ||
| * [Microsoft Edge - Edge Driver](https://developer.microsoft.com/en-us/microsoft-edge/tools/webdriver/)<br> | ||
| * <a href="https://github.com/mozilla/geckodriver/releases" rel="nofollow">Firefox - GeckoDriver (Hosted on Github)</a><br> |
There was a problem hiding this comment.
Fix capitalization: "Github" → "GitHub".
The official name of the platform is "GitHub" with a capital "H".
-* <a href="https://github.com/mozilla/geckodriver/releases" rel="nofollow">Firefox - GeckoDriver (Hosted on Github)</a><br>
+* <a href="https://github.com/mozilla/geckodriver/releases" rel="nofollow">Firefox - GeckoDriver (Hosted on GitHub)</a><br>📝 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.
| * <a href="https://github.com/mozilla/geckodriver/releases" rel="nofollow">Firefox - GeckoDriver (Hosted on Github)</a><br> | |
| * <a href="https://github.com/mozilla/geckodriver/releases" rel="nofollow">Firefox - GeckoDriver (Hosted on GitHub)</a><br> |
🧰 Tools
🪛 LanguageTool
[uncategorized] ~57-~57: The official name of this software platform is spelled with a capital “H”.
Context: ...ollow">Firefox - GeckoDriver (Hosted on Github)
* <a href="https://sites.googl...
(GITHUB)
🤖 Prompt for AI Agents
In src/pages/docs/agent/update-drivers-manually.md around line 57, fix the
capitalization of the platform name by changing "Github" to the correct "GitHub"
in the link text so it reads "Firefox - GeckoDriver (Hosted on GitHub)"; update
only the visible text, not the URL or attributes.
| - <a href="https://jira.yourcompany.com" rel="nofollow">https://jira.yourcompany.com</a> | ||
| - <a href="https://your-domain.atlassian.net" rel="nofollow">https://your-domain.atlassian.net</a> (for Jira Cloud, though this setup is mainly for Server/Data Center) | ||
| - <a href="http://192.168.1.100:8080" rel="nofollow">http://192.168.1.100:8080</a> (for internal/local instances) |
There was a problem hiding this comment.
Fix Markdown list indentation to comply with linting rules.
Lines 56–58 have unordered list items indented with 2 spaces, but markdownlint requires 0-space indentation for consistency. This causes linting failures (MD007 errors).
Apply this diff to correct the indentation:
**Examples:**
- - <a href="https://jira.yourcompany.com" rel="nofollow">https://jira.yourcompany.com</a>
- - <a href="https://your-domain.atlassian.net" rel="nofollow">https://your-domain.atlassian.net</a> (for Jira Cloud, though this setup is mainly for Server/Data Center)
- - <a href="http://192.168.1.100:8080" rel="nofollow">http://192.168.1.100:8080</a> (for internal/local instances)
+- <a href="https://jira.yourcompany.com" rel="nofollow">https://jira.yourcompany.com</a>
+- <a href="https://your-domain.atlassian.net" rel="nofollow">https://your-domain.atlassian.net</a> (for Jira Cloud, though this setup is mainly for Server/Data Center)
+- <a href="http://192.168.1.100:8080" rel="nofollow">http://192.168.1.100:8080</a> (for internal/local instances)📝 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.
| - <a href="https://jira.yourcompany.com" rel="nofollow">https://jira.yourcompany.com</a> | |
| - <a href="https://your-domain.atlassian.net" rel="nofollow">https://your-domain.atlassian.net</a> (for Jira Cloud, though this setup is mainly for Server/Data Center) | |
| - <a href="http://192.168.1.100:8080" rel="nofollow">http://192.168.1.100:8080</a> (for internal/local instances) | |
| - <a href="https://jira.yourcompany.com" rel="nofollow">https://jira.yourcompany.com</a> | |
| - <a href="https://your-domain.atlassian.net" rel="nofollow">https://your-domain.atlassian.net</a> (for Jira Cloud, though this setup is mainly for Server/Data Center) | |
| - <a href="http://192.168.1.100:8080" rel="nofollow">http://192.168.1.100:8080</a> (for internal/local instances) |
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)
56-56: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
57-57: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
58-58: Unordered list indentation
Expected: 0; Actual: 2
(MD007, ul-indent)
🤖 Prompt for AI Agents
In src/pages/docs/atto/generative-ai/integrations/jira-server.md around lines 56
to 58, the unordered list items are indented with two spaces which triggers
markdownlint MD007; remove the two leading spaces so each list item starts at
column 0 (no indentation) to match lint rules and re-run the linter to confirm
the MD007 error is resolved.
|
|
||
| [[info | **NOTE**:]] | ||
| | 1. You must obtain the **Bearer Token** from the **Download qTest Resources** page. *For more information on downloading the qTest resources, refer to the [documentation on donwloading the qTest resources](https://documentation.tricentis.com/qtest/od/en/content/overview/download_qtest_resources_page.htm).* | ||
| | 1. You must obtain the **Bearer Token** from the **Download qTest Resources** page. *For more information on downloading the qTest resources, refer to the <a href="https://documentation.tricentis.com/qtest/od/en/content/overview/download_qtest_resources_page.htm" rel="nofollow">documentation on donwloading the qTest resources</a>.* |
There was a problem hiding this comment.
Fix spelling error in link text.
The converted anchor tag contains a typo: "donwloading" should be "downloading".
- | 1. You must obtain the **Bearer Token** from the **Download qTest Resources** page. *For more information on downloading the qTest resources, refer to the <a href="https://documentation.tricentis.com/qtest/od/en/content/overview/download_qtest_resources_page.htm" rel="nofollow">documentation on donwloading the qTest resources</a>.*
+ | 1. You must obtain the **Bearer Token** from the **Download qTest Resources** page. *For more information on downloading the qTest resources, refer to the <a href="https://documentation.tricentis.com/qtest/od/en/content/overview/download_qtest_resources_page.htm" rel="nofollow">documentation on downloading the qTest resources</a>.*📝 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.
| | 1. You must obtain the **Bearer Token** from the **Download qTest Resources** page. *For more information on downloading the qTest resources, refer to the <a href="https://documentation.tricentis.com/qtest/od/en/content/overview/download_qtest_resources_page.htm" rel="nofollow">documentation on donwloading the qTest resources</a>.* | |
| | 1. You must obtain the **Bearer Token** from the **Download qTest Resources** page. *For more information on downloading the qTest resources, refer to the <a href="https://documentation.tricentis.com/qtest/od/en/content/overview/download_qtest_resources_page.htm" rel="nofollow">documentation on downloading the qTest resources</a>.* |
🧰 Tools
🪛 LanguageTool
[grammar] ~47-~47: Ensure spelling is correct
Context: ...ge.htm" rel="nofollow">documentation on donwloading the qTest resources.* | . | ||
| > In this Guide, we will be using GitHub as our SCM. Therefore, we need to install CodeShip App from GitHub Marketplace in our GitHub Account so that the repositories in the Github account are accessible. Refer to the <a href="https://blog.codeship.com/build-faster-with-github-and-cloudbees-codeship/" rel="nofollow">documentation on configuring Github as your SCM in CodeShip</a>. |
There was a problem hiding this comment.
Fix GitHub capitalization in link text.
Line 31 contains "Github" which should be "GitHub" per official GitHub branding guidelines.
Apply this fix:
- <a href="https://blog.codeship.com/build-faster-with-github-and-cloudbees-codeship/" rel="nofollow">documentation on configuring Github as your SCM in CodeShip</a>
+ <a href="https://blog.codeship.com/build-faster-with-github-and-cloudbees-codeship/" rel="nofollow">documentation on configuring GitHub as your SCM in CodeShip</a>📝 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.
| > In this Guide, we will be using GitHub as our SCM. Therefore, we need to install CodeShip App from GitHub Marketplace in our GitHub Account so that the repositories in the Github account are accessible. Refer to the <a href="https://blog.codeship.com/build-faster-with-github-and-cloudbees-codeship/" rel="nofollow">documentation on configuring Github as your SCM in CodeShip</a>. | |
| > In this Guide, we will be using GitHub as our SCM. Therefore, we need to install CodeShip App from GitHub Marketplace in our GitHub Account so that the repositories in the Github account are accessible. Refer to the <a href="https://blog.codeship.com/build-faster-with-github-and-cloudbees-codeship/" rel="nofollow">documentation on configuring GitHub as your SCM in CodeShip</a>. |
🧰 Tools
🪛 LanguageTool
[uncategorized] ~31-~31: The official name of this software platform is spelled with a capital “H”.
Context: ..."nofollow">documentation on configuring Github as your SCM in CodeShip. > > ...
(GITHUB)
🤖 Prompt for AI Agents
In src/pages/docs/continuous-integration/codeship-ci.md around line 31, the link
text uses "Github" which should be corrected to the proper brand capitalization
"GitHub"; update the anchor text so it reads "documentation on configuring
GitHub as your SCM in CodeShip" (leave URL and rel attribute unchanged).
| 1. <a href="https://msedgedriver.microsoft.com/ " rel="nofollow">https://msedgedriver.microsoft.com/</a>. | ||
| 2. <a href="https://github.com/mozilla/geckodriver/releases/download/ " rel="nofollow">https://github.com/mozilla/geckodriver/releases/download/</a>. |
There was a problem hiding this comment.
Remove trailing spaces from href attributes.
Lines 29 and 30 contain trailing spaces before the closing quote in the href attribute. These should be removed to ensure proper URL formatting and consistency with lines 31–32.
Apply this diff:
-1. <a href="https://msedgedriver.microsoft.com/ " rel="nofollow">https://msedgedriver.microsoft.com/</a>.
-2. <a href="https://github.com/mozilla/geckodriver/releases/download/ " rel="nofollow">https://github.com/mozilla/geckodriver/releases/download/</a>.
+1. <a href="https://msedgedriver.microsoft.com/" rel="nofollow">https://msedgedriver.microsoft.com/</a>.
+2. <a href="https://github.com/mozilla/geckodriver/releases/download/" rel="nofollow">https://github.com/mozilla/geckodriver/releases/download/</a>.📝 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.
| 1. <a href="https://msedgedriver.microsoft.com/ " rel="nofollow">https://msedgedriver.microsoft.com/</a>. | |
| 2. <a href="https://github.com/mozilla/geckodriver/releases/download/ " rel="nofollow">https://github.com/mozilla/geckodriver/releases/download/</a>. | |
| 1. <a href="https://msedgedriver.microsoft.com/" rel="nofollow">https://msedgedriver.microsoft.com/</a>. | |
| 2. <a href="https://github.com/mozilla/geckodriver/releases/download/" rel="nofollow">https://github.com/mozilla/geckodriver/releases/download/</a>. |
🤖 Prompt for AI Agents
In
src/pages/docs/FAQs/general/why-does-test-execution-fail-with-the-error-no-route-to-host.md
around lines 29 to 30, the href attributes contain an extra trailing space
before the closing quote; remove the space in each href value (e.g., change
"https://msedgedriver.microsoft.com/ " to "https://msedgedriver.microsoft.com/")
so the URLs match the formatting of lines 31–32 and are correctly formatted
without trailing spaces.
| ## **Steps to Install Edge Extension** | ||
|
|
||
| 1. Go to <a href="https://microsoftedge.microsoft.com/addons/detail/testsigma-recorder/pdgdbfedjpffcnmgedicplikkejikhif" target="_blank">Testsigma Recorder</a> | ||
| 1. Go to <a href="https://microsoftedge.microsoft.com/addons/detail/testsigma-recorder/pdgdbfedjpffcnmgedicplikkejikhif" rel="nofollow">Testsigma Recorder</a> |
There was a problem hiding this comment.
Add missing period for consistency.
Steps 1 in both the Firefox and Chrome extension pages end with periods, but this step is missing one. Maintain consistent punctuation across all three browser extension pages.
Apply this diff to add the period:
-1. Go to <a href="https://microsoftedge.microsoft.com/addons/detail/testsigma-recorder/pdgdbfedjpffcnmgedicplikkejikhif" rel="nofollow">Testsigma Recorder</a>
+1. Go to <a href="https://microsoftedge.microsoft.com/addons/detail/testsigma-recorder/pdgdbfedjpffcnmgedicplikkejikhif" rel="nofollow">Testsigma Recorder</a>.📝 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.
| 1. Go to <a href="https://microsoftedge.microsoft.com/addons/detail/testsigma-recorder/pdgdbfedjpffcnmgedicplikkejikhif" rel="nofollow">Testsigma Recorder</a> | |
| 1. Go to <a href="https://microsoftedge.microsoft.com/addons/detail/testsigma-recorder/pdgdbfedjpffcnmgedicplikkejikhif" rel="nofollow">Testsigma Recorder</a>. |
🤖 Prompt for AI Agents
In src/pages/docs/test-step-recorder/install-edge-extension.md around line 28,
the step text linking to the Testsigma Recorder is missing a trailing period;
update the sentence "Go to <a
href=\"https://microsoftedge.microsoft.com/addons/detail/testsigma-recorder/pdgdbfedjpffcnmgedicplikkejikhif\"
rel=\"nofollow\">Testsigma Recorder</a>" to end with a period so punctuation is
consistent with the Firefox and Chrome pages.
| ## **Add Testsigma Recorder Extension to Firefox** | ||
|
|
||
| 1. Open your **Firefox** browser and navigate to [Testsigma Recorder](https://addons.mozilla.org/en-US/firefox/). | ||
| 1. Open your **Firefox** browser and navigate to <a href="https://addons.mozilla.org/en-US/firefox/" rel="nofollow">Testsigma Recorder</a>. |
There was a problem hiding this comment.
Critical: Firefox addon link is broken and directs to wrong page.
The correct Firefox addon URL for Testsigma Recorder is https://addons.mozilla.org/en-US/firefox/addon/testsigma-recorder/, but the current link points to the generic Firefox store homepage. Users will not find the extension.
Apply this diff to correct the URL:
-1. Open your **Firefox** browser and navigate to <a href="https://addons.mozilla.org/en-US/firefox/" rel="nofollow">Testsigma Recorder</a>.
+1. Open your **Firefox** browser and navigate to <a href="https://addons.mozilla.org/en-US/firefox/addon/testsigma-recorder/" rel="nofollow">Testsigma Recorder</a>.📝 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.
| 1. Open your **Firefox** browser and navigate to <a href="https://addons.mozilla.org/en-US/firefox/" rel="nofollow">Testsigma Recorder</a>. | |
| 1. Open your **Firefox** browser and navigate to <a href="https://addons.mozilla.org/en-US/firefox/addon/testsigma-recorder/" rel="nofollow">Testsigma Recorder</a>. |
🤖 Prompt for AI Agents
In src/pages/docs/test-step-recorder/install-firefox-extension.md around line
31, the Firefox addon hyperlink points to the generic Firefox addons homepage
instead of the Testsigma Recorder add-on; update the anchor href to the correct
URL https://addons.mozilla.org/en-US/firefox/addon/testsigma-recorder/ so the
link directs users straight to the Testsigma Recorder extension page.
| --- | ||
|
|
||
| If your Android application is not capturing network logs or is showing invalid certificate errors, it may be due to missing proxy certificates or security configurations. As per [Android’s official documentation](https://android-developers.googleblog.com/2016/07/changes-to-trusted-certificate.html), apps do not trust user/admin added CAs by default. Certificates issued by these authorities are rejected, which prevents the app from capturing network traffic and can cause errors when using self-signed certificates. This article discusses steps to enable network logging on Android devices correctly. | ||
| If your Android application is not capturing network logs or is showing invalid certificate errors, it may be due to missing proxy certificates or security configurations. As per <a href="https://android-developers.googleblog.com/2016/07/changes-to-trusted-certificate.html" rel="nofollow">Android’s official documentation</a>, apps do not trust user/admin added CAs by default. Certificates issued by these authorities are rejected, which prevents the app from capturing network traffic and can cause errors when using self-signed certificates. This article discusses steps to enable network logging on Android devices correctly. |
There was a problem hiding this comment.
Minor: Use a hyphen to join compound adjectives.
The phrase "user/admin added CAs" should use a hyphen to join the adjective: "user-admin-added CAs" or "user- and admin-added CAs" for improved readability.
Apply this diff to fix the grammar:
-If your Android application is not capturing network logs or is showing invalid certificate errors, it may be due to missing proxy certificates or security configurations. As per <a href="https://android-developers.googleblog.com/2016/07/changes-to-trusted-certificate.html" rel="nofollow">Android's official documentation</a>, apps do not trust user/admin added CAs by default.
+If your Android application is not capturing network logs or is showing invalid certificate errors, it may be due to missing proxy certificates or security configurations. As per <a href="https://android-developers.googleblog.com/2016/07/changes-to-trusted-certificate.html" rel="nofollow">Android's official documentation</a>, apps do not trust user- and admin-added CAs by default.📝 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.
| If your Android application is not capturing network logs or is showing invalid certificate errors, it may be due to missing proxy certificates or security configurations. As per <a href="https://android-developers.googleblog.com/2016/07/changes-to-trusted-certificate.html" rel="nofollow">Android’s official documentation</a>, apps do not trust user/admin added CAs by default. Certificates issued by these authorities are rejected, which prevents the app from capturing network traffic and can cause errors when using self-signed certificates. This article discusses steps to enable network logging on Android devices correctly. | |
| If your Android application is not capturing network logs or is showing invalid certificate errors, it may be due to missing proxy certificates or security configurations. As per <a href="https://android-developers.googleblog.com/2016/07/changes-to-trusted-certificate.html" rel="nofollow">Android's official documentation</a>, apps do not trust user- and admin-added CAs by default. Certificates issued by these authorities are rejected, which prevents the app from capturing network traffic and can cause errors when using self-signed certificates. This article discusses steps to enable network logging on Android devices correctly. |
🧰 Tools
🪛 LanguageTool
[grammar] ~19-~19: Use a hyphen to join words.
Context: ...tation, apps do not trust user/admin added CAs by default. Certificates issue...
(QB_NEW_EN_HYPHEN)
🤖 Prompt for AI Agents
In
src/pages/docs/troubleshooting/mobile-apps/capture-network-logs-in-android-app.md
around line 19, the phrase "user/admin added CAs" should be corrected to use a
hyphenated compound adjective; replace it with either "user-admin-added CAs" or
the clearer "user- and admin-added CAs" so the adjective properly modifies "CAs"
and improves readability.
|
|
||
| [[info | **NOTE**:]] | ||
| |You can also get the specific URL from github docker-compose releases (https://github.com/docker/compose/releases). | ||
| |You can also get the specific URL from github docker-compose releases (<a href="https://github.com/docker/compose/releases" rel="nofollow">https://github.com/docker/compose/releases</a>). |
There was a problem hiding this comment.
Correct "github" capitalization to "GitHub".
The official product name is "GitHub" (with capital H).
Apply this diff:
-|You can also get the specific URL from github docker-compose releases (<a href="https://github.com/docker/compose/releases" rel="nofollow">https://github.com/docker/compose/releases</a>).
+|You can also get the specific URL from GitHub docker-compose releases (<a href="https://github.com/docker/compose/releases" rel="nofollow">https://github.com/docker/compose/releases</a>).Also applies to: 71-71
🧰 Tools
🪛 LanguageTool
[uncategorized] ~71-~71: The official name of this software platform is spelled with a capital “H”.
Context: ...|You can also get the specific URL from github docker-compose releases (<a href="https...
(GITHUB)
🤖 Prompt for AI Agents
In src/pages/docs/troubleshooting/on-prem/general-issues.md around line 71, the
word "github" is incorrectly lowercased in the sentence; change it to the
correct product name "GitHub" (preserve the existing URL and link text), and
scan the same line for any other occurrences of "github" to replace with
"GitHub" to maintain proper capitalization.
|
|
||
|
|
There was a problem hiding this comment.
Remove excessive blank lines before section heading.
Lines 27–28 contain two consecutive blank lines before the "Steps to Convert TSR Files to TSRx" section heading. Standard Markdown formatting typically uses only one blank line before section headings. Consider removing one of these blank lines for consistency.
Apply this diff:
ℹ️ For more information, refer to the <a href="https://admhelp.microfocus.com/uft/en/23.4-24.2/UFT_Help/Content/User_Guide/z_Ch_TestObjModel.htm" rel="nofollow">object model</a> and <a href="https://admhelp.microfocus.com/uft/en/23.4-24.2/UFT_Help/Content/User_Guide/Spy.htm" rel="nofollow">object spy</a>.
- ---
-
-
## **Steps to Convert TSR Files to TSRx**Note: If the --- (horizontal rule) is intentional, keep it; otherwise remove it as well.
Committable suggestion skipped: line range outside the PR's diff.
🤖 Prompt for AI Agents
In src/pages/docs/windows-automation/tsr-tsrx-files.md around lines 27–28, there
are two consecutive blank lines immediately before the "Steps to Convert TSR
Files to TSRx" heading; remove one of the blank lines so only a single blank
line precedes the heading (or if the horizontal rule `---` was intended, remove
the extra blank line but keep the `---`), then save the file.
2 participants
Updated the links as per the SEO guidelines for the ticket https://testsigma.atlassian.net/browse/DOC-351
Summary by CodeRabbit