App Testing

75
Total Pages
60
Linux-Friendly Pages
15
Pages with Bias
20.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

99 issues found
Showing 76-99 of 99 flagged pages
App Testing Quickstart: Automate load tests with CI/CD ...-testing/load-testing/quickstart-add-load-test-cicd.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exclusively describes automating load tests using Azure Pipelines and the Azure portal, with all examples and screenshots focused on Azure DevOps (a Microsoft-centric tool). There are no examples or guidance for Linux-native CI/CD tools (e.g., Jenkins, GitLab CI), nor are there any command-line or YAML examples that would be platform-agnostic. The only mention of alternatives is a brief link to a separate page for GitHub Actions, but no Linux-specific tooling or patterns are discussed.
Recommendations
  • Add explicit examples for configuring CI/CD pipelines using Linux-native tools such as Jenkins, GitLab CI, or Travis CI.
  • Provide platform-agnostic YAML or CLI examples that can be used outside of Azure DevOps, including on Linux systems.
  • Include guidance for running load tests from Linux command line (e.g., using Azure CLI, Bash scripts) and integrating with non-Microsoft CI/CD platforms.
  • Balance screenshots and walkthroughs by showing both Azure DevOps (Windows-centric) and at least one Linux-friendly CI/CD tool.
  • Clarify which steps are platform-independent and which are specific to Azure DevOps, and offer alternatives where possible.
GitHub Create Pull Request
App Testing Manage workspace access ...laywright-workspaces/how-to-manage-workspace-access.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes managing workspace access using the Azure portal, which is a web-based GUI commonly associated with Windows environments. There are no examples or instructions for managing access via command-line tools such as Azure CLI, PowerShell, or REST API, which are cross-platform and especially relevant for Linux users. All screenshots and step-by-step instructions are focused on the Azure portal interface, with no mention of Linux-specific workflows or tools.
Recommendations
  • Add equivalent instructions for managing workspace access using Azure CLI commands, which are cross-platform and widely used on Linux.
  • Include examples for using Azure PowerShell and REST API, and clarify their platform compatibility.
  • Explicitly mention that the Azure portal is accessible from any OS/browser, but provide parity for users who prefer or require command-line or automated approaches.
  • Add troubleshooting and workflow notes relevant to Linux environments, such as shell scripting or integration with Linux-based CI/CD pipelines.
GitHub Create Pull Request
App Testing Quickstart: Perform advanced diagnostics with Playwright Workspaces reporting ...vanced-diagnostic-with-playwright-workspaces-reporting.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal (web UI) for all configuration steps, which is most commonly accessed from Windows environments. There are no examples of command-line or automation steps using Linux-native tools (such as Bash scripts or CLI commands beyond Azure CLI login), nor are there any screenshots or instructions for Linux desktop environments. The only CLI example provided is 'az login', which is cross-platform, but there are no Linux-specific instructions (e.g., environment variable setting via Bash, or alternative editors for config files). Visual Studio Code is referenced as the IDE, which is cross-platform, but no mention is made of Linux-specific usage patterns or alternatives. All instructions and screenshots implicitly assume a Windows workflow and UI.
Recommendations
  • Add explicit Linux/Bash examples for setting environment variables (e.g., export PLAYWRIGHT_SERVICE_URL=...) and running Playwright commands.
  • Include instructions or screenshots for configuring resources using Azure CLI or ARM templates, which are platform-agnostic and preferred in Linux environments.
  • Mention Linux-native editors (e.g., nano, vim) for editing configuration files, or provide generic instructions.
  • Clarify that the Azure portal and Visual Studio Code are cross-platform, and provide tips for Linux users (such as keyboard shortcuts or troubleshooting).
  • Ensure that all CLI commands are shown in a way that works on both Windows and Linux shells, or provide separate tabs for each platform where necessary.
