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 26-50 of 99 flagged pages
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/load-testing/includes/include-deploy-sample-application.md
...-testing/includes/include-deploy-sample-application.md
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 and Windows-centric instructions for cloning and deploying the sample application. All examples and deployment steps assume the use of PowerShell, with only a brief tip on installing PowerShell on Linux/macOS, but no native Bash or Linux shell alternatives are provided. The use of Windows tools and commands is prioritized, and Linux users are expected to adapt by installing PowerShell rather than being offered platform-native instructions.
Recommendations
- Provide equivalent Bash or shell script examples for Linux/macOS users, especially for deployment steps.
- Include instructions for running the deployment using native Linux tools (e.g., bash scripts) if available.
- Present cross-platform instructions side-by-side or clearly indicate platform-specific steps.
- Mention Linux-first or platform-neutral tools where possible, such as using Azure CLI directly for deployment.
- Avoid assuming PowerShell is the default shell; offer alternatives for users who prefer not to install PowerShell.
Create Pull Request
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/load-testing/how-to-assign-roles.md
...ticles/app-testing/load-testing/how-to-assign-roles.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
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 'Configure Azure RBAC' section lists PowerShell before any other tool, and does not reference Linux or macOS workflows or tools. There are no examples using Bash, Azure CLI, or other non-Windows command-line interfaces.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that Azure CLI can be used on Windows, Linux, and macOS, and provide links to relevant Azure CLI documentation.
- Consider reordering the 'Configure Azure RBAC' section to present Azure CLI before PowerShell, or present both side-by-side.
- Include notes or examples for Bash scripting where appropriate.
- Ensure troubleshooting and related content sections reference cross-platform tools and workflows.
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/load-testing/includes/include-deploy-sample-application.md
...-testing/includes/include-deploy-sample-application.md
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 first, and omitting equivalent Linux shell (bash) commands. The deployment script is provided only in PowerShell, and while there is a tip about installing PowerShell on Linux/macOS, there are no native Linux shell examples or alternatives. Additionally, Windows tools and patterns (e.g., .\deploymentscript.ps1) are used throughout, with no mention of bash scripting or Linux-first workflows.
Recommendations
- Provide equivalent bash shell commands for Linux users, such as using './deploymentscript.ps1' with pwsh or offering a bash deployment script.
- Include Linux/macOS-specific instructions and examples alongside Windows/PowerShell steps.
- Reference Linux tools and patterns (e.g., bash, sh) where appropriate, not just PowerShell.
- Consider offering a cross-platform deployment script (e.g., bash and PowerShell versions) in the sample repo.
- List Linux instructions before or alongside Windows instructions to avoid 'windows_first' bias.
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
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias. Visual Studio Code (VS Code) is the only editor/IDE mentioned for local test running, and all GUI screenshots and instructions are from the Azure Portal web interface, which is platform-agnostic but often associated with Windows workflows. The .NET/NUnit example uses PowerShell syntax for package installation (dotnet add package), and the only editor integration described is for VS Code, with no mention of Linux-native editors or workflows. There are no explicit Linux shell examples (e.g., bash, zsh), and no mention of Linux-specific tools or environments. The documentation does not provide parity for Linux users in terms of editor/IDE or CLI workflow examples.
Recommendations
- Include explicit Linux shell (bash/zsh) examples for installing dependencies and running commands, especially for .NET/NUnit workflows.
- Mention and provide examples for running Playwright tests in popular Linux editors (such as Vim, Emacs, or JetBrains IDEs) or at least clarify that VS Code is cross-platform.
- Add notes or screenshots showing the experience on Linux systems, or clarify that all CLI commands and workflows are fully supported on Linux.
- Where PowerShell or Windows-specific syntax is shown, provide the equivalent bash/zsh commands for Linux users.
- Explicitly state that all steps are supported on Linux and macOS, and highlight any OS-specific considerations if they exist.
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/load-testing/includes/include-deploy-sample-application.md
...-testing/includes/include-deploy-sample-application.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows and PowerShell bias. All command-line examples use PowerShell syntax, and the deployment script is a PowerShell script with no mention of a Bash or shell alternative. The instructions assume the user is running Windows or has installed PowerShell on Linux/macOS, and Windows tools and patterns are mentioned first and exclusively. There are no native Linux shell examples or guidance for users who prefer Bash or other Unix shells.
Recommendations
- Provide equivalent Bash or shell script examples for Linux/macOS users, especially for cloning the repo and running deployment scripts.
- If the deployment script is only available in PowerShell, consider providing a Bash version or instructions for running the deployment using Azure CLI commands.
- Mention Linux/macOS workflows alongside Windows, not only as an afterthought or via PowerShell installation.
- List Linux-native tools and commands (e.g., using ./deploymentscript.sh if available, or direct Azure CLI commands) before or alongside Windows/PowerShell equivalents.
- Clarify any platform-specific requirements or limitations up front, and provide parity in documentation for all major platforms.
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
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-centric tools and workflows (such as Visual Studio Code, .NET/NUnit, and Azure CLI) and omitting explicit Linux/macOS-specific instructions or examples. All command-line and environment setup examples are generic or Windows-oriented, with no mention of Linux-specific shell commands, environment variable syntax, or alternative editors. The documentation also references Visual Studio Code and .NET/NUnit (commonly associated with Windows development) without providing parity for Linux-native tools or editors. There are no screenshots or instructions for Linux environments, and no mention of Linux-specific considerations.
Recommendations
- Add explicit Linux/macOS shell command examples (e.g., export PLAYWRIGHT_SERVICE_URL=...) alongside Windows/PowerShell equivalents.
- Include instructions and screenshots for running Playwright tests from Linux terminals and editors (such as VS Code on Linux, or alternatives like Vim/Emacs).
- Mention Linux package managers (e.g., apt, yum, brew) for installing dependencies like Node.js, .NET, and Azure CLI.
- Clarify that the instructions are cross-platform and provide OS-specific notes where behavior or commands differ.
- Show how to set environment variables in Linux/macOS shells (bash/zsh) as well as in Windows/PowerShell.
- Consider including a section or callout for Linux users, highlighting any differences or additional steps required.
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/load-testing/how-to-assign-roles.md
...ticles/app-testing/load-testing/how-to-assign-roles.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides detailed instructions and examples for configuring Azure RBAC using the Azure portal and Azure PowerShell cmdlets, which are primarily Windows-centric tools. There are no examples or guidance for performing these tasks using cross-platform tools such as the Azure CLI, nor are there any Bash or Linux shell examples. This creates a bias toward Windows users and may hinder Linux or macOS users from following the documentation effectively.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell cmdlets shown, including role assignment, listing, and removal.
- Include Bash or shell script snippets where appropriate, especially for Linux/macOS users.
- Explicitly mention that Azure CLI is cross-platform and provide links to its installation and usage.
- Ensure that instructions for configuring Azure RBAC are not limited to the Azure portal and PowerShell, but also cover CLI and REST API methods.
- Consider reordering sections so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell to avoid the impression of Windows-first bias.
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
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows/Powershell bias. Powershell commands and Windows-centric tools (such as AzPowershell, Azure PowerShell, and .NET/NUnit with C#) are used or referenced frequently, sometimes without equivalent Linux/bash alternatives. Powershell is used in both GitHub Actions and Azure Pipelines examples, and the use of 'PowerShell@2' and 'pscore' script types further reinforce this. There are no explicit bash or Linux shell command examples, and Windows/PowerShell tools are often mentioned first or exclusively, especially for authentication and setup steps.
Recommendations
- Provide bash or sh equivalents for all PowerShell commands and scripts, especially for steps like authentication, dependency installation, and running Playwright tests.
- Include Linux/macOS CLI examples (e.g., using Azure CLI instead of Azure PowerShell) alongside or before Windows/PowerShell examples.
- Clarify when a step is cross-platform and when it is Windows-specific; avoid implying that PowerShell is required on Linux runners.
- For .NET/NUnit sections, mention that .NET Core is cross-platform and provide explicit Linux/macOS instructions where relevant.
- In workflow YAML examples, show both PowerShell and bash script blocks, or use shell-agnostic commands where possible.
- Review all references to Windows tools and ensure Linux-native alternatives are documented and easy to find.
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
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Visual Studio Code (VS Code) and its Test Explorer are featured prominently as the GUI workflow, with no mention of Linux-native editors or CLI-only workflows. The only IDE-based instructions are for VS Code, which is most popular on Windows. There are no explicit Linux-specific instructions, screenshots, or terminal examples (e.g., bash vs PowerShell). The .NET/NUnit runner instructions use PowerShell syntax for package installation and do not mention Linux-specific .NET usage or shell commands. There are no references to Linux tools, shells, or package managers, and all screenshots are from the Azure Portal, which is OS-agnostic but the workflow assumes a GUI, which is more common on Windows.
Recommendations
- Include explicit Linux/macOS CLI examples alongside or before Windows/PowerShell examples (e.g., show both bash and PowerShell commands for .NET and npm usage).
- Add a section or note about running Playwright tests in Linux environments, including any differences in environment variable setup or file paths.
- Provide alternative instructions for popular Linux editors (such as Vim, Emacs, or JetBrains IDEs) or clarify that VS Code is cross-platform.
- Show at least one screenshot or terminal output from a Linux shell to demonstrate parity.
- Mention Linux package managers (apt, yum, etc.) where relevant, especially for installing dependencies like Node.js or .NET SDK.
- Clarify that all instructions are cross-platform unless otherwise noted, and explicitly state any OS-specific caveats.
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
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by frequently referencing PowerShell, using Windows-centric tools and terminology (e.g., AzPowershell, PowerShell@2 tasks), and omitting explicit Linux shell or cross-platform CLI examples. Even when CI runners are set to Ubuntu, the scripts and instructions default to PowerShell syntax and tools, with no Bash or Linux-native alternatives provided. This may hinder Linux-first or cross-platform users.
Recommendations
- Provide equivalent Bash or sh examples alongside PowerShell commands, especially for npm, dotnet, and Playwright CLI usage.
- When showing CI pipeline YAML, offer both PowerShell and Bash script variants, or use cross-platform steps where possible.
- Avoid using Windows-specific terminology (e.g., 'AzPowershell', 'PowerShell@2') as the default; clarify when steps are cross-platform or provide Linux/macOS alternatives.
- Explicitly mention that all steps work on Linux/macOS, and highlight any platform-specific considerations.
- For command-line snippets, default to Bash or provide both Bash and PowerShell versions, especially for Playwright and npm commands.
- Review all code blocks and workflow steps to ensure Linux users are not required to mentally translate from PowerShell to Bash.
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
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. It references Windows-centric tools and workflows (such as Visual Studio Code and PowerShell/dotnet commands), and omits explicit Linux/macOS equivalents or guidance. The ordering of examples and tool recommendations often assumes a Windows environment, and there is a lack of parity in shell/command-line instructions for Linux users.
Recommendations
- Provide explicit Linux/macOS command-line examples alongside Windows/PowerShell commands, especially for dotnet and environment variable setup.
- When referencing Visual Studio Code, clarify that it is cross-platform and provide alternative instructions for users who may use other editors or command-line workflows.
- Include bash/zsh shell examples for setting environment variables (e.g., export PLAYWRIGHT_SERVICE_URL=...), not just .env or PowerShell approaches.
- For .NET/NUnit instructions, show both PowerShell and bash (or generic shell) command variants (e.g., dotnet test -- NUnit.NumberOfTestWorkers=20 works on both, but clarify if there are differences).
- Avoid assuming the use of Windows-specific tools or UI patterns (such as 'Test Explorer' in VS Code) as the default; note cross-platform alternatives or limitations.
- Explicitly state platform compatibility for all steps, and add notes or links for Linux/macOS users where workflows or commands differ.
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 moderate Windows bias, primarily through the frequent use of PowerShell and Windows-centric tools (e.g., AzPowerShell, AzureCLI with PowerShell Core, dotnet CLI) in both GitHub Actions and Azure Pipelines examples. PowerShell-based commands and terminology (e.g., 'enableAzPSSession', 'PowerShell@2', 'pscore') are used throughout, and the CLI snippets for running Playwright tests use PowerShell syntax. While the workflows run on Ubuntu runners and npm/node commands are cross-platform, the documentation does not provide explicit Linux shell (bash/sh) equivalents or highlight Linux-native patterns, and Windows/PowerShell tools are often mentioned first or exclusively.
Recommendations
- Provide Linux shell (bash/sh) equivalents for all PowerShell commands and scripts, especially for npm install, Playwright test execution, and authentication steps.
- Where PowerShell is used in workflow tasks (e.g., AzureCLI@2 with 'pscore', PowerShell@2), also show how to use bash or sh scripts for the same steps.
- Avoid using PowerShell-specific flags (like 'enableAzPSSession') in examples unless necessary, or clarify their cross-platform applicability.
- Explicitly mention that all commands and workflows are cross-platform, and highlight any differences or additional steps needed for Linux environments.
- In code snippets and CLI instructions, provide both Windows (PowerShell) and Linux (bash) command formats where applicable.
- If using .NET examples (which are cross-platform), clarify that the commands work on Linux/macOS as well, and provide any OS-specific notes if needed.
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
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-centric tools and workflows, such as Visual Studio Code, PowerShell, and .NET/NUnit, while omitting explicit Linux or cross-platform command-line examples. The use of PowerShell for .NET package installation, references to Visual Studio Code as the primary GUI, and lack of Linux-specific instructions or screenshots suggest an assumption of a Windows development environment.
Recommendations
- Provide explicit Linux/macOS equivalents for all command-line instructions, such as using 'dotnet add package' in a generic shell (bash/zsh) rather than PowerShell, and clarify any OS-specific syntax differences.
- Include screenshots or instructions for using the Azure portal and Playwright CLI from Linux/macOS environments, or note that the experience is the same across platforms.
- Mention and provide examples for popular Linux editors (e.g., VS Code on Linux, Vim, or JetBrains IDEs) where appropriate, or clarify that the instructions are editor-agnostic.
- Ensure that all environment variable setup instructions include both Windows (set/PowerShell) and Linux/macOS (export or .env) methods.
- Add a note in the prerequisites or setup sections to clarify that all steps are cross-platform unless otherwise specified, and explicitly call out any platform-specific requirements.
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
Windows Tools
Missing Linux Example
Summary
The documentation shows a moderate Windows bias. Visual Studio Code (VS Code) and Azure Portal are presented as the primary UI tools, with no mention of Linux-native editors or terminal workflows. The CLI and PowerShell examples are present, but there are no explicit Linux shell or environment variable examples (e.g., export vs. set). The documentation assumes familiarity with Windows-centric tools and patterns, and does not provide Linux-specific guidance for environment setup, authentication, or test execution.
Recommendations
- Include explicit Linux/macOS shell command examples for setting environment variables (e.g., export PLAYWRIGHT_SERVICE_URL=...) alongside Windows/PowerShell equivalents.
- Mention Linux-native editors (e.g., Vim, Nano) or terminal workflows for users not using Visual Studio Code.
- Clarify that all CLI commands (npm, npx, dotnet, az) are cross-platform, and provide any OS-specific notes where behavior may differ.
- Add screenshots or terminal output examples from Linux environments to balance the current Windows/VS Code focus.
- Where file paths or configuration files are referenced, note any differences in path syntax or file permissions that may affect Linux users.
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
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias, primarily through the use of PowerShell commands and references to Windows-centric tools (such as AzPowershell and Azure PowerShell) in both GitHub Actions and Azure Pipelines examples. While the CI runners are set to 'ubuntu-latest' (Linux), the scripts and authentication steps often rely on PowerShell or Windows-specific patterns, and there is a lack of explicit Linux shell (bash/sh) alternatives. Additionally, Windows tools and patterns are mentioned before or instead of their Linux equivalents, and some examples (such as dotnet CLI usage) are shown only in PowerShell or C# contexts, with no explicit Linux shell or cross-platform alternatives.
Recommendations
- Provide equivalent bash/sh shell commands alongside PowerShell examples, especially for authentication and setup steps.
- When referencing Azure CLI or PowerShell, clarify cross-platform compatibility and provide both Windows and Linux command variants where applicable.
- Avoid using Windows-centric terminology (e.g., 'AzPowershell', 'PowerShell@2') as the default; instead, present both PowerShell and bash options, or use platform-agnostic tools where possible.
- Explicitly state that the examples work on both Windows and Linux runners, or provide separate tabs for each OS where commands differ.
- For .NET/NUnit examples, show both Windows and Linux command-line invocations (e.g., dotnet CLI in bash and PowerShell).
- Ensure that all code snippets and workflow steps are tested and documented for both Windows and Linux environments.
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
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Visual Studio Code and Azure Portal (both cross-platform but with a strong Windows association) are featured prominently, and there is a lack of explicit Linux/macOS terminal or shell examples. The only shell commands shown are generic (npm, npx, az login), but there are no Linux-specific instructions or screenshots. The Visual Studio Code workflow is described in detail, but alternative editors or CLI-only workflows (common on Linux) are not mentioned. There are no explicit PowerShell commands, but .NET/NUnit (more common on Windows) is given as an alternative runner, and the documentation does not provide parity for Linux-native tools or environments.
Recommendations
- Add explicit Linux/macOS shell examples (e.g., bash/zsh) where environment variables or CLI commands are set, especially for setting environment variables (e.g., export PLAYWRIGHT_SERVICE_URL=...)
- Include screenshots or instructions for using the Azure Portal from Linux browsers, or mention that the portal is cross-platform.
- Provide parity for Linux-native editors (such as VS Code on Linux, or alternatives like Vim/Emacs) or describe CLI-only workflows for running and debugging Playwright tests.
- Clarify that all CLI commands (npm, npx, az) work on Linux/macOS and Windows, and provide any OS-specific caveats if needed.
- If mentioning .NET/NUnit, also mention popular Linux test runners or frameworks, or clarify cross-platform support.
- Avoid assuming Visual Studio Code as the default editor; mention it as one option among several.
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 moderate Windows bias, primarily through the use of PowerShell commands and Windows-centric Azure tooling (e.g., AzPowershell, PowerShell@2 tasks) in CI/CD pipeline examples. While the workflows are shown running on Ubuntu agents, the scripts and authentication steps often use PowerShell syntax or Windows-specific tools, and PowerShell-based examples are given before or instead of bash equivalents. There is a lack of explicit Linux shell (bash) or cross-platform CLI alternatives for steps like authentication and dependency installation, which may hinder Linux-first or cross-platform users.
Recommendations
- Provide bash/sh equivalents for all PowerShell commands and scripts, especially for authentication and setup steps.
- Show both PowerShell and bash examples side-by-side in CI pipeline YAMLs, or clarify when a step is cross-platform.
- Avoid using Windows-specific tooling (like AzPowershell or PowerShell@2) as the default; prefer Azure CLI or cross-platform tools where possible.
- Explicitly mention and demonstrate Linux-native workflows, including using bash scripts and Linux package managers.
- Ensure that all code snippets and setup instructions are clearly marked as platform-specific, and provide alternatives for Linux/macOS users.
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
Missing Linux Example
Summary
The documentation exhibits a Windows bias primarily through the use of PowerShell commands and references to Windows-centric tools (such as AzPowerShell and Azure PowerShell) in both setup and workflow examples. The authentication and setup instructions often mention PowerShell or Windows tools first or exclusively, with no explicit Linux or cross-platform shell alternatives provided. While the CI runners are set to 'ubuntu-latest', the scripts and instructions assume familiarity with PowerShell, and there are no bash or Linux-native command examples. This may hinder Linux users or those working in non-Windows environments.
Recommendations
- Provide equivalent bash or sh examples for all PowerShell commands, especially for steps like installing dependencies, authentication, and running Playwright tests.
- When referencing Azure CLI or authentication, include both Azure PowerShell and Azure CLI instructions, and clarify which is cross-platform.
- Avoid using PowerShell-specific syntax in generic instructions; prefer platform-agnostic commands where possible.
- Explicitly mention that all steps are cross-platform, or provide separate tabs/examples for Windows (PowerShell), Linux (bash), and macOS where relevant.
- For CI workflow YAML, show both PowerShell and bash script blocks, or use shell: bash for Linux runners.
- Ensure that all tool references (such as 'AzPowerShell') are accompanied by their Linux/macOS equivalents or alternatives.
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
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Visual Studio Code (VS Code) is the only editor/IDE mentioned for graphical test running, and all screenshots and UI instructions are based on the Azure Portal, which is most commonly accessed from Windows environments. The .NET/NUnit example uses PowerShell syntax for package installation and does not provide a Linux/Unix alternative. There are no explicit Linux-specific instructions, terminal commands, or references to Linux-native tools or editors (such as VS Code on Linux, JetBrains Rider, or CLI-only workflows). The documentation assumes familiarity with Windows-centric tools and patterns, and does not provide parity for Linux users in terms of setup, environment variable configuration, or test running outside the VS Code ecosystem.
Recommendations
- Include explicit Linux/Unix shell command equivalents for all PowerShell or Windows CLI commands (e.g., use 'dotnet add package ...' and 'export VAR=...' in bash).
- Mention that Visual Studio Code is cross-platform, and provide instructions or screenshots for Linux/macOS users where applicable.
- Add examples for setting environment variables in Linux/macOS shells (e.g., 'export PLAYWRIGHT_SERVICE_URL=...').
- Reference Linux-native editors or CLI workflows for running and debugging tests, not just Visual Studio Code.
- Clarify that the Azure Portal is web-based and accessible from any OS, and provide any OS-specific caveats if relevant.
- Ensure all code snippets and setup steps are presented in both Windows and Linux/macOS variants, especially for .NET/NUnit and Playwright CLI usage.
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
Windows Tools
Missing Linux Example
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/macOS instructions or screenshots. The CLI and environment setup sections assume familiarity with Windows developer tooling and do not provide parity for Linux users, especially regarding environment variable management, editor integration, and .NET/NUnit usage.
Recommendations
- Provide explicit Linux/macOS instructions and screenshots alongside Windows/Visual Studio Code examples, especially for environment setup and running tests.
- Include alternative editor workflows (e.g., JetBrains Rider, Vim, or command-line only) for users not on Windows or not using Visual Studio Code.
- For .NET/NUnit sections, clarify cross-platform compatibility and provide Linux/macOS-specific commands or troubleshooting tips.
- When referencing environment variables, show both Windows (set/PowerShell) and Linux/macOS (export) syntax.
- Avoid assuming Visual Studio Code as the default editor; mention it as one option among several.
- Add a section or callout explicitly stating that all steps are cross-platform unless otherwise noted, and link to Playwright's official cross-platform documentation.
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 moderate Windows bias, primarily through the use of PowerShell commands and references to Windows-centric tools (e.g., AzPowerShell, PowerShell@2 tasks) in CI/CD examples. While the workflows are shown running on Ubuntu runners, the scripting and authentication steps often default to PowerShell or Windows-specific patterns. There is little to no mention of Linux shell equivalents or alternative Linux-native tooling, and PowerShell-based steps are presented without parallel bash/sh alternatives. Additionally, Windows/PowerShell terminology is used before or instead of Linux equivalents, especially in Azure Pipelines sections.
Recommendations
- Provide equivalent bash/sh script examples alongside PowerShell commands for installing dependencies, running tests, and authentication steps.
- In Azure Pipelines, offer both PowerShell and bash scriptType examples, or default to bash where possible for cross-platform compatibility.
- Clarify that AzPowerShell and PowerShell@2 tasks are not required if using Linux runners, and provide guidance for using AzureCLI or bash scripts.
- Explicitly mention Linux-native tools and patterns where applicable (e.g., using export for environment variables, using bash for scripting).
- Ensure that Linux and macOS users are equally represented in code snippets and workflow steps, not just by the runner OS but also by the scripting language and tools.
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
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Visual Studio Code (VS Code) is emphasized as the primary IDE for running and debugging tests, with screenshots and instructions tailored to this environment, which is most popular on Windows. There is no mention of Linux-specific tools, shells, or editors, nor are there any Linux-specific instructions or screenshots. All CLI and shell commands are generic, but the lack of explicit Linux parity (e.g., mentioning Bash, Linux package managers, or Linux desktop environments) and the exclusive use of VS Code and Azure Portal (both with a strong Windows user base) indicate a subtle preference for Windows workflows. Additionally, there are no explicit Linux or macOS examples, nor any mention of platform-specific considerations for environment variables or authentication.
Recommendations
- Add explicit Linux/macOS instructions and screenshots where relevant, such as showing terminal commands in Bash and referencing common Linux editors (e.g., Vim, Nano) for editing configuration files.
- Include notes about setting environment variables in Linux/macOS shells (e.g., export PLAYWRIGHT_SERVICE_URL=...) alongside the .env approach.
- Mention and provide examples for running Playwright tests in popular Linux IDEs or editors (e.g., JetBrains IDEs, GNOME Builder), or clarify that the instructions are cross-platform.
- Where Visual Studio Code is referenced, note that it is available cross-platform and provide links or instructions for Linux/macOS installation.
- Add troubleshooting tips or notes for Linux users, such as permissions, package installation, or differences in CLI usage.
- Balance screenshots and instructions to reflect both Windows and Linux environments, or use neutral, cross-platform imagery where possible.
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
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: PowerShell and Windows-specific tools (e.g., AzPowershell, Azure PowerShell, PowerShell@2 tasks) are used or referenced in CI examples and authentication setup, often without equivalent Bash or Linux shell examples. The use of PowerShell is shown in both GitHub Actions and Azure Pipelines, and Windows tools are mentioned before or instead of cross-platform/Linux alternatives. There are no explicit Linux shell (bash/sh) command examples for common developer workflows, and the documentation does not provide parity for Linux-first or cross-platform users.
Recommendations
- For every PowerShell or Windows-specific command or task, provide an equivalent Bash (sh) example, especially for CI/CD steps.
- In authentication setup, include Azure CLI (az) commands alongside Azure PowerShell, and clarify which commands are cross-platform.
- When referencing tools or scripts (e.g., 'PowerShell@2', 'AzPowershell'), also show how to accomplish the same with Bash or cross-platform alternatives.
- Avoid using Windows-specific terminology or tools as the default; instead, present cross-platform or Linux-first options first, or at least side-by-side.
- Explicitly mention that all workflows and commands are supported on Linux runners (e.g., Ubuntu) and provide sample shell commands for local Linux development.
- Add a section or callout for Linux/macOS users, highlighting any differences or confirming full support.
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
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation exhibits a Windows bias by using PowerShell syntax for all command-line examples (e.g., git, npm, npx commands), and by referring to 'terminal or command window' without clarifying cross-platform differences. There are no explicit Linux/macOS shell examples or notes about platform-specific differences, and the use of PowerShell prompt style (```powershell) may confuse Linux/macOS users. Additionally, Visual Studio Code is listed as a prerequisite without mention of alternative editors, which may reinforce a Windows-centric workflow.
Recommendations
- Provide all shell command examples using generic shell syntax (e.g., ```sh or ```bash) instead of PowerShell, or show both Windows (PowerShell/CMD) and Linux/macOS (bash/sh) variants side by side.
- Explicitly mention that the commands work on Linux/macOS and Windows, and note any platform-specific differences (such as environment variable syntax, path separators, etc.).
- In the prerequisites, clarify that Visual Studio Code is cross-platform, and optionally mention that any code editor can be used.
- Where 'terminal or command window' is referenced, clarify that this can be PowerShell, Command Prompt, Terminal (macOS), or a Linux shell.
- Add a section or callouts for Linux/macOS users, especially for steps involving environment variables, authentication, or file paths.
- Avoid using PowerShell-specific code blocks unless there is a Windows-only step; otherwise, prefer neutral shell syntax.
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
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Visual Studio Code (VS Code) is the only editor/IDE mentioned for local test running, and all GUI screenshots are from the Azure Portal, which is platform-agnostic but often associated with Windows workflows. There are no explicit Linux/macOS-specific instructions, terminal screenshots, or mentions of alternative editors or shells. The environment setup and CLI commands are generally cross-platform, but the documentation assumes familiarity with Windows-centric tools and patterns, especially in the 'Run your tests' and 'Set up your environment' sections. There are no Linux/macOS-specific troubleshooting tips, and the only editor extension referenced is for VS Code.
Recommendations
- Add explicit Linux/macOS instructions or notes where relevant, such as for environment variable setup, CLI usage, and file paths.
- Include at least one example or screenshot using a Linux/macOS terminal or file explorer to demonstrate parity.
- Mention alternative editors (such as JetBrains IDEs, Atom, or even Vim/Emacs) or at least clarify that the steps work in any editor, not just Visual Studio Code.
- Provide troubleshooting tips or notes for common Linux/macOS issues (e.g., file permissions, line endings, shell differences).
- Where screenshots are used, consider including at least one from a Linux or macOS environment to visually reinforce cross-platform support.