Forum Discussion
holliec
12 years agoNew Contributor
Tanya.
This is very simple. The support call with Rick was-- let me reiterate this again-- in my ORIGINAL post above.
Once again-- it has never been addressed as to WHY I had to change the DPI settings from 125% (DEFAULT) to 100% (NOT DEFAULT) to get the tests to execute. The ONLY variable that changed in my test environment is that I upgraded from Chrome 37 to Chrome 38 when the stable channel updated. NO other changes were made to this machine running Test Complete.
Having to repeat the same information three times is quite tiring, for this is a very simple issue. It appears as though I will just have to trouble-shoot this on my own, and/or accept running the system at 100% DPI to get the tests to execute, since we seem to be no closer to any alternatives. This is a very poor non-solution to a very real problem.
This is very simple. The support call with Rick was-- let me reiterate this again-- in my ORIGINAL post above.
Once again-- it has never been addressed as to WHY I had to change the DPI settings from 125% (DEFAULT) to 100% (NOT DEFAULT) to get the tests to execute. The ONLY variable that changed in my test environment is that I upgraded from Chrome 37 to Chrome 38 when the stable channel updated. NO other changes were made to this machine running Test Complete.
Having to repeat the same information three times is quite tiring, for this is a very simple issue. It appears as though I will just have to trouble-shoot this on my own, and/or accept running the system at 100% DPI to get the tests to execute, since we seem to be no closer to any alternatives. This is a very poor non-solution to a very real problem.