GitHub Create Pull Request
App Testing Manage workspace access ...laywright-workspaces/how-to-manage-workspace-access.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes managing workspace access via the Azure portal, which is a web-based GUI and does not mention any CLI-based or automation-friendly methods. There are no examples using cross-platform tools such as Azure CLI, nor are there PowerShell-specific instructions. However, the documentation implicitly favors Windows users by only referencing the Azure portal and not providing Linux-friendly or command-line alternatives, which are commonly used on Linux and macOS systems.
Recommendations
  • Add examples for managing workspace access using Azure CLI, which is cross-platform and widely used on Linux and macOS.
  • Include instructions for using Azure PowerShell for users who prefer scripting, but ensure Azure CLI examples are presented first or alongside PowerShell.
  • Explicitly mention that all steps can be performed on any OS via the Azure portal, but highlight CLI alternatives for automation and Linux parity.
  • Provide sample commands for role assignment and revocation using Azure CLI (e.g., az role assignment create/remove), and link to relevant CLI documentation.
GitHub Create Pull Request
App Testing Quickstart: Automate load tests with CI/CD ...-testing/load-testing/quickstart-add-load-test-cicd.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exclusively describes automating load tests using Azure Pipelines, which is tightly integrated with Azure DevOps—a platform historically and predominantly used in Windows-centric environments. All examples, screenshots, and instructions focus on Azure Pipelines and the Azure portal, with no mention of Linux-specific tools, shell commands, or alternative CI/CD platforms (except for a brief link to GitHub Actions). There are no examples using Linux shell, Bash, or cross-platform CLI tools, nor is there guidance for users who may prefer open-source or Linux-native CI/CD solutions.
Recommendations
  • Provide parallel examples for configuring CI/CD pipelines using Linux shell scripts, Bash, or cross-platform CLI tools.
  • Include explicit instructions and screenshots for integrating Azure Load Testing with popular Linux-friendly CI/CD platforms such as Jenkins, GitLab CI, or Travis CI.
  • Add YAML pipeline examples that demonstrate usage from both Windows and Linux build agents.
  • Highlight any platform-agnostic steps and clarify where platform-specific differences may occur.
  • Ensure that references to tools, permissions, and setup steps are not solely focused on Azure DevOps, but also mention alternatives for Linux/open-source environments.
GitHub Create Pull Request
App Testing Quickstart: Perform advanced diagnostics with Playwright Workspaces reporting ...vanced-diagnostic-with-playwright-workspaces-reporting.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily by referencing the Azure portal (a web interface, but often associated with Windows workflows), and by omitting explicit Linux/macOS CLI or shell examples. All instructions for environment setup, authentication, and running tests use generic commands (npm, az login, npx playwright), but do not show Linux/macOS-specific shell syntax, nor do they mention platform differences (e.g., environment variable setting, file paths, or shell commands). Visual Studio Code is referenced without noting cross-platform usage, and screenshots and instructions are tailored to the Azure portal UI, which is platform-agnostic but often perceived as Windows-centric. No PowerShell-specific commands are present, but the lack of Linux-specific examples or notes constitutes a subtle bias.
Recommendations
  • Add explicit Linux/macOS shell examples for environment variable setup (e.g., export PLAYWRIGHT_SERVICE_URL=...), and note differences in .env file handling if any.
  • Include instructions or screenshots for running commands in Linux/macOS terminals (e.g., bash/zsh), especially for Azure CLI and npm commands.
  • Clarify that Visual Studio Code and Azure CLI are cross-platform, and provide links or notes for installation on Linux/macOS.
  • Where file paths or configuration files are referenced, note any platform-specific differences (e.g., path separators, permissions).
  • Add troubleshooting tips for Linux/macOS users, such as handling permissions or dependencies.
GitHub Create Pull Request
App Testing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/playwright-workspaces/quickstart-advanced-diagnostic-with-playwright-workspaces-reporting.md ...vanced-diagnostic-with-playwright-workspaces-reporting.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently references the Azure portal and Visual Studio Code, both of which are commonly used on Windows but are available cross-platform. However, there is a notable absence of Linux-specific instructions, examples, or screenshots. All CLI examples use generic commands (npm, az, npx) that work on both Windows and Linux, but there are no explicit Linux shell or environment setup examples, nor any mention of Linux-specific considerations. The tip for opening a new browser tab uses the Windows-centric 'Ctrl' key notation, without mentioning Linux or macOS equivalents. There is no mention of PowerShell, but the documentation implicitly assumes a Windows-first workflow by omitting Linux alternatives and not addressing cross-platform differences.
Recommendations
  • Add explicit Linux/macOS instructions for environment variable setup (e.g., export PLAYWRIGHT_SERVICE_URL=...) and authentication steps.
  • Include Linux/macOS keyboard shortcut equivalents alongside Windows ones (e.g., 'Ctrl' vs 'Cmd').
  • Provide screenshots or notes for Azure portal usage on Linux/macOS browsers.
  • Clarify that all CLI commands are cross-platform, and note any OS-specific differences if applicable.
  • Add troubleshooting tips for common Linux/macOS issues (e.g., file permissions, npm installation).
