Introduction: For Software Development Engineers in Test (SDET), configuring custom browser profiles for test executions ensures a more tailored testing environment.
This guide simplifies how shows you step-by-step process to set up Qualitia Automation Studio (QAS) to run tests on custom browser profiles for Chrome, Edge, and Firefox.
📚Prerequisites:
Access to Qualitia Automation StudioQAS - Client.
Familiarity with the browser you 're are testing (Chrome, Edge, or Firefox).
A custom browser profile created on your computer.
...
Imagine you have specific browser extensions or settings on a custom profile that you want to test with. First, you need to fetch get the profile's path.
Chrome: Open Chrome, type chrome://version/ in the address bar, and copy the Profile Path value.
Edge: Open Edge, type Edge://version/ in the address bar, and copy the Profile Path value.
Firefox: Open Firefox, type about:profiles in the address bar, and copy the Profile Path value.
...
Now, you want to instruct QAS to use this custom browser profile for test executions.
Login to Qualitia Automation Studio QAS - Client. <insert Screenshot>
Access Execute from left navigation of your Qualitia Automation Studio QAS - Client to view Test Suite Explorer screen.
Go to the Execution Profile tab. <insert Screenshot>
Navigate Then, go to : Settings -> Local Profile -> Browse.
From the Browser Type drop-down dropdown, pick select the relevant browser.
Paste the copied Profile Path value into Browser Profile Path.
...
Note: The last part of the 'Profile Path' is the custom browser profile name
...
.
...
For example, if the path ends in \JohnS, then "JohnS" is the profile name
...
.
Under the respective options (EdgeOptions, ChromeOptions, or FirefoxOptions), in 'args', type:
--profile-directory=<profile_name>, replacing . Remember to replace <profile_name> with your custom profile's name.Adjust If necessary, edit any other necessary required settings of the execution profile.
Click Save.
| Note |
|---|
Execution Precaution: Before you run any test, to avoid conflicts or errors, you need to ensure no instances instance of the browser are is active. Make sure Also, ensure all instances of the chosen browser are closed before executing a test case or suite on the custom browser profile. |
...