Facing issues while running test list

Hi Rashmi,

Thank you for choosing Telerik Test Studio. 

When running tests that require direct desktop interaction you need to keep an active session on your execution machine. Another thing to try could be to enable the "SimulateRealClick' feature for the click steps (see the attached screenshot for reference). 

If the above does not suit your scenario please elaborate more on the experienced issue - is the single test execution successful, do you run the test lists remotely or locally, etc. 

Please let me know if I could assist you further. Hope to hear from you soon. 

Regards,
Elena Tsvetkova
Telerik

Hi Elena,

Thanks for the reply.

I am running test suite keeping an active session on the execution machine.

Test cases are passing with single test execution but in test list run I am getting these issues. I am remotely connecting to Vm and executing the test list.

In test list execution ,some test cases are getting hanged while clicking some controls in dialog window or entering first textbox in the page.When we manually close the app,the suite execution will continue.

Thanks,

Hi Rashmi,

Please let me know if you have tried with the 'SimulateRealClick' feature? 

I would like to know if you run the single test remotely as well? Have you tried to run the test list locally and observe what happens in this case? Depending on which machine the single test and test list executions fail, please provide us the application log or the remote machine one. 

It would be also helpful to know if the environments on the execution machines and the main machine are different. 

Thank you in advance for the cooperation and I hope to hear from you soon. 

Regards,
Elena Tsvetkova
Telerik

Hi Elena,

I have tried the 'SimulateRealClick' feature in some places but not every places as 'SimulateRealClick' is not helpful for if any script is rendered with click operations.

I am running the single test also remotely and executing test list in the same machine remotely .Test cases are failing only in test list run not in single test execution and that to failure is not consistent with test cases.

Attached application log and remote machine status.

Thanks,

 

Hello Rashmi,

The log you have provided is enormous and hard to investigate. Isolate the problematic test in a test list and execute it. Prior the execution clear the log so this way we can have the actual error you are facing. Also try using a wait for exist step for the failing element and let me know the outcome.

Regards,
Ivaylo
Telerik

Hi Ivaylo,

Below is the selected test log when it fails and also execution will not continue until user manually close the application,

'5/17/2016 1:41:58 AM' - 'Fail' : 8. Verify 'WelcomeTOMTextblock' text Same 'Welcome TOM'
------------------------------------------------------------
Failure Information: 
~~~~~~~~~~~~~~~
Exception thrown executing coded step: 'Verify 'WelcomeTOMTextblock' text Same 'Welcome TOM''.
InnerException:
ArtOfTest.Common.Exceptions.AssertException: Page is not loaded - [Expected:False],[Actual:True]
   at ArtOfTest.Common.UnitTesting.Assert.IsFalse(Boolean condition, String message)
   at RF8_TestAutomation.Login.Login_CodedStep4() in c:\Users\Administrator\Source\Workspaces\01_05Aug\Resource Financials\Dev\RF8\RF8_TestAutomation\SmokeTestcases\Login.tstest.cs:line 155
------------------------------------------------------------
'5/17/2016 1:41:58 AM' - Detected a failure. Step is marked 'ContinueOnFailure=False' aborting test execution.
------------------------------------------------------------
'5/17/2016 1:41:58 AM' - Overall Result: Fail
'5/17/2016 1:41:58 AM' - Duration: [37 min: 28 sec: 957 msec]

and I can see the performance of test list results are degrading after several execution.

Is there any limitation with trial version of test studio because I can see after installing telerik test studio,for first 10 days test list failure are very minimal but after some 15 days of trial period ,failures are more.

And also I have tried using " wait for exist step for the failing element ",the system is wait for whatever timeout we are given but the element is not being clicked(actions will not be continued) even though element is exist.I am not sure "wait for exist" functionality is working fine in trial version.

Hello Rashmi,

From the exception it looks like the browser does not return ready state, I don't know what might be causing this until I reproduce the behavior on my end.

Is there any way you can provide us with the application so we can take a look at this behavior?

Regards,
Ivaylo
Telerik