WaitForWindow fails even the window exists

[Thao]

Hi Telerik, here's the scenario:

1. Click a button on the main window to open a new window called xWindow. WaitForWindow("xWindow Caption", 10000) works just fine and returns xWindow. Close xWindow by clicking a button on it plus checking: xWindow.Window.WaitForVisibility(false, 10000) and xWindow.Window.exists is false.

2. Click that button again to open xWindow the second time. WaitForWindow("xWindow Caption", 10000) fails and throws a TimeoutException. The funny thing is that the exception lists the current existing windows including "xWindow Caption".

Please have a look at my situation.

Thank you,

[Boyan Boev]

Hello Thao,

I am not able to reproduce this behavior.

Could you please give us a direct access to your application along with the tests so we can reproduce this issue.

Or you can create some sample test against a public site where this issue is reproducible.

Hope to hear from you soon.

Regards,
Boyan Boev
Telerik

 

 

[Thao]

Hi Boyan,

Please find attached a sample of the scenario. It will work when we run the test. However, if we debug the test without any break points. It will throw the exception as I mentioned.

Moreover, it may happen that it sometimes fails at line 152 too (TelerikVSUnitTest1.cs).

This behaviour may relate to this.

 Thank you,

[Boyan Boev]

Hi Thao,

Thank you for the project.

I will update this thread shortly.

Thank you for your cooperation.

Regards,
Boyan Boev
Telerik

 

 

[Boyan Boev]

Hello Thao,

Unfortunately I am not able to reproduce this issue. 

The test passes without any issues.

How it is supposed to fail? Could you please record a short Jing video with the test execution.

Do you have installed Test Studio or only the framework?

Hope to hear from you soon.

Regards,
Boyan Boev
Telerik

 

 

[Kateryna]

Hi Boyan,

I've been using Telerik 2012.2.1204 for several years. Then I decided to upgrade it and installed 2015.2.723 version. We have approximately 200 tests with many windows opening/closing in every test. In version 2012 it was running ok, but after the upgrade 30% of tests were failing with error "Unable to find a window". I'm experiencing the same issue as Thao -  ArtOfTest.WebAii..WpfWindow WaitForWindow doesn't see opened windows. This is quite a random issue and is not stable even for the same window. This makes 2015.2.723 version absolutely unworkable for us. I reverted all changes back to the old 2012 version, but it's not a solution. I guess many people won't be able to use your new version because of this critical bug.
Were you able to catch that problem? In what version of the product will it be fixed?

Thank you.

[Boyan Boev]

Hi Kateryna,

I am sorry to hear you are experiencing such issue.

Could you please upgrade to our 2015.3.1015 version and give that a try.

If the issue persists please send us the application log. Clear it first and reproduce the issue.

Hope to hear from you soon.

Regards,
Boyan Boev
Telerik

 

 

[Kateryna]

Hi Boyan,

thank you for advice. I will do this early next week and will post an update here.

Thanks,

Kate

 

[Kateryna]

Hi Boyan,

I did an upgrade to 2015.3.1015 version as you advised. Then I just run a simple cycle of opening and closing the same window. On approximately 10th iteration (note, it can be 2nd or 31st ​one. This is a random, but a consistent problem), the window was not identified.

I'm attaching a log that was recorded.

Thanks,

Looking forward to hearing from you.

Kate

[Ivaylo]

Hello Kateryna,

Unfortunately we will need to reproduce the problem in order to investigate what is causing it.

Do you think you can provide us with reliable repro for investigation?

Regards,
Ivaylo
Telerik

 

 

[Kateryna]

Hi
I cannot provide you with our code, obviously. I'm pretty surprised you cannot figure out that issue by stake traces. Also, I'm very surprised no one is reporting it.
I was thinking to create a separate simple test solution with just opening and closing the window for our app, so that you could change it to any other WPF application with windows, Unfortunately, I haven't had time for this. Still I will try to find some time during next few weeks. This is allI  can do more to help you to catch that critical problem.

[Ivaylo]

Hеllo Kateryna,

The exception in the stack trace is too generic that is why we cannot determine it by looking at the log provided.

As soon as you are able to provide is with reliable repro of the problem you are experiencing we will be happy to take a look and investigate further.

Thank you for your cooperation in advance.

Regards,
Ivaylo
Telerik

 

 

[Kateryna]

Hi Ivaylo and Telerik team,

I've been quite busy. Now I created a small test WPF application with one window opening and Telerik test solution that uses the newest Testing_Framework_2016_1_0330_2 libraries.

The bug is very easy re-creatable there. Now it's failing pretty consistent on the 2nd try. I also run my test solution with old Telerik2012 and it works perfectly.

I included a small ReadMe file as well. Zip is 2.5Mb cause I included libraries, so shared it here https://www.dropbox.com/l/s/2qRUjyLVSPtOR507QAXFhr 

Looking forward to this bug being fixed.

Thanks,

 

[Boyan Boev]

Hello Kateryna,

How should I run the test? When I run TelerikWindowOpening it crashes (see the attached screen shot).

Could you please guide how to run this test?

Hope to hear from you soon.

Regards,
Boyan Boev
Telerik

 

 

[Kateryna]

Hi Boyan,

Did you read "ReadMe" file with all instructions that I mentioned?  Did you change paths to libraries? For this, you obviously need to install EXACTLY the same version of Telerik Testing framework on your machine (see the number in the previous comment). It won't run with any other version, of course.

I verified my test solution in another PC.(Downloaded my  file, installed Telerik testing framework, corrected paths and run from VS12 - All good).

Please make sure you did all required actions before running the app.

Thanks.

[Ivaylo]

Hello Kate,

I have reproduced this problem with the latest official release, however with one of the branches I cannot reproduce this behavior, can we allow some time for us to merge branches, and see whether this will be reproducible.

Regards,
Ivaylo
Telerik

 

 

[Kateryna]

Hi Ivaylo,

sure, take your time to investigate this bug. It's been there for quite some time. A few last releases that I tried for sure.

Thanks

[Boyan Boev]

Hello Kate,

Thank you.

We will update this ticket accordingly.

Regards,
Boyan Boev
Telerik

 

 

[Ivaylo]

Hello Kate,

Please excuse me for the delayed reply. Can you give it a  try with the latest internal build, I am no longer able to reproduce the behavior.

Regards,
Ivaylo
Telerik

 

 

[Kateryna]

Hi Ivailo,

what do you mean by "latest internal build"?

Do you mean I should wait for the next release version?

Do you know when Telerik Testing Framework new version is going to be released?

Thanks

 

[Ivaylo]

Hello,

We have a new internal build from the last week. Try to download and install it and verify the behavior.

Regards,
Ivaylo
Telerik