Playwright Testing
26
Total Pages
16
Linux-Friendly Pages
10
Pages with Bias
38.5%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
45 issues found
Showing 26-45 of 45 flagged pages
Playwright Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/playwright-testing/tutorial-run-end-to-end-tests.md
...es/playwright-testing/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 providing all command-line examples using PowerShell syntax (e.g., 'cd' instead of 'cd' or 'ls' instead of 'ls'), and does not offer Linux/macOS-specific instructions or examples. There is no mention of Linux or macOS terminals, shells, or platform-specific considerations, and all setup and usage steps assume a Windows environment. Visual Studio Code and Git are referenced generically, but installation links point to cross-platform sources. The Azure CLI is cross-platform, but no explicit Linux/macOS guidance is provided. The absence of Linux/macOS terminal commands or notes may hinder parity for non-Windows users.
Recommendations
- Provide both Windows (PowerShell or Command Prompt) and Linux/macOS (bash/zsh) command examples side by side, especially for commands like 'cd', 'npm install', and 'npx playwright test'.
- Explicitly mention that the Azure CLI, Visual Studio Code, and Git are cross-platform, and provide links or notes for Linux/macOS installation guides.
- Add a section or callout for Linux/macOS users, highlighting any platform-specific steps or differences (such as environment variable syntax, file paths, or shell commands).
- Use generic shell prompts (e.g., '$' for bash, '>' for PowerShell) to clarify which environment each example targets.
- Ensure that screenshots and UI references are not Windows-specific, or provide alternatives for other platforms if relevant.
Create Pull Request
Playwright Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/playwright-testing/troubleshoot-unable-sign-into-playwright-portal.md
...ing/troubleshoot-unable-sign-into-playwright-portal.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively provides troubleshooting steps using Windows PowerShell and the MSOnline module, with no mention of Linux or cross-platform alternatives. All instructions assume a Windows environment, and there are no examples or guidance for users on Linux or macOS.
Recommendations
- Include equivalent instructions using Azure CLI or Microsoft Graph API, which are cross-platform and can be run on Linux, macOS, and Windows.
- Add examples for enabling the service principal using bash or shell commands where possible.
- Mention that the MSOnline module and PowerShell steps are Windows-specific, and provide links or references for Linux/macOS users.
- Consider reordering or presenting cross-platform solutions first, or at least in parallel with Windows-specific instructions.
Playwright Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/playwright-testing/quickstart-run-end-to-end-tests.md
.../playwright-testing/quickstart-run-end-to-end-tests.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits subtle Windows bias by primarily referencing tools and workflows that are most common or exclusive to Windows environments, such as Visual Studio Code, PowerShell, and .NET/NUnit. There is a lack of explicit Linux/macOS terminal examples, and the documentation assumes the use of Visual Studio Code and .NET tooling, which are more prevalent in Windows-centric development. No Linux-specific shell or environment setup examples are provided, and the order of presentation often places Windows/VS Code workflows before more platform-neutral CLI approaches.
Recommendations
- Add explicit Linux/macOS shell examples for environment variable setup, such as export PLAYWRIGHT_SERVICE_URL=... in bash/zsh.
- Include alternative editors or CLI-only workflows, not just Visual Studio Code, to ensure parity for users on Linux or macOS.
- When referencing .NET/NUnit, clarify cross-platform support and provide equivalent instructions for running on Linux/macOS (e.g., using dotnet CLI in bash).
- Avoid assuming the use of PowerShell or Windows-specific tools; provide both PowerShell and bash/zsh command examples where relevant.
- Ensure that any screenshots or UI references (such as file explorers or dialogs) are not exclusively from Windows environments.
- Consider reordering sections so that platform-neutral or Linux/macOS examples are presented alongside or before Windows-specific workflows.
Playwright Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/playwright-testing/how-to-use-service-features.md
...cles/playwright-testing/how-to-use-service-features.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing configuration examples for Playwright using .NET/NUnit (.runsettings XML), which is primarily used in Windows environments, and by omitting explicit Linux or cross-platform CLI examples. The use of .runsettings and references to NUnit are strongly associated with Windows development workflows. There are no Bash, shell, or Linux-native configuration examples, nor any mention of Linux-specific tools or patterns.
Recommendations
- Add equivalent Linux and macOS examples, such as configuring Playwright using environment variables or JSON/YAML files commonly used in Unix-like systems.
- Include CLI-based instructions (e.g., using Bash scripts or shell commands) for managing features, in addition to the .runsettings and TypeScript examples.
- Explicitly mention that the features and configurations apply to all platforms, and provide parity in documentation for Linux, macOS, and Windows.
- If possible, provide a table or section comparing configuration methods across platforms (Windows, Linux, macOS) to clarify cross-platform support.
- Avoid assuming the use of Windows-specific test runners (like NUnit) as the default; instead, balance with examples for popular Linux/macOS runners (e.g., Mocha, Jest, or native Playwright CLI usage).
Playwright Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/playwright-testing/quickstart-generate-rich-reports-for-tests.md
...-testing/quickstart-generate-rich-reports-for-tests.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows environments and tooling. The .NET/NUnit examples use PowerShell and Windows-centric patterns (e.g., .runsettings, PowerShell commands), and there is no mention of Linux or cross-platform equivalents for .NET users. The Playwright JavaScript/TypeScript examples are more cross-platform, but the .NET section assumes a Windows environment and does not provide Linux-specific guidance or examples. Additionally, Azure CLI is referenced, which is cross-platform, but the authentication and setup instructions do not clarify Linux usage or shell differences. The documentation does not provide parity for Linux users running .NET/NUnit tests, and Windows tools and patterns are presented by default.
Recommendations
- For .NET/NUnit sections, provide explicit Linux/macOS instructions, including shell commands (e.g., bash equivalents for dotnet commands) and guidance on using .runsettings and PlaywrightServiceSetup.cs on non-Windows systems.
- Clarify that the .NET/NUnit instructions work on Linux and macOS, and provide any necessary prerequisites or differences (such as file paths, environment variable syntax, or package installation steps).
- When referencing PowerShell commands, also provide bash/zsh equivalents for cross-platform users.
- Explicitly state the cross-platform compatibility of the Azure CLI and show example commands in both Windows (PowerShell/cmd) and Linux/macOS (bash).
- Add a section or notes for Linux users running Playwright .NET tests, including troubleshooting tips or links to relevant documentation.
- Ensure that screenshots and file path examples are not Windows-specific, or provide Linux/macOS alternatives where relevant.
Playwright Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/playwright-testing/quickstart-automate-end-to-end-testing.md
...ight-testing/quickstart-automate-end-to-end-testing.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation exhibits a moderate Windows bias, particularly through the use of PowerShell commands and Azure PowerShell modules in setup instructions, as well as the use of PowerShell-based tasks in CI/CD pipeline examples. Windows-centric tools and patterns (such as AzPowershell, PowerShell@2, and scriptType: 'pscore') are referenced or used by default, even though the workflows are run on Ubuntu runners. There is little to no mention of Linux-native equivalents or alternative shell commands, and Windows/PowerShell tools are often mentioned first or exclusively.
Recommendations
- Provide equivalent Linux shell (bash/sh) commands alongside PowerShell commands for setup and package installation steps.
- When showing CI/CD pipeline tasks, include both PowerShell and bash script examples, or use cross-platform shell commands where possible.
- Avoid using Windows-specific terminology (e.g., 'AzPowershell', 'PowerShell@2') as the default; clarify when these are required and offer alternatives.
- Explicitly state that the examples are cross-platform, and test/validate all steps on both Windows and Linux runners.
- For .NET/NUnit examples, show how to install packages and run commands using bash or Linux-native tools, not just PowerShell.
- When referencing Azure CLI or authentication setup, provide both PowerShell and bash/CLI command options.
Playwright Testing
Quickstart: Continuous end-to-end testing
...ight-testing/quickstart-automate-end-to-end-testing.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a moderate Windows bias, primarily through the use of PowerShell-based examples and Windows-centric tools (e.g., AzPowershell, AzureCLI with 'pscore', PowerShell@2 tasks). These tools and patterns are referenced in both GitHub Actions and Azure Pipelines workflows, often as the default or only example for installing dependencies and running tests. While the workflows specify 'ubuntu-latest' runners and use cross-platform commands like 'npm ci' and 'npx playwright test', the authentication and setup steps rely heavily on PowerShell modules and conventions, which may be less familiar or accessible to Linux/macOS users. Additionally, command-line examples for running single tests are shown in PowerShell syntax, and there is little mention of Linux-native alternatives or shell scripting.
Recommendations
- Provide equivalent Bash/sh examples for all PowerShell commands, especially for authentication and setup steps.
- Clarify that AzureCLI and PowerShell tasks can be run on Linux/macOS runners and provide explicit instructions for those environments.
- Offer alternative workflow steps using Bash or native Linux/macOS tools where possible.
- Ensure that command-line examples (e.g., running single tests) are shown in both PowerShell and Bash syntax.
- Explicitly mention cross-platform compatibility for all tools and scripts, and highlight any platform-specific requirements.
Playwright Testing
Quickstart: Generate rich reports for Playwright tests
...-testing/quickstart-generate-rich-reports-for-tests.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. The NUnit example uses PowerShell and .NET tooling, which are most commonly associated with Windows environments. The use of .runsettings and .cs files, as well as references to PowerShell commands, may create friction for Linux/macOS users. The Playwright Test Runner example is cross-platform (Node.js), but the .NET/NUnit path is Windows-centric and does not mention Linux/macOS equivalents or alternatives. Additionally, Windows/PowerShell commands are shown before any Linux shell alternatives, and there is no explicit guidance for Linux/macOS users in the .NET/NUnit sections.
Recommendations
- Add explicit instructions for running .NET/NUnit tests on Linux/macOS, including installation steps for .NET SDK on those platforms.
- Provide bash/zsh command equivalents alongside PowerShell examples.
- Clarify that .NET Core and NUnit can be used cross-platform and provide sample commands for Linux/macOS environments.
- Mention any platform-specific caveats or requirements for Linux/macOS users in the NUnit sections.
- Ensure parity in troubleshooting and artifact collection instructions for Linux/macOS users.
Playwright Testing
Tutorial: Run end-to-end tests with Playwright Testing
...es/playwright-testing/tutorial-run-end-to-end-tests.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation consistently uses PowerShell syntax (e.g., command prompts with 'powershell' code blocks) for all terminal commands, and does not provide explicit Linux/macOS shell examples or mention platform-specific differences. This could create confusion or friction for Linux/macOS users, especially beginners, as some commands or conventions (such as environment variable setting or path separators) may differ. The documentation also implicitly assumes a Windows-first environment by not clarifying cross-platform compatibility.
Recommendations
- Provide both Windows (PowerShell or CMD) and Linux/macOS (bash/sh) command examples for all terminal commands, especially for navigation (cd), environment variable setup, and npm scripts.
- Use generic 'shell' or 'bash' code blocks where commands are cross-platform, and clarify any platform-specific differences.
- Explicitly mention that the instructions are cross-platform, and note any steps that differ between Windows and Linux/macOS.
- For environment variable configuration, show both Windows (set/PowerShell) and Linux/macOS (export) syntax.
- Consider alternating the order of examples, or grouping them together, rather than always showing Windows first.
Playwright Testing
Quickstart: Continuous end-to-end testing
...ight-testing/quickstart-automate-end-to-end-testing.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation demonstrates a notable Windows bias, especially in CI workflow examples for both GitHub Actions and Azure Pipelines. PowerShell-based tasks and Windows-centric tools (AzPowershell, AzureCLI with 'pscore', dotnet CLI) are used exclusively or shown first, even when the runner is 'ubuntu-latest'. There is no mention of Linux-native equivalents (e.g., bash, sh), nor are there alternative shell examples for Linux/macOS users. The authentication and setup steps also reference Azure PowerShell and CLI commands without Linux-specific alternatives.
Recommendations
- Provide Linux/macOS shell equivalents (bash/sh) for all PowerShell and Windows tool examples.
- Include explicit instructions or examples for running setup and authentication steps on Linux/macOS environments.
- When showing CI workflow YAML, offer both PowerShell and bash script variants, or clarify cross-platform compatibility.
- Avoid defaulting to Windows tools (AzPowershell, PowerShell@2) in examples; use platform-agnostic commands where possible.
- Clearly state which steps are OS-agnostic and which require adaptation for non-Windows environments.
Playwright Testing
Quickstart: Generate rich reports for Playwright tests
...-testing/quickstart-generate-rich-reports-for-tests.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation exhibits a moderate Windows bias, especially in the NUnit test runner sections. Package installation for NUnit is shown only with PowerShell/dotnet CLI commands, which are most familiar to Windows users. There is no mention of Linux/macOS equivalents (e.g., bash, zsh, or Mono for .NET), and Windows-centric tools (dotnet CLI, PowerShell) are referenced without alternatives. The Playwright test runner section is more cross-platform, using npm and shell commands, but the overall ordering and examples prioritize Windows tools and workflows.
Recommendations
- Provide Linux/macOS equivalents for all CLI commands, especially for .NET/NUnit sections (e.g., show bash/zsh syntax for package installation).
- Explicitly state that dotnet CLI is cross-platform and works on Linux/macOS, and provide installation links for those platforms.
- Include notes or examples for Mono usage on macOS/Linux if relevant for NUnit.
- Where PowerShell is used, offer bash/zsh alternatives or clarify that commands work in any shell.
- Balance example ordering so that Linux/macOS instructions are presented alongside or before Windows-specific ones.
Playwright Testing
Tutorial: Run end-to-end tests with Playwright Testing
...es/playwright-testing/tutorial-run-end-to-end-tests.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation consistently uses PowerShell syntax (e.g., for git, npm, and npx commands) in all code blocks, and refers to 'terminal or command window' without clarifying cross-platform differences. No Linux/macOS-specific instructions or examples are provided, and Windows-centric patterns (PowerShell prompt, command style) are used by default. This may cause confusion or friction for Linux/macOS users, especially beginners.
Recommendations
- Provide command examples using generic shell syntax (e.g., bash) or include both Windows (PowerShell/CMD) and Linux/macOS (bash/zsh) variants for all commands.
- Avoid using PowerShell-specific formatting (e.g., ```powershell) for commands that are cross-platform; use ```bash or ```sh for generic shell commands.
- Explicitly mention that all commands work on Linux/macOS unless otherwise noted, and clarify any OS-specific steps.
- If any step is OS-specific (such as environment variable syntax), provide both Windows and Linux/macOS instructions.
- Use inclusive language such as 'terminal' or 'shell' instead of 'command window', and clarify that Visual Studio Code, Git, and Azure CLI are available on all major platforms.
Playwright Testing
Manage workspace access
...s/playwright-testing/how-to-manage-workspace-access.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes managing workspace access through the Azure portal web interface, which is platform-agnostic but implicitly Windows-centric due to Azure's historical association and lack of mention of Linux-native tools or CLI workflows. There are no examples or references to Linux command-line tools (e.g., Azure CLI, Bash), nor are PowerShell or Windows-specific tools mentioned directly. However, the absence of Linux/CLI examples and the focus on GUI workflows may disadvantage Linux users or those preferring automation.
Recommendations
- Add equivalent instructions for managing workspace access using the Azure CLI, including example commands for role assignment and revocation.
- Explicitly mention that the Azure portal is accessible from any OS/browser, but provide parity for users who prefer command-line or automated workflows.
- Include links to documentation for Azure CLI and Bash scripting for role management.
- If PowerShell examples are added in the future, ensure Linux/Bash/CLI equivalents are provided alongside.
Playwright Testing
Manage workspace access
...s/playwright-testing/how-to-manage-workspace-access.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes managing access to Microsoft Playwright Testing workspaces via the Azure portal, which is a web-based GUI. There are no command-line examples provided, and no mention of cross-platform CLI tools such as Azure CLI or Azure PowerShell. The instructions implicitly assume users are accessing the Azure portal from a Windows environment, as there is no discussion of Linux or macOS workflows, nor are there examples for managing access via CLI on those platforms.
Recommendations
- Add Azure CLI examples for all role assignment and revocation steps, showing commands that work identically on Windows, Linux, and macOS.
- Explicitly mention that Azure portal is web-based and can be accessed from any OS, but provide parity by including CLI instructions for users who prefer or require command-line access.
- Include references to Azure PowerShell and Azure CLI documentation, and clarify which tools are cross-platform.
- Add troubleshooting steps or notes relevant to Linux/macOS users, such as browser compatibility or CLI installation instructions.
Playwright Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/playwright-testing/how-to-manage-workspace-access.md
...s/playwright-testing/how-to-manage-workspace-access.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes managing workspace access through the Azure portal UI, which is platform-agnostic but implicitly assumes a graphical environment. There are no command-line examples (such as Azure CLI or PowerShell), but when such examples are omitted, it can disadvantage Linux users who often prefer or require CLI-based workflows. The documentation does not mention or provide parity for Linux-native tools or workflows, nor does it reference cross-platform command-line methods for managing Azure RBAC, such as the Azure CLI, which is widely used on Linux.
Recommendations
- Add examples for managing workspace access using the Azure CLI, which is cross-platform and commonly used on Linux.
- Explicitly mention that all portal-based instructions work on any OS with a supported browser, but provide alternative CLI instructions for users who prefer or require non-GUI workflows.
- Include links to Azure CLI documentation for role assignments and access management.
- If PowerShell examples are added in the future, ensure equivalent Azure CLI examples are provided and presented with equal prominence.
Playwright Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/playwright-testing/playwright-testing-reporting-with-sharding.md
...-testing/playwright-testing-reporting-with-sharding.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Summary
The documentation page shows a moderate Windows bias by referencing Azure PowerShell (AzPowershell) for authentication in the GitHub Actions workflow, without mentioning or providing alternatives for Linux-native tools (such as Azure CLI). The only authentication example uses PowerShell, which is more commonly associated with Windows environments, even though the runner is set to 'ubuntu-latest'. No explicit Linux shell or cross-platform authentication alternatives are shown.
Recommendations
- Provide an example using Azure CLI (az login) for authentication, which is cross-platform and commonly used in Linux environments.
- Mention that both AzPowershell and Azure CLI can be used, and link to documentation for both.
- If showing a PowerShell-based example, also show a Bash/shell-based equivalent for parity.
- Clarify that the authentication method is not limited to Windows or PowerShell, and recommend the most cross-platform approach by default.
Playwright Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/playwright-testing/playwright-testing-reporting-with-sharding.md
...-testing/playwright-testing-reporting-with-sharding.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by including an Azure login step that specifically enables AzPSSession (PowerShell session) in the GitHub Actions workflow example. This references a Windows-centric authentication method and PowerShell tooling, without mentioning or providing alternatives for Linux-native authentication or CLI-based approaches. However, the rest of the examples (e.g., GitHub Actions, Ubuntu runners, shell commands) are cross-platform and do not show a strong Windows-first or exclusive pattern.
Recommendations
- Provide an alternative example for Azure authentication using the Azure CLI (az login) or a service principal, which is platform-agnostic and works natively on Linux/macOS runners.
- Clarify that enabling AzPSSession is optional and primarily needed for workflows that require PowerShell-specific Azure modules, and suggest when to use CLI vs. PowerShell.
- Explicitly mention that the workflow example runs on Ubuntu and is cross-platform, and provide notes or links for users running on Windows or macOS if there are differences.
- Audit future documentation for implicit assumptions that PowerShell or Windows tools are the default, especially in cross-platform CI/CD contexts.
Playwright Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/playwright-testing/how-to-configure-visual-comparisons.md
...ywright-testing/how-to-configure-visual-comparisons.md
Medium Priority
View Details →
Detected Bias Types
Linux First
Missing Windows Example
Summary
The documentation demonstrates a bias toward Linux by exclusively referencing Linux in all configuration examples and snapshot path templates. There are no examples or guidance for Windows users, nor is there mention of how to configure or handle visual comparisons if the service or local environment is Windows-based.
Recommendations
- Provide equivalent configuration examples for Windows environments, including snapshotPathTemplate values with 'windows' or 'win32' as the OS identifier.
- Explicitly mention how to handle visual comparisons when the service or local machine is running Windows, including any differences in path conventions or case sensitivity.
- Add a section or note clarifying how to adapt the configuration for macOS, if relevant, to ensure full cross-platform parity.
- Ensure that both Linux and Windows (and optionally macOS) are referenced equally in documentation, with examples for each where OS-specific configuration is required.
Playwright Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/playwright-testing/how-to-manage-workspace-access.md
...s/playwright-testing/how-to-manage-workspace-access.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes managing workspace access through the Azure portal UI, with no mention of command-line alternatives such as Azure CLI or Azure PowerShell. While the UI is cross-platform, the lack of CLI examples (which are especially valued by Linux users) and the absence of any Linux-specific guidance or parity checks means the documentation implicitly favors Windows/GUI workflows. There are no references to Linux tools, shell commands, or automation patterns that are common in Linux environments.
Recommendations
- Add equivalent Azure CLI examples for all role assignment and management tasks, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention that the Azure portal is accessible from any OS, but provide links or examples for users who prefer command-line or automation approaches.
- Include PowerShell examples only alongside Azure CLI and Bash equivalents, not as the sole automation method.
- Where screenshots are used, clarify that the UI is the same across platforms, or provide CLI alternatives for headless/server environments.
- Consider a section or callout for Linux users, highlighting best practices or common workflows for managing Azure RBAC from Linux systems.
Playwright Testing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/playwright-testing/how-to-use-service-config-file.md
...s/playwright-testing/how-to-use-service-config-file.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally presents both Windows and Linux options for the 'os' setting and provides examples for both. However, in the TypeScript example for the Playwright test runner, the 'os' option is set to 'ServiceOS.WINDOWS' in the code sample, even though the default is 'ServiceOS.LINUX'. This subtle ordering and example choice may suggest a preference for Windows. No exclusive use of Windows tools, PowerShell, or missing Linux examples were found.
Recommendations
- In code examples, use the default value ('ServiceOS.LINUX') for the 'os' setting or provide parallel examples for both Windows and Linux.
- When listing options, consider listing Linux first if it is the default, or explicitly state that both are equally supported.
- Ensure that any example or sample configuration does not implicitly prioritize Windows unless there is a technical reason to do so.
- If possible, add a note clarifying that both Windows and Linux are fully supported and that the choice in the example is arbitrary.