App Testing
146
Total Pages
130
Linux-Friendly Pages
16
Pages with Bias
11.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
28 issues found
Showing 1-25 of 28 flagged pages
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily biased towards Windows and PowerShell. All command-line examples use PowerShell syntax, and the workflow assumes the user is operating in a Windows environment. Linux and macOS users are only briefly mentioned in a tip about installing PowerShell, but no native Bash or shell alternatives are provided. The deployment script is a PowerShell script, with no mention of a Bash/sh equivalent.
Recommendations
- Provide Bash or shell script alternatives for Linux/macOS users, especially for deployment steps.
- Show command examples using native Linux/macOS tools and syntax (e.g., 'cd', './deploymentscript.sh' if available).
- If the deployment script is only available in PowerShell, consider providing a cross-platform version or containerized deployment instructions.
- List Linux/macOS instructions alongside Windows, not only as a tip.
- Reference Azure CLI and other cross-platform tools before platform-specific ones.
Create Pull Request
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 deploying the sample application. All command-line examples use PowerShell syntax, and the deployment script is a PowerShell script. Linux and macOS users are only briefly mentioned in a tip about installing PowerShell, but no native Bash or shell examples are provided. The documentation also references Windows tools and patterns (e.g., .ps1 scripts, PowerShell modules) without offering Linux alternatives.
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, sh), or provide a cross-platform script.
- Mention Linux-first approaches, such as using Azure CLI directly in Bash, and list these before or alongside Windows/PowerShell instructions.
- Reference Linux-specific tools or commands where applicable, such as using 'curl' or 'wget' for downloading files, and provide region code lookup via Azure CLI instead of PowerShell modules.
- Clearly indicate which steps are platform-specific and offer parity for each major OS.
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
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell examples for command-line role management, with no mention of Azure CLI or Bash equivalents commonly used on Linux and macOS. The 'Configure Azure RBAC' section presents PowerShell before any cross-platform alternatives, and does not reference Linux-specific tools or workflows. This may hinder Linux users who do not use PowerShell.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, using Bash syntax where appropriate.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux, macOS, and Windows.
- Provide links to Azure CLI documentation alongside PowerShell references.
- Consider reordering sections to present cross-platform tools (Azure CLI) before platform-specific ones (PowerShell).
- Include troubleshooting steps and examples relevant to Linux environments.
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 are provided alongside Azure CLI and portal instructions, but PowerShell is often presented before CLI. The use of PowerShell-specific cmdlets and terminology (e.g., New-AzKeyVault, Add-AzKeyVaultKey) reflects a Windows-centric approach. There are no explicit Linux shell examples (e.g., Bash), nor is there mention of Linux-specific tooling or patterns. The documentation assumes familiarity with Windows tools and workflows, which may disadvantage Linux users.
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 Bash shell usage notes where relevant.
- Add example shell commands using Bash (e.g., variable assignment, piping output) to illustrate Linux-native workflows.
- Avoid referring to PowerShell as the default automation tool; clarify that both PowerShell and Azure CLI are supported.
- Where screenshots or UI instructions are given, clarify any OS-specific differences (if any) in the Azure portal experience.
- Consider adding a section or note for Linux users, highlighting best practices or common issues when using Azure CLI and Key Vault.
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 page demonstrates a bias towards Windows environments and tooling. PowerShell and AzPowershell are used in CI examples, and Windows-centric tools (PowerShell, Azure PowerShell) are referenced for authentication and setup. There is a lack of explicit Linux shell (bash/sh) examples, and Windows tools are mentioned before their Linux equivalents, even in contexts (CI runners) that are cross-platform. The documentation does not provide parity for Linux-native commands or workflows, and assumes familiarity with Windows/PowerShell patterns.
Recommendations
- Provide equivalent bash/sh examples for all PowerShell commands, especially for CI/CD steps and authentication.
- Reference cross-platform Azure CLI commands before or alongside Azure PowerShell, especially for authentication and service principal creation.
- Explicitly mention Linux and macOS compatibility in setup instructions, and provide examples for these platforms.
- Avoid using Windows-specific terminology (e.g., 'AzPowershell') as the default; clarify when steps are platform-specific.
- Add a section or tab for Linux-first workflows, including common shell usage and troubleshooting tips for non-Windows environments.
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 a Windows bias by exclusively using PowerShell syntax for command-line examples (e.g., 'cd', 'git clone', 'npm install'), and does not provide Linux/macOS-specific shell examples or mention platform differences. The use of 'terminal or command window' language and the absence of explicit Linux instructions or screenshots further reinforce the Windows-centric approach.
Recommendations
- Provide command-line examples using both PowerShell/Command Prompt and Bash/zsh syntax, or use cross-platform commands where possible.
- Explicitly mention that instructions apply to Windows, Linux, and macOS, and clarify any platform-specific steps.
- Include screenshots or references for Linux/macOS environments where relevant (e.g., terminal, file paths).
- Avoid using only Windows terminology such as 'command window'; use 'terminal' or specify both.
- Add a section or note about platform compatibility and any differences in setup or 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
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by consistently referencing Windows-centric tools and workflows, such as the Azure portal (with Windows-style screenshots), Visual Studio Code, and PowerShell/dotnet commands. There is a lack of explicit Linux or cross-platform examples for key steps (e.g., environment variable setup, CLI usage, authentication), and no mention of Linux-specific tools or terminal environments. The instructions and visuals assume a Windows user experience, with no guidance for Linux users on alternative workflows.
Recommendations
- Add explicit Linux and macOS examples for CLI commands, environment variable setup, and file paths (e.g., bash, zsh, export PLAYWRIGHT_SERVICE_URL).
- Include screenshots or instructions for using Azure portal and Playwright CLI from Linux desktop environments.
- Mention alternative editors (e.g., VS Code on Linux, Vim, etc.) and provide parity for test running outside Visual Studio Code.
- Clarify that the Azure CLI and Playwright CLI are cross-platform, and provide troubleshooting tips for Linux users.
- Where PowerShell or dotnet commands are shown, also show equivalent bash/zsh commands for Linux users.
- Add a section or callout for Linux prerequisites (e.g., installing Node.js, Azure CLI on Linux) and note any OS-specific considerations.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes managing workspace access using the Azure portal GUI, with screenshots and instructions tailored to the portal interface. There are no examples or references to command-line tools (such as Azure CLI or PowerShell), nor are Linux/macOS-specific workflows or tools mentioned. While the Azure portal is cross-platform via web browser, many Linux users prefer or require CLI-based management, which is not covered.
Recommendations
- Add instructions and examples for managing workspace access using Azure CLI, which is available on Linux, macOS, and Windows.
- Include references to relevant Azure CLI documentation for role assignment and revocation.
- If PowerShell examples are added in the future, ensure Azure CLI equivalents are provided and shown first or side-by-side.
- Explicitly state that the Azure portal is accessible from any OS via browser, but highlight CLI alternatives for automation and scripting.
App Testing
Tutorial: Run end-to-end tests with Playwright Workspaces
...playwright-workspaces/tutorial-run-end-to-end-tests.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting all command-line examples using PowerShell syntax (e.g., 'cd', 'git clone', 'npm install') without mentioning Linux/macOS shell equivalents. The use of 'powershell' code blocks and terminology like 'command window' and 'terminal' is ambiguous, but the examples are written in a way most familiar to Windows users. There are no explicit Linux/macOS instructions or screenshots, and installation/usage patterns (such as Azure CLI and authentication) do not clarify cross-platform differences.
Recommendations
- Provide Linux/macOS shell examples (e.g., bash/zsh) alongside PowerShell commands, using appropriate code block annotations.
- Clarify that all CLI commands work on Linux/macOS and note any platform-specific differences.
- Include screenshots or instructions for Linux/macOS environments where relevant (e.g., terminal usage, file paths).
- Explicitly mention that tools like Azure CLI, Git, and npm are cross-platform and provide links to Linux/macOS installation guides.
- Avoid using only PowerShell code blocks; use 'shell' or 'bash' where appropriate, or show both.
App Testing
Manage roles in Azure Load Testing
...ticles/app-testing/load-testing/how-to-assign-roles.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides detailed instructions and examples for managing Azure RBAC using the Azure portal and PowerShell, both of which are Windows-centric tools. There are no examples or guidance for using cross-platform command-line tools like Azure CLI, nor are Linux/macOS-specific workflows or shell commands mentioned. This creates friction for users on Linux or macOS who may prefer or require non-Windows tooling.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell cmdlets shown, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Explicitly mention that Azure CLI can be used on Linux/macOS and provide links to relevant documentation.
- Consider including Bash shell examples for common tasks, or at least note the parity between PowerShell and CLI commands.
- Reorder sections so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell, to avoid Windows-first perception.
App Testing
Quickstart: Automate load tests with CI/CD
...-testing/load-testing/quickstart-add-load-test-cicd.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exclusively describes automating load tests using Azure Pipelines and Azure DevOps, which are traditionally Windows-centric platforms. All examples, screenshots, and instructions are focused on Azure Pipelines, with no mention of Linux/macOS-specific workflows, tools, or command-line examples. While there is a brief reference to GitHub Actions as an alternative, it is relegated to a 'Next steps' link and not covered in the main guide. There are no examples or guidance for Linux-native CI/CD tools (e.g., Jenkins, GitLab CI), nor any platform-agnostic command-line instructions.
Recommendations
- Provide parallel examples for configuring CI/CD pipelines using Linux/macOS environments and tools, such as GitHub Actions, Jenkins, or GitLab CI.
- Include command-line instructions that work across platforms (bash, shell scripts) rather than relying solely on portal-based or GUI workflows.
- Add screenshots and walkthroughs for Linux/macOS users, especially for steps that may differ from Windows/Azure DevOps workflows.
- Elevate the GitHub Actions workflow to a first-class section in the quickstart, not just as a 'Next steps' link.
- Mention platform requirements and clarify which steps are platform-agnostic.
App Testing
Quickstart: Continuous end-to-end testing
...t-workspaces/quickstart-automate-end-to-end-testing.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Many examples and workflow steps reference PowerShell, AzPowershell, and Windows-centric tools (e.g., Azure PowerShell, PowerShell@2, scriptType: 'pscore'). While CI examples use 'runs-on: ubuntu-latest', the authentication and setup steps often default to PowerShell or Windows-specific patterns. Linux/macOS equivalents (e.g., Bash, Azure CLI) are not provided or are mentioned after Windows tools. There are no explicit Linux/macOS command-line examples for authentication or setup, and PowerShell is assumed for scripting in Azure Pipelines.
Recommendations
- Provide equivalent Bash/Azure CLI examples for authentication and setup steps, especially for Linux/macOS users.
- Explicitly mention that PowerShell steps can be replaced with Bash/Azure CLI on non-Windows runners.
- Add notes or code samples for Linux/macOS environments where PowerShell is not available or not preferred.
- Reorder examples so that cross-platform or Linux/macOS instructions are shown first or alongside Windows/PowerShell instructions.
- Clarify that 'scriptType: pscore' is for PowerShell Core and provide alternatives for Bash.
- Ensure all critical setup steps (authentication, package installation, running tests) have Linux/macOS parity.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes managing workspace access using the Azure portal UI, which is a web-based interface accessible from any OS. However, it does not mention or provide examples for command-line alternatives such as Azure CLI or Azure PowerShell, which are commonly used on both Windows and Linux/macOS. The absence of CLI instructions or parity means Linux/macOS users who prefer or require automation or terminal-based workflows are underserved. The documentation implicitly assumes a graphical workflow, which is more typical for Windows users.
Recommendations
- Add instructions and examples for managing workspace access using Azure CLI, which is cross-platform and widely used on Linux/macOS.
- Include Azure PowerShell examples for completeness, but ensure Azure CLI is presented first or alongside PowerShell to avoid Windows-first bias.
- Explicitly state that all portal-based steps can be performed from any OS with a supported browser.
- Where screenshots are used, clarify that the portal UI is OS-agnostic.
App Testing
Quickstart: Automate load tests with CI/CD
...-testing/load-testing/quickstart-add-load-test-cicd.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page is heavily focused on Azure DevOps and Azure Pipelines, which are traditionally Windows-centric tools. All examples and screenshots reference the Azure portal and Azure DevOps UI, with no mention of Linux/macOS-specific workflows, CLI commands, or alternative CI/CD systems except for a brief link to GitHub Actions. There are no examples or guidance for users who may want to automate load tests using Linux-native tools or pipelines (e.g., Jenkins, GitLab CI, or CLI-only workflows).
Recommendations
- Add explicit examples for configuring CI/CD pipelines using Linux/macOS environments, such as Azure CLI, Bash scripts, or YAML files that can be run cross-platform.
- Provide parity by including screenshots or instructions for command-line workflows, not just portal/UI-based steps.
- Include references and step-by-step guides for integrating Azure Load Testing with other popular CI/CD tools (e.g., Jenkins, GitLab CI) that are widely used on Linux.
- Clarify that Azure DevOps and Azure Pipelines are cross-platform and can be used from Linux/macOS, and provide any necessary setup instructions for those platforms.
- Move the mention of GitHub Actions out of the prerequisites and into the main flow, with a direct comparison or alternative workflow.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is heavily oriented towards Windows and PowerShell. All command examples use PowerShell syntax, and the workflow assumes the use of PowerShell scripts for deployment. Linux and macOS users are only briefly mentioned in a tip about installing PowerShell, with no native Bash or shell alternatives provided. The initial instructions reference 'Windows PowerShell' and do not offer Linux-first or cross-platform guidance.
Recommendations
- Provide Bash or shell script alternatives for cloning the repo and running deployment steps.
- Include Linux/macOS-specific instructions alongside Windows/PowerShell examples, not just as a tip.
- List cross-platform commands first, or in parallel, rather than starting with Windows-specific instructions.
- If the deployment script is PowerShell-only, offer a Bash version or containerized alternative for Linux/macOS users.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes usage of the Azure portal UI for optimizing Azure Functions, without mentioning command-line alternatives or platform-specific tooling. There are no examples using PowerShell, but the workflow assumes use of the Azure portal, which is most commonly accessed from Windows environments. No Linux-specific tools, CLI commands, or parity examples (such as Azure CLI or Bash scripting) are provided, and there is no mention of how to perform these tasks from Linux or cross-platform environments.
Recommendations
- Add Azure CLI examples for creating and managing test profiles, running load tests, and viewing results, ensuring parity with portal-based instructions.
- Include explicit instructions or links for performing these tasks from Linux/macOS environments.
- Mention cross-platform access to the Azure portal, and clarify that all steps can be performed from any OS with a supported browser.
- Where screenshots are provided, consider including CLI output or terminal screenshots alongside portal UI images.
- Highlight any differences or considerations for Linux users, such as authentication methods or required tools.
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/load-testing/how-to-create-and-run-load-test-with-jmeter-script.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/load-testing/how-to-create-and-run-load-test-with-jmeter-script.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure CLI examples using Windows-style variable assignment and shell syntax, without any Linux-specific instructions or examples. There is no mention of Linux shell equivalents, nor are there references to Linux tools or usage patterns. The CLI examples use syntax (e.g., variable assignment with quotes and backticks) that is specific to Windows CMD or PowerShell, which may not work as-is on Linux or macOS terminals.
Recommendations
- Add Linux/bash-specific examples for Azure CLI usage, including correct variable assignment and command syntax.
- Explicitly mention cross-platform compatibility for the Azure CLI, and provide instructions for both Windows (CMD/PowerShell) and Linux/macOS (bash/zsh).
- Include notes or tabs that show how to run the CLI commands on Linux/macOS, highlighting any differences in syntax or environment setup.
- Ensure screenshots and instructions do not assume a Windows environment unless explicitly stated, and provide parity for Linux users.
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/load-testing/how-to-create-manage-test-runs.md
...testing/load-testing/how-to-create-manage-test-runs.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes managing Azure Load Testing test runs via the Azure portal, which is a web-based GUI and does not reference any command-line tools or platform-specific instructions. However, all screenshots and navigation instructions implicitly assume a Windows environment (e.g., terminology like 'ellipsis (...)', left pane navigation, and context menus), and there is no mention of Linux-specific workflows, CLI, or automation options. No PowerShell or Windows-only tools are mentioned, but there is a lack of parity for Linux users who may prefer CLI or non-GUI workflows.
Recommendations
- Add instructions for managing test runs using Azure CLI or REST API, including examples for both Windows (PowerShell, Command Prompt) and Linux (Bash).
- Include screenshots or descriptions that are platform-neutral, or explicitly mention that the Azure portal is accessible from any OS.
- Provide links or sections for automation and scripting options, highlighting cross-platform compatibility.
- Clarify that the Azure portal is web-based and does not require a Windows environment, to avoid implicit Windows bias.
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/load-testing/how-to-move-between-regions.md
...pp-testing/load-testing/how-to-move-between-regions.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively uses the Azure Portal (GUI) for all steps and does not mention or provide examples for command-line tools such as Azure CLI, PowerShell, or Bash. While this avoids explicit Windows tool bias, the lack of Linux-friendly CLI instructions means users on Linux or those preferring automation are underserved. The workflow assumes a graphical interface, which is more common on Windows, and does not address parity for Linux users.
Recommendations
- Add equivalent instructions using Azure CLI commands for exporting, modifying, and deploying ARM templates.
- Include examples for downloading test artifacts using CLI or automation scripts.
- Provide guidance for recreating resources and tests via command-line tools (Azure CLI, Bash, PowerShell), and mention cross-platform compatibility.
- Explicitly state that all steps can be performed on Linux, Mac, and Windows, and link to CLI documentation where appropriate.
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 →
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 associated with Windows environments. All examples, screenshots, and step-by-step instructions focus on Azure Pipelines and the Azure portal, with no mention of Linux-native CI/CD tools (such as Jenkins, GitLab CI, or Travis CI), nor any command-line or scripting examples for Linux shells. The only alternative (GitHub Actions) is relegated to a single sentence and links to a separate manual configuration guide, rather than being presented alongside Azure Pipelines. There is no discussion of Linux-specific workflows, tools, or patterns.
Recommendations
- Provide parallel examples for Linux-native CI/CD tools (e.g., Jenkins, GitLab CI, Travis CI) and show how to automate Azure Load Testing from those environments.
- Include command-line examples using Bash or other Linux shells for configuring and triggering load tests, in addition to portal-based workflows.
- Present GitHub Actions automation steps in the main quickstart, not only as a separate manual configuration link.
- Add notes or sections on how the process differs (if at all) for users working on Linux or macOS environments.
- Ensure screenshots and instructions do not assume Windows-only tools or interfaces, and clarify cross-platform compatibility where relevant.
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/playwright-workspaces/how-to-manage-access-tokens.md
...g/playwright-workspaces/how-to-manage-access-tokens.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exclusively describes managing workspace access tokens via the Azure portal UI, which is a web-based interface and not inherently OS-specific. However, there are no command-line examples or references to CLI tools (such as Azure CLI, PowerShell, Bash, etc.), nor any mention of Linux-specific workflows. The absence of CLI examples means that users on Linux (or those preferring automation/scripting) are not provided with parity or guidance, while Windows users may implicitly benefit from the default association with Azure portal and PowerShell in Microsoft documentation. There is a subtle 'Windows-first' bias due to the lack of cross-platform command-line instructions.
Recommendations
- Add Azure CLI examples for creating, viewing, and deleting access tokens, ensuring commands work on both Windows and Linux.
- Explicitly mention that all portal-based instructions apply equally to users on any OS, and provide links to CLI documentation.
- Include Bash script examples for Linux users to automate token management.
- If PowerShell is referenced in other related documentation, ensure Bash/Azure CLI equivalents are provided and linked.
- Clarify any OS-specific limitations or considerations for managing access tokens.
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/playwright-workspaces/how-to-configure-visual-comparisons.md
...ight-workspaces/how-to-configure-visual-comparisons.md
Medium Priority
View Details →
Detected Bias Types
Linux First
Missing Windows Example
Summary
The documentation page consistently uses Linux as the reference OS for configuring visual comparisons and snapshot paths in Playwright Workspaces. All code examples hardcode 'linux' as the OS, and the service configuration explicitly sets the OS to Linux. There are no examples or guidance for Windows users, nor is there mention of how to adapt the configuration for Windows environments.
Recommendations
- Provide equivalent configuration examples for Windows, such as using 'windows' in snapshotPathTemplate and ServiceOS.
- Add guidance for users running Playwright Workspaces on Windows, including any differences in path formats or expected behavior.
- Explicitly mention how to switch between Linux and Windows in the configuration, and discuss cross-platform considerations.
- Ensure that both Linux and Windows users are addressed in documentation, with examples and troubleshooting tips for each.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes managing Playwright Workspace access using the Azure portal GUI, which is primarily accessed via a web browser on Windows. There are no examples or instructions for managing access using cross-platform command-line tools such as Azure CLI, nor are there any Linux-specific patterns or alternatives mentioned. This results in a Windows-first and GUI-centric bias, with missing parity for Linux users who may prefer or require CLI-based workflows.
Recommendations
- Add examples for managing workspace access using Azure CLI commands, which are available on both Windows and Linux.
- Include instructions for using Azure PowerShell and explicitly note its cross-platform support, or provide Bash shell equivalents.
- Mention that all Azure portal operations can be performed from any OS with a supported browser, but highlight CLI alternatives for automation and Linux environments.
- Provide sample scripts for role assignment and revocation using Azure CLI (az role assignment), and link to relevant CLI documentation.
- Ensure screenshots and step-by-step instructions are supplemented with text-based commands for parity.
App Testing
Configure customer-managed keys for encryption
...load-testing/how-to-configure-customer-managed-keys.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation consistently presents Windows-centric tools and patterns, such as PowerShell and Azure Portal, before cross-platform alternatives like Azure CLI. PowerShell examples are given equal prominence to Azure CLI, and the Azure Portal (a GUI, often associated with Windows environments) is always listed first in tabbed instructions. There are no Linux/macOS-specific examples or mentions of platform-specific considerations, and no references to Linux-native scripting or automation tools. All command-line instructions use either PowerShell or Azure CLI, which is cross-platform, but the ordering and emphasis favor Windows users.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is natively cross-platform and preferred by Linux/macOS users.
- Explicitly mention that Azure CLI commands work on Linux/macOS and provide any necessary platform-specific notes (e.g., shell quoting, file paths).
- Add a brief section or note for Linux/macOS users, confirming full parity and listing any prerequisites (such as installing Azure CLI on Linux).
- Consider including bash script examples for automation, or at least mention that bash and other shells are supported.
- Where screenshots are shown, clarify that the Azure Portal is web-based and accessible from any OS.
App Testing
Quickstart: Perform advanced diagnostics with Playwright Workspaces reporting
...vanced-diagnostic-with-playwright-workspaces-reporting.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently references the Azure portal and Visual Studio Code, both of which are cross-platform but have a strong association with Windows environments. All screenshots and step-by-step instructions use the Azure portal UI, with no mention of command-line alternatives or Linux-native tools. The only authentication example uses Azure CLI, which is cross-platform, but there are no explicit Linux/macOS shell examples (e.g., bash vs. PowerShell). Environment variable setup uses Node.js and dotenv, which is cross-platform, but there are no explicit Linux/macOS shell commands for setting environment variables. The tip for opening a new tab uses the Windows-style 'Ctrl' key, with no mention of 'Cmd' for macOS. There are no PowerShell-specific commands, but the overall flow assumes familiarity with Windows-centric tooling and UI.
Recommendations
- Add explicit Linux/macOS shell examples for setting environment variables (e.g., export PLAYWRIGHT_SERVICE_URL=...)
- Include notes or screenshots for Azure portal on Linux/macOS browsers, or mention that all steps are identical across platforms
- When referencing keyboard shortcuts, mention both Windows ('Ctrl') and macOS ('Cmd') keys
- Provide CLI-only alternatives for Azure portal steps where possible (e.g., using Azure CLI to create resources, assign roles, configure storage)
- Clarify that Visual Studio Code and Azure CLI are fully supported on Linux/macOS, and link to installation guides for those platforms