GitHub Create Pull Request
App Testing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/playwright-workspaces/how-to-manage-workspace-access.md ...laywright-workspaces/how-to-manage-workspace-access.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes managing access to Playwright Workspaces via the Azure portal, which is a web-based GUI. There are no CLI examples (such as Azure CLI, PowerShell, or Bash), nor are there instructions for managing access from Linux or cross-platform command-line tools. The workflow assumes use of the Azure portal, which is most commonly accessed from Windows environments, and does not mention or provide parity for Linux users or automation scenarios.
Recommendations
  • Add Azure CLI examples for role assignment and revocation, which work cross-platform (Windows, Linux, macOS).
  • Include PowerShell examples if relevant, but ensure Azure CLI (bash/zsh) is presented first or alongside PowerShell.
  • Explicitly mention that all steps can be performed from any OS using the Azure portal, but highlight CLI alternatives for automation and Linux users.
  • Provide links to Azure CLI documentation for RBAC management.
  • Add troubleshooting notes relevant to CLI usage (e.g., authentication, role propagation delays).
GitHub Create Pull Request
App Testing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/load-testing/quickstart-add-load-test-cicd.md ...-testing/load-testing/quickstart-add-load-test-cicd.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on Azure Pipelines and Azure DevOps, which are traditionally more Windows-centric tools. All examples and screenshots are from the Azure portal and Azure DevOps UI, with no mention of Linux-specific tools, shell commands, or cross-platform considerations. There are no CLI or script examples (PowerShell, Bash, etc.), and the workflow assumes use of the Azure portal and Azure DevOps, which are often used in Windows environments. Linux users or those using open-source CI/CD tools (other than a brief mention of GitHub Actions) are not provided with equivalent guidance or examples.
Recommendations
  • Add explicit examples for configuring CI/CD pipelines using Linux-based tools (e.g., Bash scripts, Azure CLI, YAML for GitHub Actions, etc.).
  • Include screenshots or instructions for using the Azure CLI or other cross-platform interfaces to set up load tests and pipelines.
  • Provide parity for open-source CI/CD platforms (GitHub Actions, Jenkins, GitLab CI) with step-by-step instructions and sample configuration files.
  • Clarify which steps are platform-agnostic and which may require adaptation for Linux environments.
  • Reference Linux shell commands and tools where appropriate, and avoid assuming use of Windows-only interfaces.
GitHub Create Pull Request
App Testing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/playwright-workspaces/quickstart-advanced-diagnostic-with-playwright-workspaces-reporting.md ...vanced-diagnostic-with-playwright-workspaces-reporting.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently references the Azure portal and Visual Studio Code, both of which are commonly associated with Windows environments. All screenshots and step-by-step instructions are tailored to the Azure portal UI, with no mention of Linux-native tools or alternatives. There are no examples of CLI commands for Linux-specific shells (e.g., bash), nor are there instructions for using non-GUI tools or Linux desktop environments. The authentication section only mentions Azure CLI but does not provide Linux-specific installation or usage notes. There are no PowerShell-specific commands, but the overall workflow assumes a Windows-centric approach.
Recommendations
  • Add explicit instructions and screenshots for Linux users, such as using Azure CLI in bash/zsh terminals.
  • Include notes on installing and running Azure CLI on Linux distributions.
  • Mention alternative editors (e.g., Vim, VS Code on Linux) and provide parity in instructions.
  • Clarify that the steps and tools are cross-platform where applicable, and highlight any differences for Linux users.
  • Provide sample commands for setting environment variables in Linux (e.g., export PLAYWRIGHT_SERVICE_URL=...) alongside Windows instructions.
