9 Answers, 1 is accepted
0
Hello QA,
Errors like this seem to be a common problem. Take a look at this search result for example.
So from what I see in this ASP.NET forums thread the system may be missing a .Net update. Can you check if there are pending updates for this machine?
Greetings,
Konstantin Petkov
the Telerik team
Errors like this seem to be a common problem. Take a look at this search result for example.
So from what I see in this ASP.NET forums thread the system may be missing a .Net update. Can you check if there are pending updates for this machine?
Greetings,
Konstantin Petkov
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items
0
Kristine
Top achievements
Rank 2
Rank 2
answered on 11 Aug 2010, 10:41 AM
Hi Konstantin,
I've updated my machine using Windows update but the problem did not go away. Note that I have VS 2010 installed in my machine.
Regards,
QA
I've updated my machine using Windows update but the problem did not go away. Note that I have VS 2010 installed in my machine.
Regards,
QA
0
Hello QA,
VS 2010 comes with .Net framework v4 but the test studio does not depend on the new framework version. We build the tool on top of .Net 3.5 SP1 and it seems the problem comes from the core of the framework.
I think this blog post gives a good overview of the issue and they seem to have promised to fix it with the Service Pack. They probably haven't though. As the blog author describes this issue comes from unwanted garbage collection so I'm not sure if we have any control over that. I suppose we probably have no such control though especially as you report this happens from time to time.
Can you please try running the same test list on another machine around? If that doesn't happen on another one in the same network, that probably means there are different updates available on the first over the other.
I will also share the problem with the devs here and see if we can come to any work-around.
Kind regards,
Konstantin Petkov
the Telerik team
VS 2010 comes with .Net framework v4 but the test studio does not depend on the new framework version. We build the tool on top of .Net 3.5 SP1 and it seems the problem comes from the core of the framework.
I think this blog post gives a good overview of the issue and they seem to have promised to fix it with the Service Pack. They probably haven't though. As the blog author describes this issue comes from unwanted garbage collection so I'm not sure if we have any control over that. I suppose we probably have no such control though especially as you report this happens from time to time.
Can you please try running the same test list on another machine around? If that doesn't happen on another one in the same network, that probably means there are different updates available on the first over the other.
I will also share the problem with the devs here and see if we can come to any work-around.
Kind regards,
Konstantin Petkov
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items
0
Hi QA,
Just wanted to check back with you and see if you have managed to resolve this error on the problematic machine. That can surely help someone else running into the same error, thank you!
Kind regards,
Konstantin Petkov
the Telerik team
Just wanted to check back with you and see if you have managed to resolve this error on the problematic machine. That can surely help someone else running into the same error, thank you!
Kind regards,
Konstantin Petkov
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items
0
Kristine
Top achievements
Rank 2
Rank 2
answered on 17 Aug 2010, 08:29 AM
Hi Konstantin,
I am still encountering the same error using the same machine. I haven't tried running the test list in another machine though. I just split the test list into several test lists as a workaround for the mean time.
Regards.
QA
I am still encountering the same error using the same machine. I haven't tried running the test list in another machine though. I just split the test list into several test lists as a workaround for the mean time.
Regards.
QA
0
Hi QA,
I'm glad that worked for you. It is also good to know of the work-around and hope that can help someone else as well.
Greetings,
Konstantin Petkov
the Telerik team
I'm glad that worked for you. It is also good to know of the work-around and hope that can help someone else as well.
Greetings,
Konstantin Petkov
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items
0
Kristine
Top achievements
Rank 2
Rank 2
answered on 18 Aug 2010, 04:14 AM
Hi Konstantin,
I did some observations in the test list execution. I'm not sure if this info will help, but I think the error is encountered during these scenarios (so far):
1. Wait for condition has timed out. I have set the wait for element timeout to 120,000 ms. In the test list, I also have all timeouts to 120,000ms. Maybe the client-server timeout is much less than this?
2. Test that is bound to repeat a lot.
e.g. My original login scenario has 4 user logins. It does not continue to the next test after the 4th run. I tried reducing the data bind to 3 user logins, it now runs ok.
3. Memory exhaustive tests, e.g. something that does a search on a grid (several pages of it) for a particular item using the Find.AllByType function.
Regards,
QA
I did some observations in the test list execution. I'm not sure if this info will help, but I think the error is encountered during these scenarios (so far):
1. Wait for condition has timed out. I have set the wait for element timeout to 120,000 ms. In the test list, I also have all timeouts to 120,000ms. Maybe the client-server timeout is much less than this?
2. Test that is bound to repeat a lot.
e.g. My original login scenario has 4 user logins. It does not continue to the next test after the 4th run. I tried reducing the data bind to 3 user logins, it now runs ok.
3. Memory exhaustive tests, e.g. something that does a search on a grid (several pages of it) for a particular item using the Find.AllByType function.
Regards,
QA
0
Hello QA,
So it looks like some heavy operations may cause troubles in general. I'm especially concerned about the memory consumption since the browser may take a lot of memory depending on the application under test and the operation the test performs.
Thanks for sharing that info!
Sincerely yours,
Konstantin Petkov
the Telerik team
So it looks like some heavy operations may cause troubles in general. I'm especially concerned about the memory consumption since the browser may take a lot of memory depending on the application under test and the operation the test performs.
Thanks for sharing that info!
Sincerely yours,
Konstantin Petkov
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items
0
Kristine
Top achievements
Rank 2
Rank 2
answered on 20 Aug 2010, 04:21 AM
Hi Konstantin,
I was able to run the test list using a different machine, and I still encountered the .rem error. Yeah, the workaround for now is try to split the test list into several lists. I do hope Microsoft will be able to come up with a fix soon. Thanks so much for the assistance.
Best Regards,
QA
I was able to run the test list using a different machine, and I still encountered the .rem error. Yeah, the workaround for now is try to split the test list into several lists. I do hope Microsoft will be able to come up with a fix soon. Thanks so much for the assistance.
Best Regards,
QA