Record Web feature is broken when utilizing certain Configuration Parameters

Web Testing
,
1

Hello to whom it may concern,

I was hoping someone could help me with an issue I’m experiencing while utilizing the Record Web feature.

Per my employer’s instructions, we’ve been asked to apply multiple browser configuration parameters to avoid productivity loss caused by Alerts, Prompts and Pop-ups etc. during test automation, but also to help ensure the browsers are executing Tests in a consistent manner.

In summary, when utilizing the Configuration Parameters (as outlined below), the Record Web feature just straight up does not work. The Red border highlight indicator that appears on mouse-hover over page Elements does not display, nor does interaction with Elements cause them to get recorded as expected.

For context, attached I’ve provided the following:

JSON Beautified version:

{
  "CHROME_DRIVER": {
    "args": [
      "--disable-component-update",
      "--disable-dev-shm-usage",
      "--disable-features=ChromeManagement,EnterprisePolicy",
      "--disable-features=SafeBrowsing,PasswordLeakToggleMove",
      "--disable-infobars",
      "--disable-notifications",
      "--disable-popup-blocking",
      "--disable-save-password-bubble",
      "--disable-single-click-autofill",
      "--force-device-scale-factor=1",
      "--guest",
      "--incognito",
      "--lang=en-US",
      "--override-language-detection",
      "--password-store\\u003dbasic"
    ],
    "excludeSwitches": [
      "enable-automation",
      "load-extension"
    ],
    "prefs": {
      "credentials_enable_service": false,
      "profile.password_manager_enabled": false,
      "profile.password_manager_leak_detection": false,
      "autofill.profile_enabled": false
    }
  }
}

Any advice or knowledge on which Configuration Parameters might impact Record Web would be highly appreciated! Otherwise, I’ll have to resort to the time intensive task of eliminating variables and testing them individually.

Thank you in advance!

2 Likes
2

Hi there, and thanks for posting in the Katalon community! :hugs:

To help you faster, please review our guide on Record Web Utility here: Record Web utility in Katalon Studio | Katalon Docs. Double-checking the steps and configurations might resolve the issue.

If the doc doesn’t help, feel free to provide more details, and a community member will assist you soon.

Thanks for being a part of our community!
Best,
Elly Tran

1 Like
3

the following topic may concern:

Probably, the Configuration parameters are not the cause of your issue.

1 Like
4

i think this topic should be pinned so people can be aware of this issue

🚨 [Announcement] Chrome 142 Recording Issue

2 Likes
5

Hi @kazurayam ,

Interesting… as I have only observed an issue with Record Web feature when I have the configuration parameters applied. Otherwise, I can use Record Web just fine, both for distinct new test cases and when updating a test case that has prior steps executed from Call Test Case.

I’m even on version:

  • Chrome: 142.0.7444.135
  • Katalon Studio: 10.4.1-3016bf4f2c
1 Like
6

Thus far, through process of elimination, I’ve verified the issue is reproducing from one of the configuration parameters from “args”, these:
"args": [
"--disable-component-update",
"--disable-dev-shm-usage",
"--disable-features=ChromeManagement,EnterprisePolicy",
"--disable-features=SafeBrowsing,PasswordLeakToggleMove",
"--disable-infobars",
"--disable-notifications",
"--disable-popup-blocking",
"--disable-save-password-bubble",
"--disable-single-click-autofill",
"--force-device-scale-factor=1",
"--guest",
"--incognito",
"--lang=en-US",
"--override-language-detection",
"--password-store\\u003dbasic"
]

The issue does not reproduce when the excludeSwitches or prefs paramenters are included in the configuration.

I’ll investigate further when I can.

1 Like
7

Hello @Elly_Tran,

As suggested, I have reviewed the Record Web utility in Katalon Studio page and even ensured the Activate browser extensions are accurately installed (these) for each browser:
• Download and install Katalon Recorder on Chrome
• Download and install Katalon Recorder on Firefox
• Download and install Katalon Recorder on Edge Chromium

For context, this issue was initially experienced following these Katalon Courses: hands-on-guide-to-kickstart-test-automation > Exploring the skillset development roadmap for beginners, however, Record Web is working fine, both before and after, the removal of the configuration parameters I’ve outlined above; either during a distinct New Test Case recording, or via an existing Test Case utilizing the Call Test Case feature to preface Steps before starting a recording. (i.e. the issues only present itself when utilizing the configuration parameters.)

Therein, I assume its due to a specific configuration parameter my employer has instructed us to utilize, but I’m trying to figure out which one specifically so I can collaborate with my manager to update our required configuration parameters accordingly.

Please let me know if you need further details.

8

Dear Depapp,

I have pinned it under Announcement for more visibility

Thank you

2 Likes
9

FYI everyone,

As of today (20251112), with these versions

  • Katalon Version: 10.4.1-3016bf4f2c
  • Google Version: 142.0.7444.163

I think I’ve figured out which Chrome Driver arguments are causing this issue, it’s both guest and incognito. If the Configuration has 1 &/or the other, or both, the issue is manifesting.

"args": [
      "--guest",
      "--incognito"
    ]

However, with the following configuration parameters, Record Web is working just fine, both for distinct new test cases and when updating a test case that has prior steps executed from Call Test Case. See below:

JSON Beautified version:

{
  "CHROME_DRIVER": {
    "args": [
      "--disable-component-update",
      "--disable-dev-shm-usage",
      "--disable-features=ChromeManagement,EnterprisePolicy",
      "--disable-features=SafeBrowsing,PasswordLeakToggleMove",
      "--disable-infobars",
      "--disable-notifications",
      "--disable-popup-blocking",
      "--disable-save-password-bubble",
      "--disable-single-click-autofill",
      "--force-device-scale-factor=1",
      "--lang=en-US",
      "--override-language-detection",
      "--password-store\\\\u003dbasic",
      "--start-maximized"
    ],
    "excludeSwitches": [
      "enable-automation",
      "load-extension"
    ],
    "prefs": {
      "credentials_enable_service": false,
      "profile.password_manager_enabled": false,
      "profile.password_manager_leak_detection": false,
      "autofill.profile_enabled": false
    }
  }
}

Please let me know if you’ve got any questions or encounter something different. I hope this helps!

Respectfully,
Chris

2 Likes
10

Record Web breaks because of these parameters:

  • excludeSwitches: ["enable-automation"]

  • excludeSwitches: ["load-extension"]

  • --incognito

  • --guest

11

Hi @m.aldaajeh ,

Interesting… I did not experience any issues while utilizing the excludeSwitches, as I mentioned here:
"excludeSwitches": [
"enable-automation",
"load-extension"
]

When I was verifying the behavior though, I was explicitly isolating each section individually (args, excludeSwitches, prefs) followed by each parameter individually as well.

What did you do differently to encounter an issue with the excludeSwitches parameters?

Just curious, thank you!

1 Like