Ability to Include Browser Flags in Context Menu Test Runs

[Christopher-C-Robinson]

Feature Request: Ability to Include Browser Flags in Context Menu Test Runs

Description

I am writing to request a new feature for the 'TestCafe Test Runner' extension for Visual Studio Code. Currently, when right-clicking on a test file, I can choose to run it with a specified browser using the 'TestCafe: Run Test(s) in [Browser]' option. However, I am unable to include additional browser-specific flags, such as --ignore-certificate-errors, within this process. This feature would greatly enhance the flexibility and usability of the extension.

Motivation

In many testing scenarios, particularly when dealing with self-signed SSL certificates or other browser-specific configurations, it is crucial to run tests with specific browser flags. The ability to include these flags directly from the context menu would streamline the testing process and accommodate a wider range of testing environments.

Suggested Implementation

An ideal implementation could be an option in the extension settings where users can specify custom browser flags. These flags would then be automatically appended to the browser command whenever a test is run from the context menu. For example, if I add --ignore-certificate-errors as a custom flag in the extension settings, selecting 'TestCafe: Run Test(s) in Chrome' would run the test in Chrome with the --ignore-certificate-errors flag applied.

Use Case

For instance, I frequently encounter environments where SSL certificates are self-signed. The ability to right-click on a test file and run it with the --ignore-certificate-errors flag directly from the context menu would significantly enhance my workflow and reduce the need for manual command line adjustments.

Additional Context

This feature would be a valuable enhancement for the 'TestCafe Test Runner' extension, making it more adaptable and user-friendly for various testing requirements. It would particularly benefit those who need to quickly and frequently adjust their testing setup without resorting to manual command-line entries.

I hope you will consider adding this feature. It would undoubtedly be a significant improvement to the extension's functionality.

Thank you for your time and effort in maintaining this valuable tool.

Best regards,
Christopher Robinson