Visual Studio Integration additional command line arguments
I am currently working on migrating my test runs from Jenkins to Visual Studio with the goal of running them from TFS. It appears straight forward enough, but there is one thing in the Jenkins TestComplete plugin that I don't see in the Visual Studio Integration. The Jenkins TestComplete plugin has a field for "Additional Command Line Arguments". I use this field to pass the "/tr_prefer_wmpaint_hooking" for one of my tests that needs that particular text recognition mechanism. I do nota similar field in the visual studio integration. Is there a field I am missing or is there another way to accomplish this through visual studio? Thanks in advance. - Chris
How do you link work items in TFS using TestComplete? Can create 1 but not link 2.
Using Issue Tracking templates, one can create and modify existing work items in TFS to an extent. However, to link 2 work items together, it is unclear if that is at all possible. If you try to use AttachFileLink, it says that it only supports internal attachments so it would seem that TC intended for it to be used. My example is that I am using TC to run automated tests on code and create new bugs on an error. To make these usable and not become lost in TFS's backlog, I want these to be linked to a set test case (which I can specify by ID, title, etc). There does not appear to be an easy way to tell TC what other items these bugs should be linked to using IssueTracking and the only workaround I can see is to make the tester go in by hand and associate them all to the desired test case. Is there any way to automate this, likely by using IssueTracking or via a plug-in? I am using TC 11 and have Visual Studio 13 premium installed on my machine in addition to the web portal.
How to launch app, freshly-built by Team Build, for GUI testing?
Hi, I've searched the help and forums but haven't found the answer - I'm sure this must be a silly question: I'm trying to schedule GUI regressiontesting on our applications as part of our nightly automated build. Team Buildgets our C++ code from TFS each night and compiles/builds our applications. We now have a test project with test items linked to a Test Complete .pjs file located underneath the Visual Studio test project, with everything checked-in to TFS. The build service is set to run interactively so it can test the GUI. I've added the pre-/post- build events to copy the TC folder to the target directory. Team Build builds the code on a build agent VM called \\dev-agent, and the code ends up atC:\Builds\11\TFSProject\MySolution\bin on that machine. The TC project folder is getting copied there successfully. We also have a build drop location set up on the test controller itself,and the build output all ends up in a folder such as\\TFScontroller\Built Code\MyBuild\MyBuild_20150313.16, and again the TC project folder is getting copied there successfully. My question is - what is the recommended way of launching the freshly-build application at the start of each test? The location of the application to run changes with every build on the build controller (drop location), and the location on the build agent (where I'm assuming the tests and TestComplete will run) is also specific to that build agent (number "11" in my case, at present), and will be different if this build and these tests are run on a different agent, and also differ hugely from where they will appear on a tester/developer machine. Once the app is launched, all the clicking, checkpoints, etc., should all work, but I'm not sure at the moment how to actually start the application in the first place, ready for testing. Sorry if this is a stupid question - any help greatly appreciated! Thanks, Richard
