TestCafe Salesforce Automation - hammerhead Error "This page has an error. You might need to refresh it"

[ArunjaiAcc]

What is your Test Scenario?

Via automation tried to navigate to create firm/ create contact layout

What is the Current behavior?

Error on opening the page via test cafe

[Cannot read property 'hammerhead|event|internal-blur' of null] _ cancelInternalEvents()@http://192.168.0.9:52557/hammerhead.js:13:27910 {anonymous}()@http://192.168.0.9:52557/hammerhead.js:12:6 HTMLElement.dispatchEvent()@http://192.168.0.9:52557/hammerhead.js:13:27061 me.handleBlur()@https://preqin--uat.lightning.force.com/components/lightning/input.js:1:35128

What is the Expected behavior?

The page should load successfully and the user able to add the details

What is your web application and your TestCafe test code?

https://preqin--uat.lightning.force.com/

Debug Logs: [Cannot read property 'hammerhead|event|internal-blur' of null] _ cancelInternalEvents()@http://192.168.0.9:52557/hammerhead.js:13:27910 {anonymous}()@http://192.168.0.9:52557/hammerhead.js:12:6 HTMLElement.dispatchEvent()@http://192.168.0.9:52557/hammerhead.js:13:27061 me.handleBlur()@https://preqin--uat.lightning.force.com/components/lightning/input.js:1:35128

import { Selector } from 'testcafe';

fixture New Fixture .page Env Url;

test('New Test', async (t: TestController) => { await t .click('#username') .typeText('#username', '*') .click('#password') .typeText('#password', '') .click('#Login') .click(Selector('button').withText('Show Navigation Menu')) .click(Selector('#navMenuList span').withText('Firms').nth(1)) .click(Selector('#brandBand_1 div').withText('New').nth(7)) .click(Selector('#brandBand_2 span').withText('Next')) .wait(8000); });

Screenshots:

Steps to Reproduce:

1. Go to my website ...
2. Navigate to FIrm/Contact page
3. Click on new
4. See the error (Viewed only via automation)

Your Environment details:

• testcafe version: <1.15.2>
• node.js version: <v12.18.2>
• command-line arguments:
• browser name and version: <Version 92.0.4515.131>
• platform and version: < Windows>
• other:

[Farfurix]

@ArunjaiAcc

Hello,

We would love to assist you and diagnose this issue. However, since your website requires authentication, I will not be able to access it. Our policy prevents us from accessing a customer’s internal resources without prior written approval from the entity that owns the server/web resource. If you want us to research the problem further, we’ll need access to the server/web resource and your account using your credentials. Please send us ([email protected]) written confirmation. It must permit DevExpress personnel to remotely access your website account and its internal resources for research/testing/and debugging purposes.

Could you please send the complete test code with credentials and the written confirmation to our mailbox: [email protected]?

[ArunjaiAcc]

Sure, I will share the same @Farfurix

[aleks-pro]

@ArunjaiAcc , please leave a comment here after you send the confirmation to [email protected].

[ArunjaiAcc]

I have shared the detail with [email protected]. Please check into this @aleks-pro

[Farfurix]

@ArunjaiAcc

Hello, We couldn't find your Email. Would you please re-send it? How do we identify it?

[Farfurix]

@ArunjaiAcc

Hello,

We didn't manage to find your Email. Please re-send it.

[ArunjaiAcc]

Hello @Farfurix I re-sended it

[ArunjaiAcc]

import { Selector } from 'testcafe';

fixture New Fixture .page Env Url;

test('New Test', async (t: TestController) => { await t .click('#username') .typeText('#username', '*') .click('#password') .typeText('#password', '') .click('#Login') .click(Selector('button').withText('Show Navigation Menu')) .click(Selector('#navMenuList span').withText('Firms').nth(1)) .click(Selector('#brandBand_1 div').withText('New').nth(7)) .click(Selector('#brandBand_2 span').withText('Next')) .wait(8000); });

[Farfurix]

@ArunjaiAcc

Hello,

I reproduced this issue by clicking the following drop-down menu: We will update this thread once we have any news.

As a workaround, you can use another way to reach the "New Firms" page, without clicking a drop-down menu:

1. Click the "Firms" tab
2. Click the "New" button

[ArunjaiAcc]

Thanks, I'll check it out.

On Wed, Sep 1, 2021 at 2:02 PM Vladimir Airikh @.***> wrote:

@ArunjaiAcc https://github.com/ArunjaiAcc

Hello,

I reproduced this issue by clicking the following drop-down menu: [image: Capture] https://user-images.githubusercontent.com/30019338/131634838-92009ef6-5727-410f-ad2b-7b48985de82e.PNG We will update this thread once we have any news.

As a workaround, you can use another way to reach the "New Firms" page, without clicking a drop-down menu:

1. Click the "Firms" tab
2. Click the "New" button

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/DevExpress/testcafe/issues/6459#issuecomment-910063736, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKXAVPF7MVOUXQL5QOX5HELT7XQJFANCNFSM5CAUZ6FQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[aozomaro]

Hi that work around doesn’t work. I have the same issue only I browse directly to the page and it still fails. This has been broken since June, is there a plan to resolve this issue?

[Aleksey28]

Hi @aozomaro,

Please share your example for further research. There must be another issue.

[Artem-Babich]

Hello @ArunjaiAcc, 

I've just tried to reproduce this issue with [email protected]. However, the testing URL you shared is no longer available.  Could you try running your test with [email protected] with the experimental-proxyless option enabled? This option enables native browser automation. In Proxyless mode, a few issues are already fixed. This issue might also be fixed in Proxyless mode. This option is available in all interfaces:

// Command-line
testcafe chrome tests --experimental-proxyless   

// Programmatic
const testcafe = await createTestCafe({ experimentalProxyless: true });

// Configuration file
{
"experimentalProxyless": "true"
} 

Please keep in mind that this mode is experimental. Also, the Proxyless mode is implemented only in Google Chrome. It will not work correctly if you run tests in a non-Chrome browser or in a combination of other browsers.

[ArunjaiAcc]

Hi, Sure, I will check and let you know.

Regards, Arunkumar

On Mon, Feb 6, 2023 at 7:36 PM Artem-Babich @.***> wrote:

Hello @ArunjaiAcc https://github.com/ArunjaiAcc,

I've just tried to reproduce this issue with @.*** However, the testing URL you shared is no longer available. Could you try running your test with @.*** with the experimental-proxyless option https://testcafe.io/documentation/404237/guides/experimental-capabilities/proxyless-mode enabled? This option enables native browser automation. In Proxyless mode, a few issues are already fixed. This issue might also be fixed in Proxyless mode. This option is available in all interfaces:

// Command-line testcafe chrome tests --experimental-proxyless

// Programmatic const testcafe = await createTestCafe({ experimentalProxyless: true });

// Configuration file { "experimentalProxyless": "true" }

Please keep in mind that this mode is experimental. Also, the Proxyless mode is implemented only in Google Chrome. It will not work correctly if you run tests in a non-Chrome browser or in a combination of other browsers.

— Reply to this email directly, view it on GitHub https://github.com/DevExpress/testcafe/issues/6459#issuecomment-1419135816, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKXAVPA4MZPPV3BWHAYSSFDWWEAOXANCNFSM5CAUZ6FQ . You are receiving this because you were mentioned.Message ID: @.***>

[github-actions[bot]]

This issue was automatically closed because there was no response to our request for more information from the original author. Currently, we don't have enough information to take action. Please reach out to us if you find the necessary information and are able to share it. We are also eager to know if you resolved the issue on your own and can share your findings with everyone.