When I right click the method in the project that I created, and then select "Generate Code for Coded UI Test -> Use Coded UI Test Builder", I get the following error message " To edit or add another coded UI test, you must first close the Coded UI Test Builder that is open"
Now, I am not sure where do I have to go and close the already open Coded UI Test Builder?
Anyone?
Thanks
Running multiple CodedUI test on same active desktop is not supported.
Then close that one which is already on:
Your problem is that there is another instance of the test builder open, or at least visual studio sees that as the case (it is not supported to have more than one open at a time). Verify that there is nothing open either in task manager, or by restarting.
Related
I am using BluePrism v6.1.0 and I am trying to identify elements from a launched application in Application Modeller. (I used the Windows application type in the modeler configuration)
From some tutorials I saw, the launch button changes to Identify button after the app is launched, however, mine is still showing "Launch". Please see screenshot below
screenshot
You need to launch the application from the application modeller, not on your own.
Since you are using Windows 10, the built in applications are use differently than normal in windows 7. Here is how you can add the code to make it work with your system Screenshot. Also for future applications use this code in Windows Power Shell to get information about the application you wanted to work with in Window 10 : "Get-AppxPackage"
Not fully explained here but this can also mean not only is the app not launched but blueprism can't "see" the app is launched. Two ways to solve this so close the application and relaunch it then it will change to identify, OR you can attach the current instance of the object to the running application.
Either way the outcome is you're making blueprism see the active application so it will change the launch to an identify option.
Edit: watch out as well, if you connect your application to blue prism and then detach it blue prism will no longer see the running application hence will revert the identify option into a launch option.
Using the Test hub in the Web Portal why is the "Associated Automation" tab completely empty, greyed out and prevented from being used?
What do I need to do to enable all this and run a coded ui test? I have hand coded, Coded UI tests that are build and in dlls but need to run the tests in those dlls in my test suite.
For background, I can run the tests in the dlls using a batch file and have done so successfully but struggling to get started running them from my test plan! My Microsoft "Test Manager" has the same problem, all greyed out but as Test Manager is being deprecated I am less concerned about that.
EDIT:
Another way of viewing this problem is to ask why does the Automation Status not show the option "Automated"? See picture below ...
It is not possible per MSDN documentation.
In the visual studio development environment, try right clicking on a test in test explorer, clicking something such as "Associate to Test Case", then entering in the test case number and see if that works. I believe it is greyed out because there is no valid input options through the web right now.
I have a script which was developed using TruClient for a web application. When I'am going through this test manually everything is working fine. When I'am doing the same test using TruClient in Virtual User Generator everything is fine as well(automated script is written properly).
The problem starts when I'm using LoadRunner Controller. From specified moment all the tests are failed(circa after 40 passed iterations/10 Vusers).
My question is: is there any possibility to check what was wrong on the website? Maybe take some screenshots or something?
(Controller 12.02.0.0 Build 1258)
Not sure if you know about this, but this is where I debug TruClient (and all) scripts which are running in Controller mode.
1) Goto the "Run" tab
2) Double click on the group of the user you want to look at.
3) Right click on the user you want to look at (some could be running or failed)
4) Select "Show User Log"
This will show the console output of the script so will show you then a step starts or finishes, and any LR.log statements you have scripts.
You can enable get screenshots on error (I think it may be enabled by default) in the run-time settings, but I haven't had any luck with the option in there to get a screenshot of every step.
If you restart a user then your logs will be overwritten.
I am using build deploy test workflow to execute testcases on Lab environment-CodedUI. Browser IE instance remains open after test execution is over.
I am thinking if I can add something to my build workflow, which send instructions on test agent machine to close that browser instance. Is that possible?
I execute testcases in bunch. No testcase close the browser instance. They work on same browser instance to save login time. Hence I want to close browser once execution is over
Regards,
Gbhavsar
You can use the inbuilt functionality of settings
browserInstance.CloseOnPlaybackCleanup = true
or use a custom .bat file to close/kill all open IE/Chrome/FireFox processes in your post test script.
See https://blogs.msdn.microsoft.com/visualstudioalm/2012/11/08/coded-ui-test-why-does-application-close-after-each-test-in-visual-studio-2012/
I have created a number of (standalone) automated test-cases captured using CodedUITest in Visual Studio 2013, to test webpages.
They work fine within Visual Studio, individually; and when several of them are put into a single project as a solution, to create a kind of playlist.
However, I'm trying to use Microsoft Test Manager as a 'front-end' - in order to be able to select which tests, create play-lists, decide how many times a specific test-case should be run etc, with the results stored.
TFS is being used to both store my (individual) test-cases, and, where I'd like to deposit the resultant output of pass/fail etc.
Trouble is, even though the test-automation part functions very well within Visual Studio, getting Microsoft Test Manager to function with what I have, and its associated environment is proving a COMPLETE NIGHTMARE.
My system is simple; I have a virtual machine setup with the testing environment which allows (within VS) for me to run these automated tests.
Why is this proving so difficult to work with MTM? It should be easy - I should simply be having to point MTM at the folder my test-cases are stored, and use its GUI to tell it what and how many tests I want to run.
Anyone else have a similar problem, or a similar setup?
All MS do is point me to (countless) pages which I've already read - for which the whole lot seems to be much deeper than it needs to be.
You cant just point MTM at a folder and tell it to run the tests as it would have no idea where to put the data. The results of each codedui running are associated with a corresponding test case in mtm.
You also need to have an automated build create the output (your assemblies) for you. Idealy everything goes together with your application. As your application changes, so will your tests.
You should add your CodedUI projects to the same solution that is used to build the application that you are testing. Then when the automated build for that application kicks off your code is picked up to. Both things, test and application, end up in a drop location. It is that drop location that MTM will use to find your test assemblies.
If, while you have the main solution open, you open/create a Test Case you can go to the automation tab in Visual Studio and associate one of your CodedUI tests with that Test Case. The test case will then show up as Automated in MTM.
Now that we have the versioned bits and know where to find them MTM needs somewhere to run them. If you open MTM and switch to the Lab center you can create a Standard environment to run your tests. This will automatically go install the agents required so you wikk need admin on those boxes.
Now that we have both versioned tests and an environment you can find the Test Case in MTM and see that it is "automated". If you right-click on it and say run you will get a box requesting an environment, and which version of the bits to go run. It will then go off and run those tests against that environment and feed the result back into the Test Case.
Does that help?
You'll need to setup Test controller and Test agent and associate you build with a Test Plan in MTM.In Test Lab you need to associate Test Agent to the Test Controller.
Once done you'll need to allow File & Printer sharing exception
And then you will have to add Test Controllers and Agents to Appropriate Groups.
Control Panel->All Control Panel Items->Administrative Tools->Computer
Management