Behavior difference when using Chrome vs Chrome for Testing

[Emmanuel Pelletier]

Hey everyone,

I have weird behaviors in my test suite.

I noticed that if I use an actual google chrome binary and not a chrome for testing binary, tests don't behave the same. For the same browser version/driver version.

When using chrome for testing, it seems my tests need a whole more care.

For example, I have a test where I click on a dropdown menu button, then click on the first item of the dropdown menu that appeared.

When testing with Chrome, no issue.

When testing with Chrome for testing, I must update my test so that I tell it to explicitly wait for the dropdown menu to be visible in the dom, in order for it to not crash. It's a matter of milliseconds.

Maybe this shows I could have written my tests better; but I find very weird that behavior is different between basically just using chrome or chrome for testing.

Do you know of any default configuration of Chrome for Testing that could be set differently, that I missed?

Thanks!