Hi there,

 

I was wondering if there is a way to get more information from the email that is sent out by the scheduler? Currently it gives very little output as to what the steps where leading up to the failure. For the person having access to Test Studio, you get to see the log files, and you can view the log files of a particular step that failed.

 

Surely there must be a way of attaching the log file, of a particular test step, to the excel document? Or maybe even a way of sending an email with the log file information via email? Not all persons involved will have access to Test Studio, and will not understand where tests are failing.

 

Any further info will be very much appreciated.

 

Thanks

New to Test Studio and we're trying to record a specific keyboard combination of Ctrl + Alt + Shift + P.

How would I go about creating a test step?

 

Thanks

Is there a way to clear unexpected browser message boxes that might display when running an automated test?

Occasionally, our AUT will display a message box if the test fires an event before the UI is ready. The message box causes the test to hang and this prevents subsequent tests from running.

Granted, this is a timing issue between our web site and the test that needs to be addressed, but I was thinking a test as a step could be added to each test to automatically clear any hanging message boxes if they should appear unexpectedly. This would keep our tests running on daily basis as we address the timing issues.

I've used a function in another testing tool, but I'm not sure how to accomplish this in a test as a step in Test Studio, so any suggestions would be appreciated!

Is there a way to camper values from the Data table?  For example:

If([User Role] = “Admin”) then run anything under the true branch.  In my case I want to do different validation for each role and do not want to go down the coding path as of yet. 

Any ideas?

Thanks,

John

Button not enabled when executing the test in TEST STUDIO

I had no trouble recording the test... during playback it does find the button and does simulate the click ... but since the button is not enabled, next page does not load and this causes the next step in the test fail.

 

Hello,

 I would like to compare an extracted date value from a txtbox or datepicker control.  There are multiple places in the application that we would have to verify that the current date is displayed.  So I would like to write this once and be able to reuse the function.  Has anyone done this before or have any ideas on how to do this?

 My initial thoughts would be to create a stand alone test with a coded step that compares an extracted date variable to 'DateTime.Now.ToString("M/dd/yyyy").  Then anytime I needed to compare dates I would always use the same extracted variable name.  Is this something that would work anywhere in a project?  

Thanks for your thoughts,

Leon

We like to run our tests on machines, where the Test Studio is not installed. Therefore we are deploying our dlls and all Test Studio dlls in the execution folder. When a test starts the Internet Explorer gets started and appears but the test-procedure does not continue, it fails. In the debugger we see, that the process times out in "Manager.LaunchNewBrowser();" ...

Everything else the same, just the Test Studio installed on the machine, the test succeeds...

Could you please give us some advice, what needs to be done, to run tests on a machine, where Test Studio is not installed?


The call stack:

Result Message: Initialization method DMS.GuiTest.PortfolioCRUDTest.TestInitialize threw exception. System.TimeoutException: System.TimeoutException: Wait for condition has timed out.
Result StackTrace:
at ArtOfTest.Common.WaitSync.CheckResult(WaitSync wait, String extraExceptionInfo, Object target)
   at ArtOfTest.Common.WaitSync.For[T](Predicate`1 predicate, T target, Boolean invertCondition, Int32 timeout, WaitResultType errorResultType)
   at ArtOfTest.Common.WaitSync.For[T](Predicate`1 predicate, T target, Boolean invertCondition, Int32 timeout)
   at ArtOfTest.WebAii.Core.Manager.WaitForBrowserToConnect(Int32 browserIndexToWaitFor)
   at ArtOfTest.WebAii.Core.Manager.LaunchNewBrowser(BrowserType browserToLaunch, Boolean waitForBrowserToConnect, ProcessWindowStyle windowStyle, String arguments)
   at ArtOfTest.WebAii.Core.Manager.LaunchNewBrowser()
   at DMS.GuiTest.DMSBaseTest.TestInitialize() in y:\DMS\_trunk\Client\DMS.GuiTest\DMSBaseTest.cs:line 54
   at DMS.GuiTest.PortfolioCRUDTest.TestInitialize() in y:\DMS\_trunk\Client\DMS.GuiTest\PortfolioCRUDTest.cs:line 18

Hi,

I did each steps[in an android device(4.4.2) ] following test studio mobile getting started document, But I encounter an issue:

Package 'com.telerik.demoapplication' not found.

 

Do everyone know how to fix it? Thanks in advance.

 

Nathan

Is the Test Studio included in DevCraft Complete package or is this a separate product to be purchased?

hi there,

I am working with Test Studio and trying to get my company to purchase this software for our internal testing needs; I am still learning though, and now I have also to overcome some strange but hard technical difficulties.

I recently switched from an older machine to a new one, so I moved from a Windows 7 laptop (64bit, i3 CPU, 4 GB RAM) to a Windows 10 one (64bit, i5 CPU, 8 GB RAM + SSD HDD); this new machine proved to be obviously faster and more reliable than the other one under any circumstance, as it was never used before but just freshly updated to latest versions of drivers and OS.

I saved on a external HDD the whole folder from the older system which carried all of the (working) tests I created there and pasted it in my new computer.

I reinstalled and updated Test Studio, the 3 browsers I was testing (Chrome, Firefox and Explorer 11) to their most recent versions. I was also pleased to see that Test Studio could recognize the folder created on the older system and import the test plan and their relative resources inside the interface in the new PC.

I installed the plug-ins, extensions, all the desired add-ons for the three browsers to work with Test Studio, on replay as well as on record side.

 

I started working on Test Studio and here came the disaster: I am having a terrible performance, the program runs ok while not testing, but the real problems starts when doing so.

----LAUNCHING EXISTING TESTS:

Chrome: seems to execute the test at first but then highlights all the wrong places of the web apps and runs slowly

Firefox: doesn't run the test, opens a window and then remains stuck at "preparing browser for automation"

Explorer11: seems to execute the test but highlights all the wrong places of the web apps and runs slowly

----RECORDING NEW TESTS (sometimes it even crashes before launch stuck at "Launching recorder..."):

Chrome: runs incredibly slow, even when staying still with mouse, moves herratically the red highlighting tool everywhere around the web page components and goes as far as filling up my system memory and forcing me to close the browser to stop.

Firefox: opens a new window, but shows the message "Please verify that the Test Studio Recorder extension is installed and enabled in your browser." I knew I did, but I even checked again as this happened: I have "Test Studio Automation" and "Test Studio Recorder" correctly installed and enabled at the moment of execution.

Explorer11: it seems to work somewhat well, surely the best of the three, it starts as a normal test recording and I even manage to highlight parts of the site correctly and even access the context menu, but after a while the highlighting tool starts moving on its own and I can't use the menu effectively anymore.

 

I tried uninstalling Test Studio, reinstalling it, disabling-removing-redownloading all the extensions but nothing happens.

Is this a known issue? I tried to find a solution in other threads, but I've gone just as far as discovering which .NET framework version I am running and it's the 4.6.1.

I would really appreciate a hand on this because working is becoming very difficult here.

Thank you very much in advance for any recommendation and, hopefully, a solution.

Until next time.