GitHub Create Pull Request
App Testing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/load-testing/quickstart-add-load-test-cicd.md ...-testing/load-testing/quickstart-add-load-test-cicd.md
Medium Priority View Details →
Scanned: 2025-09-08 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on Azure Pipelines and the Azure portal workflow, with all UI and process examples tailored to the Azure DevOps ecosystem. There are no references to command-line operations, scripting, or tooling that would be specific to either Windows or Linux, but the workflow assumes the use of Azure DevOps, which is more commonly associated with Windows-centric environments. There are no Linux-specific examples, nor is there mention of cross-platform CLI alternatives. The only mention of alternatives is a link to a separate guide for GitHub Actions, but no Linux/Unix shell or cross-platform scripting is shown or referenced.
Recommendations
  • Include examples or references for configuring CI/CD pipelines using cross-platform tools such as the Azure CLI, Bash scripts, or YAML files that can be used on both Windows and Linux.
  • Add explicit Linux/Unix shell command examples for common tasks (e.g., using Azure CLI to trigger load tests, manage service connections, or download artifacts).
  • Clarify that the Azure Pipelines and Azure DevOps workflows are cross-platform and can be used from Linux environments, or provide guidance for Linux users.
  • Provide parity in screenshots or instructions for users accessing Azure DevOps and Azure portal from Linux systems (e.g., using browser-based workflows, CLI alternatives).
  • Where possible, include a section or callout for Linux users, highlighting any differences or additional steps required.
GitHub Create Pull Request
App Testing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/load-testing/how-to-create-notification-rules.md ...sting/load-testing/how-to-create-notification-rules.md
Medium Priority View Details →
Scanned: 2025-09-08 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes configuring notifications via the Azure portal UI, with all screenshots and instructions referencing the web interface. There are no command-line examples, nor are there any references to scripting or automation using CLI tools such as Azure CLI, PowerShell, or Bash. However, the absence of any CLI examples means that if users wish to automate notification configuration, there is no guidance for either Windows (PowerShell) or Linux (Bash) users. The documentation implicitly assumes portal-based (GUI) usage, which is more common among Windows users, and does not address Linux-centric workflows or tools.
Recommendations
  • Add examples for configuring notifications using the Azure CLI, which is cross-platform and works on both Windows and Linux.
  • If PowerShell examples are provided, ensure equivalent Bash or Azure CLI examples are also included.
  • Explicitly mention that all steps can be performed from any OS via the Azure portal, but provide automation/scripting guidance for users who prefer command-line workflows.
  • Include references or links to documentation for automating notification configuration using ARM templates, Bicep, or Terraform, which are platform-agnostic.
  • Ensure screenshots and instructions do not assume a particular OS or desktop environment.
GitHub Create Pull Request
App Testing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/load-testing/how-to-move-between-resource-groups-subscriptions.md ...g/how-to-move-between-resource-groups-subscriptions.md
Medium Priority View Details →
Scanned: 2025-09-08 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation only describes how to move Azure Load Testing resources using the Azure portal, a web-based GUI tool. There are no command-line examples or automation instructions for either Windows (PowerShell) or Linux (CLI), but the lack of Azure CLI (cross-platform) or Bash examples means Linux users are not directly supported. The only automation tools mentioned are ARM templates and Bicep, which are cross-platform but not interactive. The absence of Azure CLI or Bash examples constitutes a subtle bias toward Windows-centric, GUI-based workflows.
Recommendations
  • Add Azure CLI examples for moving resources, as the CLI is cross-platform and widely used on Linux.
  • Include Bash script snippets for common automation scenarios.
  • Explicitly mention that the Azure portal is accessible from any OS, but provide parity with command-line instructions.
  • If PowerShell examples are added in the future, ensure equivalent Bash/Azure CLI examples are also provided.
