This is regarding running multiple desktop application in ranorax. My queries are
Q1- can we execute multiple test cases parallel in Ranorax ?
Q2- If one ranorax script is running, can we hide ranorax window? The intention of doing this is so that System can be utilized to do other tasks.
Thanks for time and consideration.
Thanks
Punit (Arpit3)
Running Parallel test cases on Desktop Applications
Re: Running Parallel test cases on Desktop Applications
Hi,
As for question #1, no, you can't run multiple test cases/suites at the same time (on the same desktop). You see, it would be like if two or more real users would like to use the same computer at the same time. Even if you would be able to connect two or more mouses/keyboards to the same computer, what would be expected result if one user would like to drag mouse to the left and the other one to the right? You see the issue?
And this is exactly what would happen with two different tests running at the same machine/desktop.
Then only proper way to run multiple tests at the same time would be using multiple machines (either physical or virtual), ideally with some sort of continuous integration tool (e.g. Jenkins, Bamboo, etc.).
As for #2, I'm not quite sure, which window exactly do you want to hide? If you want to hide Ranorex progress dialog, it could be done by unchecking "Show Progress Dialog" option in Test Suite settings, as shown here:
http://www.ranorex.com/support/user-gui ... html#c3024
Or via code:
As for question #1, no, you can't run multiple test cases/suites at the same time (on the same desktop). You see, it would be like if two or more real users would like to use the same computer at the same time. Even if you would be able to connect two or more mouses/keyboards to the same computer, what would be expected result if one user would like to drag mouse to the left and the other one to the right? You see the issue?
And this is exactly what would happen with two different tests running at the same machine/desktop. Then only proper way to run multiple tests at the same time would be using multiple machines (either physical or virtual), ideally with some sort of continuous integration tool (e.g. Jenkins, Bamboo, etc.).
As for #2, I'm not quite sure, which window exactly do you want to hide? If you want to hide Ranorex progress dialog, it could be done by unchecking "Show Progress Dialog" option in Test Suite settings, as shown here:
http://www.ranorex.com/support/user-gui ... html#c3024
Or via code:
Code: Select all
// hide Ranorex progress dialog
Ranorex.Controls.ProgressForm.Hide();
// show Ranorex progress dialog
Ranorex.Controls.ProgressForm.Show(); Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
Ranorex explorer at Descartes Systems
Please add these details to your questions:
- Ranorex Snapshot. Learn how to create one >here<
- Ranorex xPath of problematic element(s)
- Ranorex version
- OS version
- HW configuration
Re: Running Parallel test cases on Desktop Applications
Thanks for response on Queation 1.
Question 2 is in the context of application window on which Ranorex automation is being performed and can same window be minimized through automation script before triggering the actual automation steps, instead of using mouse clicks and keystrokes based automation can we make use of control objects to perform the activities like button click, set the text in the text box.
Intention of doing this is we want to utilize system for other tasks.
Thanks for time and consideration.
Question 2 is in the context of application window on which Ranorex automation is being performed and can same window be minimized through automation script before triggering the actual automation steps, instead of using mouse clicks and keystrokes based automation can we make use of control objects to perform the activities like button click, set the text in the text box.
Intention of doing this is we want to utilize system for other tasks.
Thanks for time and consideration.
Re: Running Parallel test cases on Desktop Applications
You should NOT be using your test system for ANY other purpose while you are running tests. Any use could jeopardize the consistency of your test cases and the actions of the test itself. Ranorex makes this pretty clear in their documentation.
If you need to have your tests run without interfering with the user using the PC, then you could look at getting a Virtual Machine setup on the user's system, or in a VM farm, if you have one available.
Otherwise you should wait for the test to complete before continuing to use the system.
Having said that, you CAN use specific actions against elements in your SUT, but there are drawbacks, not the least of which is that when Ranorex fires these actions, it does not always fire all events associated with the element. Some developers and frameworks attach events to specific actions such as mouse clicks and key presses, while the Ranorex actions may activate different events.
My suggestion is that you test the system the way a user would use it, using Ranorex to move the mouse and enter keyboard input through it's filter drivers. Doing otherwise also leads to the test not really testing user input, but testing the underlying API of the framework of your SUT, which is great, but usually that isn't what a functional tester wants.
If you need to have your tests run without interfering with the user using the PC, then you could look at getting a Virtual Machine setup on the user's system, or in a VM farm, if you have one available.
Otherwise you should wait for the test to complete before continuing to use the system.
Having said that, you CAN use specific actions against elements in your SUT, but there are drawbacks, not the least of which is that when Ranorex fires these actions, it does not always fire all events associated with the element. Some developers and frameworks attach events to specific actions such as mouse clicks and key presses, while the Ranorex actions may activate different events.
My suggestion is that you test the system the way a user would use it, using Ranorex to move the mouse and enter keyboard input through it's filter drivers. Doing otherwise also leads to the test not really testing user input, but testing the underlying API of the framework of your SUT, which is great, but usually that isn't what a functional tester wants.
Shortcuts usually aren't...
Re: Running Parallel test cases on Desktop Applications
thanks for the reply,
We tried running test case in minimized mode on java swing application. We are able to click on buttons (using press method) and enter data in textfield in application window minimized mode only. But when the control comes to combobox, application window gets maximized. Is there any way to run the action on combobox in minimized mode.
We tried running test case in minimized mode on java swing application. We are able to click on buttons (using press method) and enter data in textfield in application window minimized mode only. But when the control comes to combobox, application window gets maximized. Is there any way to run the action on combobox in minimized mode.
-
Support Team
- Site Admin
- Posts: 12145
- Joined: Fri Jul 07, 2006 4:30 pm
- Location: Houston, Texas, USA
- Contact:
Re: Running Parallel test cases on Desktop Applications
Hi Arpit,
Unfortunately, there is no way to run certain actions with minimized window, since the element needs to be visible for e.g. a click-action.
Could you tell me if there is a special reason for testing the application in minimized state.
Kind regards,
Matthias
Unfortunately, there is no way to run certain actions with minimized window, since the element needs to be visible for e.g. a click-action.
Could you tell me if there is a special reason for testing the application in minimized state.
Kind regards,
Matthias
