Hi Federico,

Lately I needed to focus on some other stuff in our project so I couldn't proceed with your test code.

Now that I tried it and found that It still doesnot work as it is trying to execute the script in the testFrame context and eventually ends up with the following JS exception:

 Test Stack Trace:

Line 14:
Line 15:  // execute a script that opens a new window that loads your real site
Line 16:  page.ExecuteScript("function openWindow() { window.open('Login.aspx'); return true;} openWindow();");
Line 17:
Line 18:  // get the popupwindow and automate against it.

[Microsoft.Web.Testing.Light.WebTestException: Exception was thrown by the client engine: "[TestExecutorException]: Unhandled JS exception while executing command handler function ExecuteScript.  (Details: {\"name\":\"TypeError\",\"message\":\"Object doesn't support this property or method\",\"number\":-2146827850,\"description\":\"Object doesn't support this property or method\"})" when running command: ExecuteScript on the target: < id=, index: 0>.]
   at Microsoft.Web.Testing.Light.HtmlPage.ExecuteCommand(BrowserCommand command) in C:\Users\mosborn.000\Desktop\Microsoft.Web.Testing.Lightweight\Framework\UI\HtmlPage.cs:line 110
   at Microsoft.Web.Testing.Light.HtmlPage.ExecuteScript(String scriptExpression) in C:\Users\mosborn.000\Desktop\Microsoft.Web.Testing.Lightweight\Framework\UI\HtmlPage.cs:line 207
   at UserManagementTests.SignInAndSignOut() in c:\v5\Www\UI\App_Code\Tests\UserManagementTests.cs:line 16

My web test method looks like as below:

[WebTestMethod]

// Navigate to the login page

// execute a script that opens a new window that loads your real site

// get the popupwindow and automate against it.

// Fill Login control user/password and click login button

page.Elements.Find("Password").SetText("password");

// Verify content of the Home page

// Click the logout link

// Verify login button now exists.

I traced back to the LTAF code where it was failing:

    evalInActiveFrame : function(expression) {
        // Frame containing the running test (where the script must be evaluated)
        var frame = TestExecutor.get_activeWindow().get_activeFrame().get_jsFrame();
       
        // Safari doesn't support changing the context of the eval function,
        // so it has to be done specially
        if ("safari" != DomSupport.get_navigatorName())
        {
           return frame.eval(expression);          //IT FAILS AT THIS LINE
        }
        .
        .
        .
    }

Can you provide some other insight?

Besides this, yes, it would be of great help if we can run the tests in new windows. Also, currently, test running frames can be used to display outputs/exceptions/logs etc instead.

Waiting for your response...