Why automate? I do automated testing because there's only so much a human being can do and remain healthy. Sleep is a requirement. So, while people sleep, automation that I create does what I've described above in order to make sure that nothing gets past the final defense of the testing group.I love good food, good books, good friends, and good fun.

Re: JavaScript runtime error. TypeError: browser.Page is not a function

MY guess is that you have an object mapped as just straight "page" in your NameMapping. Probably something like NameMapping.Sys.browser.page. This is confusing TestComplete when you try and call the "Page" method of the actual browser object.

Why automate? I do automated testing because there's only so much a human being can do and remain healthy. Sleep is a requirement. So, while people sleep, automation that I create does what I've described above in order to make sure that nothing gets past the final defense of the testing group.I love good food, good books, good friends, and good fun.

Why automate? I do automated testing because there's only so much a human being can do and remain healthy. Sleep is a requirement. So, while people sleep, automation that I create does what I've described above in order to make sure that nothing gets past the final defense of the testing group.I love good food, good books, good friends, and good fun.

Re: JavaScript runtime error. TypeError: browser.Page is not a function

I'm not sure why it worked for you before. Basically, what that line is doing is returning a BrowserInfo object, not the actual Browser process running in Windows. So, the fact that it used to work is what is the mystery to me.

Why automate? I do automated testing because there's only so much a human being can do and remain healthy. Sleep is a requirement. So, while people sleep, automation that I create does what I've described above in order to make sure that nothing gets past the final defense of the testing group.I love good food, good books, good friends, and good fun.