Testexecute tests run on Chrome browser

[AlexKaras]

Hi,

> I do not see google update Under Policies ?

Have you downloaded and installed the template as described in the Google document referenced in the article?

As for the second option, the key must be created manually if the key is absent in the registry.

[nisgupta]

@AlexKaras 

Oh my mistake , I am now looking at this docs . Seem like I have to download template and then i can see the options.

Manage Chrome updates (Windows) - Google Chrome Enterprise Help

[nisgupta]

We have now started building Chrome tests. 

We already have firefox tests. For chrome tests we are just copying the scripts and Name mapping . We make changes in script where we are launching browser just replacing firefox with chrome .

Is it the right way to do this ? Do we need to create name mapping again for chrome browser ?

Please update 

Thanks

NG

[Marsha_R]

Here's some information about cross-browser testing.

https://support.smartbear.com/testcomplete/docs/app-testing/web/general/cross-browser/about.html

[AlexKaras]

Hi,

> we are just copying the scripts and Name mapping .

In general, copying is not required and only browser name should be provided as a parameter.

However, depending on your tested web application and test code, script adjustments might be required to match browser specific.

[nisgupta]

@Marsha_R 

@AlexKaras 

Thanks for the updates ,

We are getting error in chrome Tests 

This operation returned because timeout period has expired 

Any updates why we are getting ? Also attaching the screenshot.

[AlexKaras]

Hi,

Any more details?

What operation failed? Anything in the Details log pane? Can you post screenshot of the test? Why 'error' message was manually logged just before?

[nisgupta]

Attached the Detail Panel

javaScript runtime error. 

The Operation returned because the timeout period expired.

[Marsha_R]

The error messages are usually pretty targeted.  What ever that line is looking for didn't happen fast enough for the test to see it.  

You can test this by putting a Delay right before the line that failed.  If that seems to fix it, then take the Delay out and adjust the failed line with the appropriate Wait

https://support.smartbear.com/testcomplete/docs/app-objects/common-tasks/waiting-process-or-window-a...

[nisgupta]

@Marsha_R 

This is why I have updated as shown in the attached screenshot.

Thanks

NG