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 51-75 of 99 flagged pages
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 subtle Windows bias by prioritizing Windows-centric tools and workflows, such as the Azure Portal UI (which is most commonly used on Windows), Visual Studio Code (with screenshots and instructions), and .NET/NUnit examples. There is a lack of explicit Linux/macOS terminal examples, and no mention of platform-specific differences or parity. The CLI instructions are generic, but the focus on Visual Studio Code and .NET/NUnit (both more common in Windows environments) without parallel Linux/macOS guidance or screenshots may leave Linux users underserved.
Recommendations
- Add explicit Linux/macOS terminal examples and clarify that all CLI commands work cross-platform.
- Include screenshots or instructions for running Playwright tests from Linux/macOS terminals, not just Visual Studio Code or Azure Portal.
- Mention any platform-specific prerequisites or differences (e.g., environment variable syntax differences between Windows and Unix shells).
- Provide parity in .NET/NUnit and Node.js/Playwright examples for both Windows and Linux environments.
- Clarify that Visual Studio Code is cross-platform, and optionally include screenshots from Linux/macOS versions.
- Where PowerShell or Windows-specific commands are shown, also provide bash/zsh equivalents.
Create Pull Request
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 (a Microsoft product popular on Windows) is the only IDE mentioned for test running, and all screenshots and portal instructions are Windows-centric. There are no explicit Linux/macOS-specific instructions, CLI examples, or screenshots. The use of PowerShell for .NET package installation and the absence of Linux/macOS equivalents (e.g., bash or zsh) further reinforce the bias. The documentation assumes familiarity with Windows tools and patterns, and does not provide parity for Linux users in environment setup, CLI usage, or troubleshooting.
Recommendations
- Provide explicit Linux/macOS CLI examples alongside Windows/PowerShell commands (e.g., use both 'dotnet add package ...' and 'dotnet add package ...' in bash/zsh).
- Include screenshots or instructions that are platform-agnostic or show both Windows and Linux environments where possible.
- Mention and demonstrate how to run Playwright tests from common Linux shells (bash, zsh) and editors (such as VS Code on Linux, or alternatives like Vim/Emacs).
- Clarify that the Azure CLI and Playwright tools are cross-platform, and provide any Linux/macOS-specific installation or troubleshooting tips.
- Avoid assuming Visual Studio Code is the only or default editor; mention that any editor or terminal can be used.
- Add a note or section for Linux/macOS users on environment variable setup, file paths, and permissions if 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
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It consistently references the Azure portal (a web UI, but often associated with Windows-centric workflows), Visual Studio Code (with screenshots and instructions), and .NET/NUnit (with PowerShell/dotnet CLI commands). There is no mention of Linux-specific workflows, tools, or terminal environments. All CLI examples are generic, but the focus on Visual Studio Code and .NET/NUnit, as well as the absence of Linux/macOS-specific instructions or screenshots, suggests a Windows-first approach. There are no explicit Linux shell or environment variable examples (e.g., export vs. set), and no mention of Linux package managers or shell environments.
Recommendations
- Add explicit Linux/macOS shell examples for setting environment variables (e.g., export PLAYWRIGHT_SERVICE_URL=...) alongside Windows/PowerShell equivalents.
- Include screenshots or instructions for running Playwright tests in popular Linux environments or terminals.
- Mention cross-platform compatibility for the Azure CLI and Playwright CLI, and provide installation links or notes for Linux/macOS users.
- Balance Visual Studio Code instructions with alternative editors or CLI-only workflows, especially for Linux users.
- Clarify that all steps and tools (Azure CLI, Playwright CLI, .NET, etc.) are cross-platform, and provide troubleshooting notes for Linux/macOS where appropriate.
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 configuring Azure RBAC, with no mention or examples of cross-platform tools such as Azure CLI or Bash scripting. The PowerShell section is detailed and includes multiple cmdlet examples, while there is no equivalent section for Linux/macOS users. The only command-line automation path described is via PowerShell, which is primarily a Windows tool, though available cross-platform. There is also no mention of Bash, shell, or Azure CLI commands, and the portal instructions do not address OS-specific nuances.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell cmdlets shown, using Bash syntax where appropriate.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Structure the 'Configure Azure RBAC' section to present both PowerShell and Azure CLI options, or provide a table comparing both approaches.
- Ensure that troubleshooting and automation guidance is not limited to Windows/PowerShell, but also addresses Linux/macOS environments.
- Where possible, use neutral language such as 'command-line tools' and clarify when instructions are OS-specific.
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 (.ps1) with no alternative for Bash or native Linux shell. The instructions explicitly start with 'Open Windows PowerShell,' and while there is a tip about installing PowerShell on Linux/macOS, there are no native Linux shell or Bash examples. Additionally, references to tools and commands (such as Get-AzLocation) are PowerShell-specific, with no mention of Azure CLI or cross-platform alternatives.
Recommendations
- Provide equivalent Bash or native Linux shell examples for all steps, especially for cloning the repo and running deployment scripts.
- Offer a Bash or shell script alternative to the PowerShell deployment script, or document how to perform the deployment using Azure CLI commands.
- Present cross-platform instructions first, or at least in parallel with Windows/PowerShell instructions, to avoid the 'Windows-first' impression.
- Reference Azure CLI commands (which are cross-platform) instead of or in addition to PowerShell-specific commands like Get-AzLocation.
- Clearly indicate which steps are platform-specific and provide guidance for both Windows and 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 by providing PowerShell-based commands and examples (e.g., AzureCLI@2 with scriptType: 'pscore', PowerShell@2 tasks, and explicit PowerShell code blocks) without offering equivalent bash or Linux shell alternatives. Windows tools and patterns (such as AzPowershell, PowerShell tasks, and .NET/NUnit focus) are mentioned and used throughout, often without parallel Linux-native instructions. In several places, PowerShell is the only scripting language shown, and there are no bash or sh examples for Linux users, especially in CI/CD pipeline steps. This may hinder Linux users or those using non-Windows runners.
Recommendations
- Provide bash/sh equivalents for all PowerShell commands and scripts, especially in CI/CD pipeline examples.
- When showing Azure CLI or login steps, include both PowerShell and bash variants, or use cross-platform CLI commands where possible.
- Avoid using Windows-specific terminology (e.g., 'AzPowershell', 'PowerShell@2') as the default; instead, present both Windows and Linux options side by side.
- Explicitly mention compatibility with Linux runners and provide examples using Ubuntu or other Linux environments.
- For .NET/NUnit examples, clarify that they are cross-platform and, if possible, show how to run them on Linux (e.g., using dotnet CLI on Ubuntu).
- In code blocks and workflow YAML, use shell-agnostic syntax or provide both shell and PowerShell versions.
- Review all sections for implicit Windows-first assumptions and add Linux parity throughout.
App Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-testing/load-testing/tutorial-identify-bottlenecks-azure-portal.md
...-testing/tutorial-identify-bottlenecks-azure-portal.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While the Azure CLI is used (which is cross-platform), the instructions mention using PowerShell commands to deploy the sample application, and Visual Studio Code is recommended without noting Linux alternatives. There are no explicit Linux/macOS terminal examples or references to Bash, and the deployment steps do not clarify if the commands are compatible with Linux shells. The documentation also does not provide Linux-specific troubleshooting or environment validation steps.
Recommendations
- Provide explicit Bash/Linux shell command examples alongside PowerShell where applicable, or clarify that the Azure CLI commands are cross-platform and show syntax for both environments.
- When referencing Visual Studio Code, mention that it is available on Windows, Linux, and macOS, and provide links or notes for Linux installation.
- If PowerShell is required for deployment, provide equivalent Bash scripts or instructions for Linux/macOS users.
- Include notes or troubleshooting steps for common Linux/macOS issues (e.g., permissions, path differences) when using the Azure CLI or Git.
- Explicitly state that the tutorial is cross-platform, and ensure screenshots or UI references are not Windows-specific unless unavoidable.
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. It consistently references Visual Studio Code (a Microsoft product popular on Windows), the Azure Portal (web-based but often associated with Windows-centric workflows), and .NET/NUnit (commonly used in Windows environments). There are no explicit Linux or macOS-specific instructions, nor are there terminal commands or screenshots showing Linux shells or file paths. The CLI instructions are generic (e.g., 'npx', 'dotnet'), but there is no mention of Linux-specific setup, environment variables, or troubleshooting. The documentation does not provide parity for Linux users in terms of examples, tooling, or environment setup.
Recommendations
- Include explicit Linux/macOS instructions and screenshots where relevant, such as using Bash or Zsh shells, and showing file paths in Linux format.
- Add notes or examples for setting environment variables in Linux/macOS shells (e.g., 'export PLAYWRIGHT_SERVICE_URL=...') alongside the .env approach.
- Mention Linux package managers (e.g., apt, yum, brew) for installing prerequisites like Node.js, .NET, or Azure CLI.
- Provide parity in troubleshooting tips for Linux users (e.g., permissions, path issues).
- Balance references to Visual Studio Code with mentions of other editors or CLI-only workflows, or clarify that VS Code is cross-platform.
- Ensure screenshots and instructions do not assume a Windows environment by default.
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
Missing Linux Example
Windows First
Summary
The documentation page exhibits a Windows bias by using PowerShell syntax for all command-line examples (e.g., git, npm, npx), omitting Linux/macOS shell equivalents, and not clarifying cross-platform compatibility. There are no explicit Linux or macOS instructions or screenshots, and the command-line instructions assume a Windows environment. This may confuse or exclude users on Linux or macOS.
Recommendations
- Provide both Windows (PowerShell/cmd) and Linux/macOS (bash/zsh) command examples, or use a neutral shell syntax where possible.
- Explicitly state that the commands work on all platforms, or note any platform-specific differences.
- Use generic 'terminal' or 'shell' terminology instead of 'command window', and clarify that instructions apply to all major OSes.
- Include Linux/macOS-specific installation or troubleshooting notes where relevant.
- Add screenshots or notes for Linux/macOS environments, not just Windows/Azure Portal.
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 moderate Windows bias. Command-line examples are consistently shown using PowerShell syntax (e.g., 'cd' and command blocks labeled as 'powershell'), with no explicit Linux/macOS shell equivalents. The instructions and tooling (Azure CLI, npm, git) are cross-platform, but examples and terminology default to Windows conventions. There are no Linux/macOS-specific notes or alternative shell commands provided.
Recommendations
- Provide Linux/macOS shell examples alongside PowerShell commands, using appropriate syntax (e.g., 'cd' and 'ls' in bash/zsh).
- Label command blocks generically (e.g., 'shell') or provide tabs for Windows (PowerShell) and Linux/macOS (bash/zsh).
- Add notes clarifying that all tools (Azure CLI, npm, git) are cross-platform and provide installation links for Linux/macOS.
- Explicitly mention that the steps work on Linux/macOS and highlight any platform-specific differences, if any.
Medium 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 the deployment script is a PowerShell script (.ps1), with only a brief tip mentioning that PowerShell can be installed on Linux/macOS. There are no Bash or Linux-native instructions, and the workflow assumes familiarity with Windows tools and patterns.
Recommendations
- Provide equivalent Bash shell commands and instructions for Linux/macOS users, especially for git clone and directory navigation.
- Offer a cross-platform deployment script (e.g., a Bash script or Azure CLI commands) or document how to run the PowerShell script using pwsh on Linux/macOS more prominently.
- Mention Linux/macOS compatibility earlier in the instructions, not just as a tip.
- If the deployment script is Windows-specific, provide an alternative for Linux/macOS users.
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 is heavily focused on Azure DevOps Pipelines, which is most commonly used in Windows-centric environments. All examples, screenshots, and step-by-step instructions are tailored to Azure DevOps and the Azure portal, with no mention of Linux/macOS-specific tools, shell commands, or alternative CI/CD platforms except for a brief link to manual GitHub Actions configuration. There are no Linux/macOS command-line examples, nor is there any discussion of how to perform these steps outside the Azure portal or DevOps UI.
Recommendations
- Add explicit Linux/macOS command-line examples for configuring and running load tests, such as using Azure CLI or REST API.
- Provide parity examples for configuring CI/CD pipelines using popular Linux-friendly platforms (e.g., GitHub Actions, Jenkins, GitLab CI) directly in the quickstart, not just as a link.
- Include screenshots or instructions for performing tasks in non-Windows environments, such as using terminal commands.
- Clarify which steps are platform-agnostic and which are specific to Azure DevOps/Azure portal, and offer alternatives where possible.
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
Windows First
Summary
The documentation page provides detailed instructions for managing Azure RBAC roles via the Azure portal and PowerShell, but omits equivalent examples for Linux/macOS users (e.g., Azure CLI or Bash). All command-line examples use PowerShell cmdlets, which are native to Windows and less common on Linux/macOS. There is no mention or example of using Azure CLI, which is cross-platform and preferred by many non-Windows users. The ordering also places Windows-centric tools (portal, PowerShell) before any mention of alternatives.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands shown.
- Explicitly mention that Azure CLI is available and supported on Linux/macOS.
- Provide Bash shell examples for role assignment and management tasks.
- Reorder sections to present cross-platform tools (Azure CLI) before or alongside PowerShell.
- Clarify which tools are available on which platforms to help users choose appropriately.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively describes managing workspace access using the Azure portal, a graphical tool primarily available on Windows and macOS, but does not mention or provide examples for command-line alternatives such as Azure CLI, PowerShell, or REST API. There are no Linux-specific instructions or parity for users who prefer or require non-GUI, cross-platform workflows.
Recommendations
- Add instructions and examples for managing workspace access using Azure CLI, which is cross-platform and widely used on Linux.
- Include PowerShell examples, but ensure Azure CLI examples are presented first or alongside them to avoid Windows-first bias.
- Reference REST API documentation for advanced or automated access management, which is platform-agnostic.
- Explicitly state that all management tasks can be performed from Linux/macOS using CLI or API, not just the Azure portal.
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 exhibits several signs of Windows bias. Many examples and workflow steps use PowerShell scripts and Windows-centric tooling (e.g., AzPowershell, AzureCLI with 'pscore', PowerShell@2 tasks), often without providing equivalent bash or Linux shell alternatives. The use of PowerShell is prominent in both GitHub Actions and Azure Pipelines examples, and Windows-specific terminology (e.g., AzPowershell session) appears before or instead of Linux/macOS options. There are no explicit bash or Linux shell script examples, and the documentation does not clarify cross-platform compatibility for these steps.
Recommendations
- Provide equivalent bash or Linux shell script examples alongside PowerShell examples, especially for CI steps.
- Clarify when PowerShell usage is required and when bash/sh alternatives are supported, especially for AzureCLI and GitHub Actions steps.
- Explicitly state cross-platform compatibility for all CLI commands and scripts.
- Where possible, use platform-agnostic commands (e.g., 'npm ci', 'npx playwright test') and minimize reliance on Windows-specific tooling.
- Add notes or tabs for Linux/macOS users, showing how to adapt authentication and workflow steps without PowerShell.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes managing workspace access via the Azure portal GUI, which is most commonly used on Windows. There are no examples or references to command-line alternatives (such as Azure CLI or PowerShell), nor is there any mention of Linux/macOS workflows or tools. All screenshots and instructions assume a graphical interface, which may not be the primary method for Linux users.
Recommendations
- Add instructions and examples for managing workspace access using Azure CLI, which is cross-platform and widely used on Linux/macOS.
- Include PowerShell examples if relevant, but ensure Azure CLI is presented first or alongside PowerShell.
- Explicitly state that the Azure portal is accessible from any OS via a web browser, and mention any OS-specific considerations if applicable.
- Add a section comparing GUI and CLI workflows, highlighting parity and differences for Linux/macOS users.
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 roles using the Azure portal and Azure PowerShell cmdlets. There are no examples or guidance for using cross-platform tools such as Azure CLI, which is natively supported on Linux/macOS. The exclusive use of PowerShell and portal instructions creates friction for Linux/macOS users, who may not have access to PowerShell or prefer CLI workflows.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands shown, including role assignment, listing, and removal.
- Explicitly mention that Azure CLI is supported and provide links to relevant Azure CLI documentation.
- Consider presenting CLI examples before or alongside PowerShell examples to promote platform neutrality.
- Clarify that PowerShell is available cross-platform, but highlight CLI as the default for Linux/macOS users.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows and PowerShell usage. All command-line examples use PowerShell syntax, and instructions assume a Windows environment by default. Linux/macOS users are only briefly mentioned in a tip, which suggests installing PowerShell, but no native Bash or shell alternatives are provided for common tasks like cloning the repo or running deployment scripts.
Recommendations
- Provide equivalent Bash or shell commands for Linux/macOS users, especially for git operations and directory navigation.
- If the deployment script is PowerShell-only, offer a cross-platform alternative (e.g., a Bash script) or document how to run it with pwsh on Linux/macOS in the main instructions, not just a tip.
- List Linux/macOS instructions alongside Windows, not as an afterthought.
- Mention platform requirements and limitations up front, so users know if PowerShell is mandatory.
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 focuses exclusively on Azure Pipelines and Azure DevOps, which are traditionally more Windows-centric tools. All examples, screenshots, and step-by-step instructions are tailored to the Azure portal and Azure DevOps UI, with no mention of Linux/macOS-specific workflows, CLI alternatives, or cross-platform considerations. There are no examples using bash, shell scripts, or Linux-native CI/CD tools. The only nod to alternatives is a brief link to manual configuration for GitHub Actions, but no Linux-specific guidance is provided.
Recommendations
- Add explicit examples and instructions for configuring CI/CD pipelines on Linux/macOS environments, including CLI-based workflows.
- Include sample YAML pipeline definitions that work on Linux agents, and clarify any OS-specific requirements or differences.
- Provide parity by showing how to automate load tests using Linux-native CI/CD tools (e.g., Jenkins, GitLab CI) or at least mention their compatibility.
- Ensure screenshots and instructions are not exclusively based on Windows/Azure DevOps UI; consider including CLI or cross-platform alternatives.
- Expand the 'Next steps' section to include Linux/macOS troubleshooting and best practices.
App Testing
Configure customer-managed keys for encryption
...load-testing/how-to-configure-customer-managed-keys.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples and references to Windows-centric tools (PowerShell, Azure portal screenshots) are consistently presented before Azure CLI equivalents. The Azure portal UI is also Windows-oriented. While Azure CLI commands are provided for most tasks, there are no explicit Linux/macOS shell examples (e.g., Bash), and the PowerShell approach is often described in more detail. No Linux-specific tools or workflows are mentioned.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to prioritize cross-platform usage.
- Include explicit Bash shell examples for Linux/macOS users, especially for ARM template deployments and scripting.
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide notes or links for installing Azure CLI on non-Windows platforms.
- Add screenshots or instructions for Azure portal usage on macOS/Linux browsers, or clarify that the portal is web-based and OS-agnostic.
- Avoid assuming PowerShell is the default scripting environment; mention alternatives where appropriate.
App Testing
Quickstart: Run Playwright tests at scale
...aywright-workspaces/quickstart-run-end-to-end-tests.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits mild Windows bias through its use of Windows-centric tools (Visual Studio Code, PowerShell, .NET CLI), and by presenting Windows/Visual Studio Code workflows and screenshots before or instead of Linux alternatives. There are no explicit Linux/macOS terminal examples, nor are platform-specific setup instructions (e.g., environment variable configuration) shown for bash/zsh. The use of PowerShell for .NET package installation and the lack of Linux-specific guidance for environment setup and CLI usage may create friction for Linux/macOS users.
Recommendations
- Include explicit Linux/macOS terminal commands and examples (e.g., bash/zsh for environment variable setup, .NET CLI usage).
- Provide screenshots or instructions for Linux/macOS environments, not just Visual Studio Code on Windows.
- Add guidance for installing dependencies (like Azure CLI, Playwright) on Linux/macOS, including package manager commands.
- Mention cross-platform alternatives to PowerShell (e.g., bash) for .NET CLI commands.
- Clarify that Visual Studio Code is available cross-platform, and provide parity for other editors or terminal workflows.
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 exhibits several signs of Windows bias. Many examples and workflow steps use PowerShell scripts and Windows-centric tools (e.g., AzPowershell, AzureCLI with 'pscore'), and PowerShell is referenced in both GitHub Actions and Azure Pipelines examples. The use of PowerShell and Windows-specific terminology appears before or instead of Linux/macOS alternatives. There are no explicit bash or shell script examples, and the documentation does not clarify how Linux/macOS users should adapt commands or authentication steps. The only nod to cross-platform is the use of 'ubuntu-latest' runners, but the actual commands and authentication flows are Windows/PowerShell-centric.
Recommendations
- Provide equivalent bash/shell script examples for Linux/macOS users alongside PowerShell examples.
- Clarify which commands and authentication steps are cross-platform and which are Windows-specific.
- Use neutral, cross-platform CLI tools and commands where possible (e.g., Azure CLI instead of AzPowershell).
- Explicitly mention Linux/macOS compatibility and provide adaptation notes for non-Windows environments.
- Order examples so that cross-platform or Linux/macOS instructions are presented first or equally.
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 moderate Windows bias. Command-line examples are consistently shown using PowerShell syntax (e.g., 'cd', 'git clone', 'npm install') without explicit Linux/macOS shell equivalents. There is no mention of Linux/macOS-specific instructions for common tasks like installing Azure CLI, Git, or running Playwright commands. Windows tools and patterns (PowerShell, Visual Studio Code) are referenced first or exclusively, and screenshots are from the Azure Portal, which is cross-platform but visually Windows-centric. Linux/macOS users may need to infer or adapt commands and installation steps.
Recommendations
- Provide shell command examples using Bash syntax alongside PowerShell, or use a neutral format where possible.
- Explicitly mention Linux/macOS installation steps for Azure CLI, Git, and Visual Studio Code, with links to platform-specific guides.
- Clarify that all commands (git, npm, npx) work on Linux/macOS and provide any necessary adjustments (e.g., path separators, environment variable setting).
- Include screenshots or notes indicating that the Azure Portal is accessible from any OS.
- Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, environment variable setup).
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 focuses exclusively on Azure Pipelines and the Azure DevOps portal, with all examples and screenshots based on the web UI and Azure-specific workflows. There is no mention of Linux-specific tools, command-line interfaces, or alternative CI/CD systems (other than a brief link to GitHub Actions). No examples are provided for configuring pipelines using Linux-native tools or shell scripts, and the documentation assumes use of the Azure portal and Azure DevOps, which are more commonly used in Windows environments.
Recommendations
- Include examples for configuring CI/CD pipelines using Linux command-line tools (e.g., Azure CLI, Bash scripts) and show how to automate load tests without relying on the Azure portal UI.
- Provide parity by adding step-by-step instructions for setting up load tests in popular Linux-based CI/CD systems (e.g., Jenkins, GitLab CI) alongside Azure Pipelines.
- Add sample YAML pipeline definitions that can be used in cross-platform environments, highlighting any OS-specific considerations.
- Explicitly mention that the process works on both Windows and Linux agents, and clarify any differences in setup or execution.
- Include screenshots or terminal output from Linux environments to balance the visual representation.
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 primarily accessed via a web browser on Windows. There are no examples or instructions for command-line or automation approaches, such as using Azure CLI, PowerShell, or REST API, which are cross-platform and commonly used on Linux. The absence of Linux-specific or CLI-based instructions may disadvantage users who prefer or require non-Windows environments or automation.
Recommendations
- Add instructions and examples for managing workspace access using Azure CLI, which is available on Linux, macOS, and Windows.
- Include REST API examples for role assignment and revocation, enabling automation and cross-platform usage.
- If PowerShell examples are added, ensure Azure CLI equivalents are provided and presented with equal prominence.
- Explicitly mention that all management operations can be performed from Linux, macOS, and Windows using CLI or API tools.
- Add troubleshooting and prerequisite notes for CLI/API usage, such as authentication setup on Linux.