GitHub Create Pull Request
App Testing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/load-testing/quickstart-add-load-test-cicd.md ...-testing/load-testing/quickstart-add-load-test-cicd.md
Medium Priority View Details →
Scanned: 2025-08-08 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on Azure Pipelines and the Azure portal, with all instructions and screenshots based on the web UI. There are no command-line examples, but the workflow implicitly assumes a Windows-centric environment by referencing Azure DevOps and omitting any mention of Linux, macOS, or cross-platform CLI alternatives. There are no references to Powershell or Windows-specific tools, but Linux users are not provided with parity guidance or examples. The only nod to alternatives is a link to a separate guide for GitHub Actions, which is not integrated into the main flow.
Recommendations
  • Include explicit instructions or examples for configuring CI/CD pipelines using cross-platform tools such as the Azure CLI, Bash scripts, or YAML files that can be run on Linux or macOS agents.
  • Provide parity examples for Linux environments, such as how to trigger or manage load tests from a Linux shell or using platform-agnostic tools.
  • Mention and demonstrate how to use self-hosted Linux agents in Azure Pipelines for running load tests.
  • Integrate references to GitHub Actions and other CI/CD platforms more directly in the main flow, not just as a 'next steps' or separate guide.
  • Clarify that the instructions are platform-agnostic if that is the case, or explicitly state any platform dependencies.
GitHub Create Pull Request
App Testing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/load-testing/how-to-optimize-azure-functions.md ...esting/load-testing/how-to-optimize-azure-functions.md
Medium Priority View Details →
Scanned: 2025-08-08 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively describes using the Azure portal (a web UI) for all actions, with no mention of command-line or scripting alternatives. There are no CLI, PowerShell, or Bash examples, and no references to Linux-native tools or workflows. This can disadvantage Linux users who often prefer or require CLI-based automation and scripting. The documentation implicitly assumes a GUI-first workflow, which is more common in Windows-centric environments.
Recommendations
  • Add equivalent instructions for using the Azure CLI (az), which is cross-platform and commonly used on Linux.
  • Provide Bash shell script examples for automating test profile creation and load test execution.
  • Explicitly mention that all steps can be performed from any OS via the Azure portal, but highlight CLI alternatives for Linux users.
  • If PowerShell examples are added in the future, ensure Bash or Azure CLI equivalents are provided alongside.
  • Reference relevant documentation for using Azure Load Testing and Azure Functions from the command line, not just the portal.
GitHub Create Pull Request
App Testing Configure customer-managed keys for encryption ...load-testing/how-to-configure-customer-managed-keys.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents examples for Azure portal, PowerShell, and Azure CLI in all major sections. However, PowerShell examples are consistently shown before Azure CLI, and there is no mention of Bash, Linux shell, or macOS-specific guidance. While Azure CLI is cross-platform, the ordering and emphasis on PowerShell (a Windows-centric tool) may create a perception of Windows bias. There are no explicit Windows-only tools, but the documentation does not acknowledge Linux/macOS environments or provide parity tips for those platforms.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more commonly used on Linux/macOS.
  • Explicitly mention that Azure CLI commands work on Linux/macOS and Windows, and provide installation links for those platforms.
  • Add brief notes or links for Linux/macOS users on how to install and use Azure CLI.
  • Consider including Bash script examples for automation, or at least acknowledge their use.
  • Add a statement clarifying that PowerShell Core is available on Linux/macOS, if relevant.
GitHub Create Pull Request
App Testing Quickstart: Run Playwright tests at scale ...aywright-workspaces/quickstart-run-end-to-end-tests.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates mild Windows bias by prioritizing Windows-centric tools and workflows. The Azure portal is referenced as the primary method for resource creation and management, which is most commonly used on Windows. Visual Studio Code is highlighted as the main IDE for running and debugging tests, and the .NET/NUnit runner examples use PowerShell and dotnet CLI commands, which are more familiar to Windows users. There are no explicit Linux/macOS terminal examples (e.g., bash, zsh), nor are alternative Linux-native tools or workflows mentioned. The documentation does not provide parity for Linux/macOS users in terms of command-line examples or environment setup.
Recommendations
  • Add explicit Linux/macOS terminal examples alongside Windows/PowerShell commands, especially for .NET/NUnit runner sections.
  • Include instructions for using the Azure CLI to create and manage Playwright Workspaces, as an alternative to the Azure portal.
  • Mention Linux/macOS compatible editors (e.g., VS Code, Vim, JetBrains IDEs) and provide instructions for running tests in those environments.
  • Clarify that all CLI commands (npm, npx, dotnet) work on Linux/macOS and provide sample outputs from those platforms.
  • Add troubleshooting tips for Linux/macOS users, such as file permission issues or environment variable setup differences.
