Forum Discussion
if the test extension is being disabled then it may not be configured correctly like said above. However, today I experienced an issue with Chrome and my TC when using objectSpy. It would only recognize the window object. Kind of like firefox was doing to several individuals last week.
I admit I have not used the objectSpy in a little while, but I know it worked last time it was used (especially in Chrome). I checked the properties for it on my test machine and found all my 'switches' were gone. Dunno, possibly because of an update to either my browser or even my machine.
So hopefully easy answer for you is just to work through the preparing document. I am doing that right now myself. Crossing my fingers as well.
currently Chrome version: 68.0.3440.75 with Date Modified: 07/23/2018 04:13 PM EDT
- tristaanogre6 years agoEsteemed Contributor
If Chrome updated, that's the issue right there. Last I saw (and, I'll admit, I've been on vacation for 2 weeks), Chrome was at version 67... so, if you're at 68 now, it's entirely likely that the Chrome extension will need an update from SmartBear.
As documented, it's generally considered a best practice to turn off automatic browser updates for Chrome and Firefox to off set this lag time. Once the browser plugin is updated, you can then update your browser for the new version.
Related Content
Recent Discussions
- 3 hours agosimonaferrara
- 3 hours agoAli2