Rank 1
Hello,
we are doing web testing using Telerik Test Studio. On our main test machine everything was working fine until recently. For no obvious reason Google Chrome stopped responding and can no longer be calibrated.
Clicking the "Calibrate" button just gives an entry into the log. The log from Test Runner shows this error:
Telerik.TestStudio.Scheduling.Client.exe(7412:15),TestStudio] ChromeConfiguration.GetBrowserConfigurationStatus() : Error during serialization or deserialization using the JSON JavaScriptSerializer. The length of the string exceeds the value set on the maxJsonLength property.
Parameter name: input
We did not alter anything on the machine, there are scheduled runs on every hour. First few runs went through fine that day and then Chrome stopped responding. Any idea on how we can solve this?
Thank you, best regards.
Aleksandar
3 Answers, 1 is accepted
Hi Aleksandar,
I am sorry to know you have encountered such trouble.
Based on the shared details and error listed, I guess that something in the Chrome user settings on that specific machine causes the issue. Since we are not Chrome experts the best option seems to be reinstalling Chrome. However, it is important to remove all leftover user data before performing a fresh installation - please, check where to find that data here.
Once you complete the re-install of Chrome, please, also delete the Test Studio user settings for Chrome as well - basically this may not be necessary but it won't harm anything. So, please, open a file explorer and navigate to C:\Users\<username>\AppData\Roaming\ArtOfTest and locate the chrome_user_settings.json file - you can delete it as it will be created again with the default values.
Then, try to calibrate Chrome and let me know if that works this time.
Thank you in advance for your cooperation.
Regards,
Elena
Progress Telerik
Rank 1
Hello Elena,
thanks for the tip. Simply deleting the JSON file and user data from Chrome helped. No need to reinstall Chrome.
Thanks again, regards,
Aleksandar
Hello Aleksandar,
Thank you for the feedback - I am pleased to know that regenerating the Chrome settings resolved the errors.
Regards,
Elena
Progress Telerik