GitHub Create Pull Request
App Testing Quickstart: Perform advanced diagnostics with Playwright Workspaces reporting ...vanced-diagnostic-with-playwright-workspaces-reporting.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently references the Azure portal and Visual Studio Code, which are cross-platform, but does not provide any Windows-specific commands or PowerShell examples. However, there is a subtle Windows bias in the instructions and screenshots: all UI navigation tips use Windows-style terminology (e.g., 'Ctrl' for keyboard shortcuts), and there are no explicit Linux/macOS terminal or shell examples, nor any mention of platform-specific differences for Azure CLI or environment variable setup. The order of presentation (e.g., 'Ctrl' for opening tabs) and lack of Linux/macOS-specific tips or screenshots may create minor friction for non-Windows users.
Recommendations
  • Include Linux/macOS-specific instructions or tips where relevant (e.g., use 'Cmd' for macOS keyboard shortcuts alongside 'Ctrl').
  • Add notes or examples showing Azure CLI usage in Bash/zsh, especially for environment variable setup.
  • Ensure screenshots and UI navigation tips are not exclusively Windows-centric.
  • Explicitly state that all CLI commands work on Linux/macOS, and mention any platform-specific caveats if they exist.
GitHub Create Pull Request
App Testing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/load-testing/how-to-optimize-azure-functions.md ...esting/load-testing/how-to-optimize-azure-functions.md
Low Priority View Details →
Scanned: 2025-09-08 00:00
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation page provides instructions exclusively through the Azure Portal UI and does not reference any OS-specific tools, commands, or examples. However, it lacks any mention of command-line or automation options (such as Azure CLI, PowerShell, or Bash), which could be relevant for both Windows and Linux users. There is no explicit Windows bias, but the absence of Linux (or cross-platform) command-line examples or references to automation may disadvantage Linux users who prefer or require non-GUI workflows.
Recommendations
  • Add examples for running and configuring Azure Load Testing and Performance Optimizer using the Azure CLI, which is cross-platform and commonly used on Linux.
  • If PowerShell automation is supported, provide equivalent Bash or Azure CLI scripts for Linux users.
  • Explicitly mention that all steps can be performed from any OS using the Azure Portal, and provide links or references to CLI documentation for users who prefer command-line workflows.
  • Include a section on automating performance optimization using scripts, with examples for both Windows (PowerShell) and Linux (Bash/Azure CLI) environments.
GitHub Create Pull Request
App Testing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/playwright-workspaces/how-to-test-local-applications.md ...laywright-workspaces/how-to-test-local-applications.md
Low Priority View Details →
Scanned: 2025-09-04 00:00
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation provides configuration and usage examples for Playwright Workspaces using TypeScript (Playwright test runner) and C# (NUnit test runner), but does not include any Linux-specific instructions, shell commands, or examples. There is no mention of Linux tools, patterns, or environment-specific considerations, nor are there any examples that demonstrate usage on Linux systems. The documentation is neutral in terms of operating system, but the absence of Linux-specific guidance or parity checks may disadvantage Linux users.
Recommendations
  • Add explicit Linux usage examples, such as running Playwright tests in a Linux shell or terminal, and note any OS-specific considerations (e.g., environment variables, file paths).
  • Include a section or note confirming that the instructions and examples work identically on Linux, or highlight any differences if present.
  • If there are any prerequisites or dependencies that differ on Linux (such as package installation or network configuration), document them clearly.
  • Consider providing bash/zsh command-line examples alongside the existing ones, especially for common Linux workflows.
  • Mention Linux-specific troubleshooting steps or tips, if applicable, to ensure parity and confidence for Linux users.
