Frames sample test fails on IE9 (Win7)

[Andrei]

Hi,

Frames test that comes together with your framework (%program files%\Telerik\Test Studio\Samples\Testing Framework\QuickStarts_NUnit_CS\Tests\Frames.cs) fails on machine with IE9 and Windows 7 (32-bit) with the following error:

QuickStarts_NUnit_CS.Frames.FramesAction:
System.NullReferenceException : Object reference not set to an instance of an object.

at QuickStarts_NUnit_CS.Frames.FramesAction() in c:\Program Files (x86)\Telerik\Test Studio\Samples\Testing Framework\QuickStarts_NUnit_CS\Tests\Frames.cs:line 138

Latest WebAii version is used - 2013.2.1327.0

The same tests passes on IE11 and Windows 8.1

[Konstantin Petkov]

Hello,

Thank you for contacting us!

I'm trying to replicate that but unable to do so. The exact line in the class from the result is empty on my end.

Can you please elaborate more on the problem? Is this a compilation error or a playback one? If the latter can you share the test runner you are playing with? Also how about the NUnit version? I have installed the latest NUnit v. 2.6.3 and it works just fine on the Windows 7 machine.

Looking forward to hearing from you.

Regards,
Konstantin Petkov
Telerik

[Andrei]

Hi,

sorry to mislead you, actual exception line is 133 (I was testing on two machines and provided logs from instance where I've been trying to make changes to the file) at the following code:

132            Browser t11_frame = ActiveBrowser.Frames["T11_Frame"];
133            t11_frame.RefreshDomTree();

I've tried now with the latest NUnit version (2.6.3.13283) and issue has re-produced. Are there any logs that could help you find the problem?

I am performing the following steps:
1. Build QuickStarts_NUnit_CS project from command line using MSBUILD
2. Open NUnit UI and load obtained dll
3. Select FramesAction test and run it - exception occurs

Please tell me if you have any questions.
Thank you, 
Andrei

[Konstantin Petkov]

Hello Andrei,

Thanks for the additional info!

This problem has been addressed recently and the fix will be available in the next official release coming in a week or two. We just confirmed the problem is no longer reproducable with the latest internal build, which you can download from your Telerik account:

Download link

Version notes

Regards,
Konstantin Petkov
Telerik