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 1-25 of 99 flagged pages
App Testing
Tutorial: Run end-to-end tests with Playwright Workspaces
...playwright-workspaces/tutorial-run-end-to-end-tests.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively using PowerShell syntax for command-line examples (e.g., 'cd', 'git clone', 'npm install'), without providing Linux/macOS shell equivalents. There is no mention of Linux-specific instructions, nor are alternative shell commands (such as Bash) shown. The prerequisites and environment setup steps do not address platform differences, and Windows-centric tools and patterns (such as PowerShell prompt style) are used throughout.
Recommendations
- Provide command-line examples using both PowerShell (Windows) and Bash (Linux/macOS) syntax, or use a neutral format where possible.
- Explicitly mention platform differences in prerequisites and installation steps (e.g., Azure CLI installation commands for Linux, macOS, and Windows).
- Include notes or sections for Linux/macOS users, such as alternative commands for navigation and environment setup.
- Avoid using only PowerShell code blocks for generic commands; use 'shell' or 'bash' where appropriate.
- Clarify that the instructions are cross-platform and provide links or guidance for platform-specific issues.
Create Pull Request
App Testing
Manage roles in Azure Load Testing
...ticles/app-testing/load-testing/how-to-assign-roles.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a bias toward Windows by exclusively providing PowerShell examples for command-line role management, without mentioning or providing examples for Azure CLI or Bash (common on Linux/macOS). The only command-line tool referenced is Azure PowerShell, which is primarily used on Windows. There are no Linux-specific instructions, and the order of presentation puts PowerShell before any mention of cross-platform alternatives.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and commonly used on Linux/macOS.
- Explicitly mention that Azure CLI and Bash can be used for role management, and provide links to relevant documentation.
- Balance the presentation order by introducing Azure CLI and PowerShell together, or by leading with the cross-platform Azure CLI.
- Include troubleshooting steps and examples that apply to Linux/macOS environments, not just Windows/PowerShell.
- Clarify that Azure PowerShell is available on Linux/macOS, but highlight Azure CLI as the default cross-platform tool.
App Testing
Configure customer-managed keys for encryption
...load-testing/how-to-configure-customer-managed-keys.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are provided alongside Azure CLI and portal instructions, but PowerShell is often presented before Azure CLI. The use of PowerShell and references to PowerShell modules (Az.KeyVault) are inherently Windows-centric, as PowerShell is most commonly used on Windows. Screenshots and step-by-step instructions are focused on the Azure portal, which is platform-agnostic but often associated with Windows workflows. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tooling or patterns. The documentation does not address Linux users directly or provide parity for Linux-native command-line environments beyond Azure CLI.
Recommendations
- Add explicit bash shell examples for key operations, especially for users who prefer native Linux tools.
- Clarify that Azure CLI commands work cross-platform and provide any necessary setup instructions for Linux environments.
- Reorder code tabs so that Azure CLI appears before PowerShell, or alternate the order to avoid implicit prioritization.
- Mention that PowerShell Core is available on Linux and macOS, if PowerShell examples are retained, to reduce the perception of Windows exclusivity.
- Include notes or links for Linux users regarding authentication, environment setup, and common troubleshooting scenarios.
- Where screenshots are used, consider including examples from Linux desktop environments or terminal outputs.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively using PowerShell for deployment instructions and examples. All command-line steps assume a Windows environment, with only a brief mention that PowerShell can be installed on Linux/macOS, but no native Bash or Linux shell alternatives are provided. The deployment script is a PowerShell script, and there are no instructions for Linux users who may prefer Bash or shell scripts. Windows tools and patterns are referenced first and exclusively.
Recommendations
- Provide equivalent Bash or shell script examples for Linux/macOS users, especially for deployment steps.
- If the deployment script is only available in PowerShell, offer guidance on how to run it in Linux/macOS environments, or provide a cross-platform alternative.
- Mention Linux-native tools and commands (e.g., using Bash, sh, or zsh) alongside PowerShell instructions.
- Ensure that references to region codes and other Azure CLI commands are shown in both PowerShell and Bash syntax.
- Consider restructuring the documentation so that instructions for Windows and Linux/macOS are presented in parallel, or clearly indicate platform-specific steps.
App Testing
Tutorial: Identify performance issues with load testing
...-testing/tutorial-identify-bottlenecks-azure-portal.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing PowerShell commands and tools (e.g., 'PowerShell commands to deploy the sample application'), listing Windows-centric tools (Visual Studio Code, PowerShell) in the prerequisites, and not providing explicit Linux/macOS equivalents or examples. The deployment instructions mention using PowerShell and command windows, which are primarily associated with Windows, without clarifying or providing alternatives for Linux/macOS users. There are no screenshots or CLI examples shown in a Linux terminal, and no mention of Bash or shell scripting. The documentation assumes familiarity with Windows workflows and tools, and does not address platform-specific differences or provide parity for Linux users.
Recommendations
- Provide explicit Linux/macOS instructions alongside Windows/PowerShell examples, including Bash equivalents for all CLI commands.
- Clarify when PowerShell is required and offer alternatives (e.g., Bash, zsh) for non-Windows users.
- Include screenshots of commands being run in Linux/macOS terminals as well as Windows command prompts.
- List platform-agnostic tools first in prerequisites (e.g., Azure CLI, Git), and mention platform-specific installation guides for both Windows and Linux/macOS.
- Avoid using 'command window' or 'PowerShell' generically; specify 'terminal' and provide examples for multiple platforms.
- Add notes or tips for Linux/macOS users where workflows or commands differ.
App Testing
Quickstart: Run Playwright tests at scale
...aywright-workspaces/quickstart-run-end-to-end-tests.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by consistently referencing Windows-centric tools and workflows, such as Visual Studio Code and PowerShell/.NET examples, and by providing instructions that assume use of the Azure portal (which is most commonly used on Windows). There are no explicit Linux-specific instructions, examples, or screenshots, and CLI commands are presented generically without addressing platform differences (e.g., environment variable setup, shell differences). The documentation also prioritizes Visual Studio Code (a Microsoft product popular on Windows) for test running and debugging, without mentioning alternatives for Linux users.
Recommendations
- Add explicit Linux shell examples for environment variable setup (e.g., export PLAYWRIGHT_SERVICE_URL=...) and clarify cross-platform differences.
- Include instructions and screenshots for running Playwright tests from Linux terminals and editors (such as VS Code on Linux, or alternatives like Vim, Emacs, or JetBrains IDEs).
- Provide parity for .NET examples by including equivalent instructions for Linux (e.g., using Bash instead of PowerShell, installation via apt/yum/pacman if relevant).
- Mention and link to Linux-specific installation guides for Azure CLI and Playwright.
- Clarify that all CLI commands work on Linux and Mac, and note any platform-specific caveats.
- Add a section or callout for Linux users, highlighting any differences or additional steps required.
App Testing
Quickstart: Perform advanced diagnostics with Playwright Workspaces reporting
...vanced-diagnostic-with-playwright-workspaces-reporting.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal (web UI), Visual Studio Code, and Azure CLI, without providing any Linux-specific instructions, terminal screenshots, or alternative tools. All example commands and environment setup steps are generic and could apply to Linux, but there are no explicit Linux shell examples, nor is there mention of Linux desktop environments or alternative editors. The tip for opening the trace viewer uses the Windows-centric 'Ctrl' key convention, and there is no mention of Linux-specific keyboard shortcuts or usage patterns.
Recommendations
- Provide explicit Linux shell command examples and screenshots where relevant (e.g., bash, zsh).
- Mention Linux desktop environments and alternative editors (such as Vim, Emacs, GNOME Terminal) alongside Visual Studio Code.
- Clarify that Azure CLI and npm commands work on Linux and provide any necessary Linux-specific installation instructions.
- Include Linux keyboard shortcut conventions (e.g., 'Ctrl' vs 'Cmd' vs 'Super') in tips and instructions.
- Add notes or sections for troubleshooting or configuring on Linux systems, especially for environment variables and file paths.
- Ensure parity in examples by alternating or combining Windows and Linux instructions, rather than defaulting to Windows-centric patterns.
App Testing
Quickstart: Continuous end-to-end testing
...t-workspaces/quickstart-automate-end-to-end-testing.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. PowerShell is used as the default scripting language in CI pipeline examples (e.g., AzureCLI@2 with scriptType: 'pscore', PowerShell@2 tasks), and authentication setup instructions reference Azure PowerShell before alternatives like Azure CLI. The use of 'AzPowershell' and PowerShell-based tasks is prevalent in both GitHub Actions and Azure Pipelines examples. There are no explicit Linux shell/bash script examples, and Windows-centric tools/patterns are mentioned or implied before their Linux equivalents. The documentation does not provide parity for Linux-native workflows or shell scripting, which may hinder adoption by Linux-focused teams.
Recommendations
- Provide equivalent bash/shell script examples alongside PowerShell examples, especially for CI/CD pipeline steps.
- Reference Azure CLI commands before or alongside Azure PowerShell, and clarify when either can be used.
- Explicitly mention cross-platform compatibility and provide instructions for both Windows and Linux runners.
- Avoid using Windows-specific terminology (e.g., AzPowershell) as the default; use more generic or platform-neutral language.
- Add examples for Linux/Mac environments, such as bash scripts for authentication and test execution.
- Clarify that Playwright and its Azure integrations work on Linux runners and provide troubleshooting tips for non-Windows environments.
App Testing
Quickstart: Run Playwright tests at scale
...aywright-workspaces/quickstart-run-end-to-end-tests.md
High Priority
View Details →
Detected Bias Types
Windows First
Visual Studio Code Heavy
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by prioritizing Visual Studio Code (a Microsoft tool popular on Windows), referencing PowerShell and .NET examples, and omitting explicit Linux/macOS-specific instructions or screenshots. All terminal/CLI instructions use generic 'terminal' language, but do not clarify cross-platform differences (e.g., environment variable setting, CLI usage nuances). There are no Linux-specific examples, nor are alternative Linux-native editors or tools mentioned.
Recommendations
- Include explicit Linux/macOS instructions for setting environment variables (e.g., export PLAYWRIGHT_SERVICE_URL=...) and running CLI commands.
- Add screenshots or references for using Playwright in Linux-native editors (e.g., VS Code on Linux, JetBrains IDEs, Vim, etc.), or clarify that VS Code is cross-platform.
- Provide parity for .NET/NUnit examples by mentioning how to install and run on Linux (e.g., using dotnet CLI on Ubuntu).
- Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, dependency installation).
- Clarify that all CLI commands are cross-platform, and specify any platform-specific caveats where relevant.
App Testing
Tutorial: Run end-to-end tests with Playwright Workspaces
...playwright-workspaces/tutorial-run-end-to-end-tests.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily through the use of PowerShell syntax for all command-line examples (e.g., git, npm, npx), and by referring to 'terminal or command window' without clarifying platform differences. There are no explicit Linux/macOS shell examples (e.g., bash), nor are there instructions for platform-specific nuances (such as path separators or environment variable setting differences). The installation instructions for tools like Azure CLI, Git, and Visual Studio Code are generic but do not provide parity for Linux-specific installation or usage patterns.
Recommendations
- Provide both PowerShell/Command Prompt and Bash (Linux/macOS) examples for all CLI commands, using appropriate syntax for each platform.
- Clarify platform-specific terminology (e.g., 'terminal' for Linux/macOS, 'command prompt' for Windows) and mention any differences in usage.
- Include Linux/macOS installation instructions or links for prerequisites such as Azure CLI, Git, and Visual Studio Code.
- Show how to set environment variables in both Windows (set/setx) and Linux/macOS (export) contexts.
- Use neutral shell syntax (e.g., $ for shell prompts) or provide tabs/switchers for platform-specific instructions.
App Testing
Manage roles in Azure Load Testing
...ticles/app-testing/load-testing/how-to-assign-roles.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell examples for command-line role management, without mentioning or providing equivalent Azure CLI (cross-platform) commands. The only command-line tooling referenced is Azure PowerShell, which is most commonly used on Windows. There are no Linux-specific instructions or examples, and the portal UI instructions are platform-neutral but do not address Linux-specific considerations. The structure presents PowerShell before any mention of CLI alternatives, and omits Bash or Azure CLI usage entirely.
Recommendations
- Add equivalent Azure CLI (az) examples for all role assignment, listing, and removal operations, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that Azure CLI can be used on Linux, macOS, and Windows, and provide installation links.
- Where PowerShell is referenced, clarify that it is available cross-platform, but recommend Azure CLI for Linux users.
- Consider adding Bash script examples for common tasks to improve Linux parity.
- Review troubleshooting and related content for any implicit Windows assumptions, and add notes or examples relevant to Linux environments.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page is heavily biased towards Windows and PowerShell. All command-line examples use PowerShell syntax, and instructions assume the use of Windows PowerShell, with only a brief tip about installing PowerShell on Linux/macOS. There are no bash or native Linux shell examples, and Windows tools and patterns (such as .ps1 scripts and Get-AzLocation) are mentioned exclusively or before any Linux equivalents.
Recommendations
- Provide equivalent bash or shell commands for Linux/macOS users, such as using './deploymentscript.ps1' with pwsh, or alternative deployment scripts (e.g., bash).
- Mention Linux and macOS environments explicitly in the main instructions, not just in tips.
- If the deployment script is PowerShell-only, offer a cross-platform alternative or clarify requirements up front.
- Include region code lookup commands for Azure CLI (e.g., 'az account list-locations') as an alternative to Get-AzLocation.
- Reorder instructions so that Windows and Linux/macOS usage are presented with equal prominence.
App Testing
Configure customer-managed keys for encryption
...load-testing/how-to-configure-customer-managed-keys.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are provided alongside Azure CLI and portal instructions, but PowerShell is a Windows-centric tool. In several sections, PowerShell instructions are presented before Azure CLI, which is cross-platform. The use of PowerShell-specific modules and commands (e.g., Az.KeyVault, New-AzKeyVault) reinforces the Windows orientation. There are no explicit Linux-only examples or references to Linux-native tools or shell environments (e.g., Bash), and screenshots are exclusively from the Azure portal, which is platform-agnostic but often associated with Windows workflows.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and more familiar to Linux users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell environments (e.g., Bash) where appropriate.
- Include notes or examples for Linux users, such as how to install Azure CLI on Linux, or how to run ARM template deployments from Bash.
- Avoid using Windows-specific terminology or tools as the default; clarify that PowerShell is available cross-platform but is traditionally a Windows tool.
- Where possible, add screenshots or references to Linux desktop environments to balance visual representation.
App Testing
Tutorial: Identify performance issues with load testing
...-testing/tutorial-identify-bottlenecks-azure-portal.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell commands and patterns for deployment, mentioning Visual Studio Code and Git with download links that default to Windows installers, and generally assuming a Windows-centric workflow. There is no explicit mention of Linux-specific commands, shell environments, or alternative deployment instructions for Linux/macOS users. The use of 'terminal or command window' is ambiguous but leans toward Windows terminology, and PowerShell is referenced as a deployment tool without equivalent Bash or Linux shell examples.
Recommendations
- Provide explicit Linux/macOS command-line examples alongside PowerShell, especially for deployment steps.
- Include instructions for using Bash or other common Linux shells where PowerShell is referenced.
- Clarify tool installation links to point to platform-specific installers (Windows, Linux, macOS) and mention package managers (e.g., apt, yum, Homebrew).
- Use neutral terminology such as 'terminal' instead of 'command window', and specify platform differences where relevant.
- Add screenshots and workflow notes for Linux environments in addition to Windows.
- Ensure all CLI commands are tested and presented in a cross-platform manner, noting any OS-specific differences.
App Testing
Quickstart: Continuous end-to-end testing
...t-workspaces/quickstart-automate-end-to-end-testing.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell and Windows-centric tools (AzPowershell, Azure PowerShell, AzureCLI with 'pscore') are used for authentication and workflow steps, often as the primary or only example. There is frequent mention of PowerShell and Windows-specific commands, and no explicit Linux shell (bash/sh) equivalents are provided for authentication or scripting steps. The use of Windows tools and patterns appears before or instead of cross-platform alternatives, and there is a lack of parity in showing Linux-native approaches.
Recommendations
- Provide bash/sh equivalents for all PowerShell commands and workflow steps, especially for authentication and scripting in CI pipelines.
- Explicitly mention and demonstrate how to perform setup and authentication steps on Linux/macOS environments, including using Azure CLI in bash.
- Avoid using Windows-specific terminology (e.g., AzPowershell, PowerShell@2) as the default; instead, present cross-platform alternatives first or side-by-side.
- Clarify which steps are platform-agnostic and which require adaptation, and offer guidance for users on Linux/macOS.
- Include sample CI workflow snippets using bash or sh for both GitHub Actions and Azure Pipelines.
- Review and update code blocks and instructions to ensure they work seamlessly on Linux/macOS systems, not just Windows.
App Testing
Quickstart: Continuous end-to-end testing
...t-workspaces/quickstart-automate-end-to-end-testing.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a bias towards Windows environments by frequently referencing PowerShell and Windows-centric tools (e.g., AzPowershell, Azure PowerShell, AzureCLI with 'pscore'), and using PowerShell syntax for installation and command-line examples. Windows authentication and setup patterns are mentioned before Linux equivalents, and there is a lack of explicit Linux shell (bash/sh) examples or instructions, even though CI runners are set to 'ubuntu-latest'.
Recommendations
- Provide equivalent bash/sh command-line examples alongside PowerShell commands, especially for installation and CLI usage.
- Clarify that Azure CLI and authentication steps work cross-platform, and provide Linux/macOS specific instructions where relevant.
- Avoid using PowerShell-specific flags (e.g., 'enableAzPSSession: true') unless necessary, and explain alternatives for Linux/macOS users.
- Include explicit Linux/macOS setup and troubleshooting sections, or at least mention platform parity.
- When referencing tools (e.g., Azure PowerShell, Azure CLI), mention their cross-platform availability and usage.
- Balance example scripts and code blocks to include both Windows and Linux shell environments, especially for CI/CD workflows.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively using PowerShell for deployment instructions, referencing Windows PowerShell as the default shell, and omitting equivalent Linux shell (bash) examples. The use of Windows-specific tools and commands is prevalent, and Linux alternatives are only briefly mentioned as an afterthought, without concrete examples.
Recommendations
- Provide parallel bash (Linux/macOS) command examples for each PowerShell step, especially for cloning the repo and running deployment scripts.
- Highlight cross-platform compatibility by showing how to run the deployment script with bash (if possible) or provide a bash version of the deployment script.
- List Linux-native tools and commands (e.g., curl, wget, bash scripts) where appropriate, and mention them before or alongside Windows tools.
- Explicitly state platform requirements and offer guidance for users on Linux/macOS, including troubleshooting and environment setup.
- Ensure that documentation sections do not assume Windows as the default platform, and structure instructions to treat Windows, Linux, and macOS equally.
App Testing
Tutorial: Identify performance issues with load testing
...-testing/tutorial-identify-bottlenecks-azure-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell commands for deployment, mentioning 'command window' alongside 'terminal', and not providing explicit Linux/macOS shell examples or instructions. The prerequisites and CLI usage are generally cross-platform, but deployment steps and terminology lean toward Windows users. There are no screenshots or instructions for Linux-specific tools, nor are there alternative shell commands or troubleshooting notes for non-Windows environments.
Recommendations
- Provide explicit Linux/macOS shell command examples alongside PowerShell, especially for deployment steps.
- Use neutral terminology such as 'terminal' instead of 'command window' throughout the documentation.
- Include notes or troubleshooting tips for common Linux/macOS issues (e.g., file permissions, environment variables).
- Add screenshots or illustrations showing the process on Linux/macOS systems.
- Mention and link to Linux/macOS installation guides for all required tools (Azure CLI, Git, VS Code) in the prerequisites section.
- Clarify that all CLI commands are cross-platform, and specify any platform-specific differences where relevant.
App Testing
Manage roles in Azure Load Testing
...ticles/app-testing/load-testing/how-to-assign-roles.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by providing detailed instructions and examples exclusively for Azure PowerShell, which is most commonly used on Windows. There are no examples or guidance for using Azure CLI, Bash, or other cross-platform tools that are standard on Linux or macOS. The PowerShell section is prominent and the only command-line automation method described, while Linux-friendly alternatives are omitted.
Recommendations
- Add equivalent Azure CLI examples for all role management tasks (listing, assigning, and removing roles).
- Include Bash shell snippets and instructions for Linux/macOS users where appropriate.
- Mention Azure CLI as a cross-platform alternative before or alongside PowerShell in the introduction to command-line tools.
- Clarify that PowerShell is available cross-platform, but highlight Azure CLI for users who prefer native Linux/macOS tooling.
- Ensure troubleshooting steps reference both PowerShell and Azure CLI where applicable.
App Testing
Tutorial: Run end-to-end tests with Playwright Workspaces
...playwright-workspaces/tutorial-run-end-to-end-tests.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits Windows bias by exclusively using PowerShell syntax for all command-line examples (git, npm, npx), and by not providing Linux/macOS-specific instructions or shell syntax. The term 'terminal or command window' is used, which is ambiguous but leans toward Windows terminology. There are no explicit Linux or macOS examples, nor are platform differences addressed in installation or usage steps.
Recommendations
- Provide command-line examples using standard shell syntax (e.g., bash) alongside PowerShell, or use a neutral format.
- Clarify platform-specific instructions for installing prerequisites like Azure CLI, Git, and Visual Studio Code, including links or notes for Linux/macOS users.
- Replace ambiguous terms like 'command window' with 'terminal' or specify platform differences where relevant.
- Add notes or sections addressing any differences in environment variable setup, file paths, or authentication steps for Linux/macOS users.
- Ensure screenshots and UI instructions are not Windows-specific, or provide alternatives for other platforms if applicable.
App Testing
Quickstart: Run Playwright tests at scale
...aywright-workspaces/quickstart-run-end-to-end-tests.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows. The Azure portal and Visual Studio Code are featured prominently, with screenshots and instructions that implicitly assume a Windows environment. There are no explicit Linux-specific examples, commands, or screenshots, and alternative Linux tools or workflows (such as using Linux-native editors or package managers) are not mentioned. The authentication instructions rely on Azure CLI, which is cross-platform, but the overall workflow and examples are tailored to Windows users, especially in the Visual Studio Code sections.
Recommendations
- Add explicit Linux terminal examples and screenshots, showing how to run Playwright tests and configure environments on Linux distributions.
- Include instructions for popular Linux editors (such as Vim, Emacs, or GNOME Text Editor) for editing configuration files, alongside Visual Studio Code.
- Mention Linux-native package managers (e.g., apt, yum) for installing prerequisites like Node.js and Azure CLI.
- Clarify that all CLI commands and workflows are cross-platform, and provide troubleshooting tips for common Linux issues (such as file permissions or environment variable setup).
- Balance screenshots and UI walkthroughs by including examples from Linux desktop environments (e.g., GNOME, KDE) where relevant.
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/playwright-workspaces/quickstart-run-end-to-end-tests.md
...aywright-workspaces/quickstart-run-end-to-end-tests.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-centric tools and workflows, such as Visual Studio Code and PowerShell/.NET examples, and by omitting explicit Linux or cross-platform alternatives in key steps. The CLI instructions and environment setup are generally platform-neutral, but the examples and screenshots focus on Windows environments, and there is no mention of Linux-specific package managers, shell environments, or desktop tools. The documentation assumes familiarity with Windows tools and does not provide parity for Linux users in terms of examples, troubleshooting, or alternative workflows.
Recommendations
- Add explicit Linux/macOS instructions for installing dependencies (e.g., using apt, yum, or Homebrew for Azure CLI).
- Include screenshots and examples using Linux terminals and desktop environments alongside Windows/VS Code.
- Mention cross-platform alternatives to Visual Studio Code, or clarify that VS Code is available on Linux/macOS.
- Provide shell commands and environment variable setup examples for Bash/zsh (e.g., export PLAYWRIGHT_SERVICE_URL=...) in addition to .env and PowerShell.
- Clarify that all CLI commands work on Linux/macOS, and note any platform-specific caveats.
- Add troubleshooting tips for common Linux issues (e.g., file permissions, dependency installation).
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/playwright-workspaces/tutorial-run-end-to-end-tests.md
...playwright-workspaces/tutorial-run-end-to-end-tests.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively using PowerShell syntax for all command-line examples (e.g., git, npm, npx), without providing Linux/macOS shell equivalents. The instructions and examples assume a Windows environment, and there is no mention of Linux-specific patterns, tools, or alternative commands. This may hinder Linux users who expect bash/zsh syntax or platform-specific guidance.
Recommendations
- Provide command-line examples in both PowerShell (Windows) and bash/zsh (Linux/macOS) syntax, especially for navigation (cd), running commands, and environment variable setup.
- Explicitly mention cross-platform compatibility for tools like Azure CLI, Playwright, and npm, and link to platform-specific installation guides.
- Include screenshots or instructions for both Windows and Linux environments where relevant, such as terminal usage.
- Add notes or callouts for any platform-specific differences (e.g., environment variable syntax, file paths).
- Ensure that the documentation does not assume Visual Studio Code as the only editor, and mention alternatives for Linux users if appropriate.
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/playwright-workspaces/quickstart-automate-end-to-end-testing.md
...t-workspaces/quickstart-automate-end-to-end-testing.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation demonstrates a noticeable Windows bias, primarily through the frequent use of PowerShell and Windows-centric tools (e.g., AzPowershell, Azure PowerShell, AzureCLI with 'pscore'). Windows authentication and setup patterns are described first or exclusively in several places, with PowerShell commands and references appearing before or instead of Linux alternatives. There is little to no mention of Linux shell equivalents, and the workflow examples default to PowerShell-based steps even when the runner is 'ubuntu-latest'.
Recommendations
- Provide equivalent Bash or Linux shell commands alongside PowerShell examples, especially for CI steps and authentication.
- Explicitly mention cross-platform compatibility and clarify when commands/tools are OS-agnostic.
- Where PowerShell is used, offer Bash alternatives for Linux/macOS users (e.g., Azure CLI commands in Bash).
- Avoid implying PowerShell is required on non-Windows runners; clarify that Azure CLI and related tools work in Bash.
- Add notes or tabs for Linux/macOS setup steps, especially for local development and CI/CD environments.
- Review and balance the order of tool mentions (e.g., Azure CLI before or alongside Azure PowerShell).
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/load-testing/how-to-configure-customer-managed-keys.md
...load-testing/how-to-configure-customer-managed-keys.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples and references are given equal prominence to Azure CLI, but PowerShell is a Windows-centric tool. In several sections, PowerShell is listed before Azure CLI, and there is extensive use of PowerShell-specific modules and commands. The documentation also references the Azure portal, which is cross-platform but often associated with Windows workflows. There are no explicit Linux shell (bash) or scripting examples, nor any mention of Linux-specific tools or considerations.
Recommendations
- Provide bash shell examples alongside PowerShell, especially for ARM template deployments and Azure Key Vault operations.
- Clarify that Azure CLI commands work natively on Linux and macOS, and provide installation or usage notes for those platforms.
- Where PowerShell is referenced, note that PowerShell Core is available cross-platform, and provide guidance for Linux/macOS users.
- Consider listing Azure CLI examples before PowerShell, as CLI is more universally available across platforms.
- Add explicit notes or sections for Linux users, such as environment setup, authentication, and scripting best practices.