GitHub Create Pull Request
App Testing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/playwright-workspaces/how-to-test-local-applications.md ...laywright-workspaces/how-to-test-local-applications.md
Low Priority View Details →
Scanned: 2025-09-02 00:00
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation provides configuration and usage examples for Playwright Workspaces using TypeScript (Node.js) and C# (NUnit), but does not include any Linux- or Unix-specific instructions, shell commands, or references to Linux tools or environments. There are no explicit Windows-only commands, but the absence of Linux-specific guidance or troubleshooting may disadvantage Linux users.
Recommendations
  • Add explicit Linux/Unix shell command examples where relevant, such as using bash/zsh or common Linux CLI patterns.
  • Include notes or troubleshooting tips for Linux users, such as handling permissions, networking, or environment variables that may differ from Windows.
  • If any platform-specific configuration is required (e.g., file paths, environment setup), provide both Windows and Linux examples.
  • Clarify that the provided commands (npx, dotnet) are cross-platform, and mention any prerequisites or differences for Linux environments.
  • Consider adding a section or callout confirming Linux support and linking to Linux-specific Playwright documentation if available.
GitHub Create Pull Request
App Testing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/playwright-workspaces/how-to-test-local-applications.md ...laywright-workspaces/how-to-test-local-applications.md
Low Priority View Details →
Scanned: 2025-09-01 00:00
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation does not display explicit Windows bias in terms of command-line tools or PowerShell usage, nor does it mention Windows-specific tools or patterns. However, it lacks explicit Linux (or macOS) examples, such as bash/zsh shell commands, Linux-specific configuration notes, or references to platform-specific considerations. The examples provided are platform-neutral (TypeScript and C#), but the absence of Linux/macOS-specific guidance or validation may leave Linux users uncertain about compatibility or required adjustments.
Recommendations
  • Add explicit Linux/macOS command-line examples (e.g., bash/zsh usage) alongside the current examples.
  • Include a note confirming cross-platform compatibility, or highlight any platform-specific considerations for Linux/macOS users.
  • If there are any differences in environment setup or file paths between Windows and Linux/macOS, document them clearly.
  • Consider providing a Linux/macOS-specific section or callout to reassure non-Windows users that the instructions apply to their platforms.
GitHub Create Pull Request
App Testing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/playwright-workspaces/how-to-use-service-config-file.md ...laywright-workspaces/how-to-use-service-config-file.md
Low Priority View Details →
Scanned: 2025-08-30 00:01
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation demonstrates a subtle Windows bias by listing Windows as the first option in OS-related configuration examples and code snippets, even though Linux is the default. There are no missing Linux examples, and both OS options are documented, but Windows is consistently mentioned or shown before Linux.
Recommendations
  • List Linux before Windows in all option lists and code examples, especially since Linux is the default.
  • Provide code examples that use Linux as the value for the OS setting, or alternate between Linux and Windows in examples.
  • Explicitly state that Linux is the default and recommended option where relevant.
  • Ensure parity in any future troubleshooting or tool references (e.g., avoid referencing only Windows tools or PowerShell commands).
GitHub Create Pull Request
App Testing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/playwright-workspaces/how-to-use-service-config-file.md ...laywright-workspaces/how-to-use-service-config-file.md
Low Priority View Details →
Scanned: 2025-08-08 00:00
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation exhibits a mild 'windows_first' bias: in the Playwright (TypeScript) example, the 'os' setting is shown with 'ServiceOS.WINDOWS' in the code sample, even though the default is 'ServiceOS.LINUX'. Similarly, in the .NET/NUnit example, 'OSPlatform.Linux' is used, but both platforms are mentioned. There are no PowerShell-heavy examples, exclusive Windows tools, or missing Linux examples, but Windows is sometimes presented first or as the example value.
Recommendations
  • Ensure that code samples use the default (Linux) OS setting, or provide both Windows and Linux examples side by side.
  • When listing options, alternate which OS is presented first, or use alphabetical order.
  • Explicitly mention parity and support for both Windows and Linux in introductory sections.
  • If possible, add brief notes about any OS-specific considerations or limitations.
GitHub Create Pull Request
← Previous Page 4 of 4 Next →