AspNetHost

[Marius Grigoriu]

My goal is to run as many tests using the in process server as possible for execution speed while having an IE window open to run javascript-dependent tests and switching between the two browsers as necessary.

I am having trouble getting the in process host to work and it appears that even the samples have the same issue. After LaunchNewBrowser ActiveBrowser remains null and the following appears in the log:
ActiveBrowser was changed and set to LastOrDefault. Current active was either invisible or disconnected
ActiveBrowser was changed and set to LastOrDefault. Current active was either invisible or disconnected

Unable to find anything in the documentation, I am hoping that someone here can help.
Thanks!

[Cody]

Hello Marius Grigoriu,

I am sorry to report this is a known problem with our 2011.1.502 release. Hopefully we can fix this shortly. I have logged this bug here.

In the meantime you should be able to use our 2010.3.1607 version which is still available for download.

Kind regards,
Cody
the Telerik team

[Lukasz Zwozniak]

I have a very similar problem.

while performing the following code

Element findEle = manager.ActiveBrowser.Find.ByContent("text");
actions.Click(findEle);

I get message:

- FindParam used: [Find logic: Use 'Content' where content is 'text' of type 'TextContent' and (none) ]
- Start Element: [Element: '#comment#:-1']

ActiveBrowser was changed and set to LastOrDefault. Current active was either invisible or disconnected

How select a button?

[Cody]

Hi Lukasz Zwozniak,

I am sorry to report this is caused by the same bug. This is scheduled to be fixed and released in about two weeks. You can track this here.

All the best,
Cody
the Telerik team

[Tim]

Hi,

Any idea to what this could be related (e.g. Browser / OS, etc.) so that I can try to work around it?


Thanks,

[Cody]

Hi Tim,

Unfortunately there is no work around. When we made changes to support WPF application testing we fatally broke the AspNetInProcHost option. The only "workaround" is to fall back to a build older than 2011.1.502, such as 2010.3.1421. At the moment we haven't had time to fix this bug. We will soon however.

Regards,
Cody
the Telerik team

[Cody]

Hi Tim,

I am happy to report this bug has been fixed in our latest public release. 

Best wishes,
Cody
the Telerik team