I've posted this over at the AQA forums as well but have only received one response so wanted to see if anyone else has any ideas....
I am having a couple of issues with using TestComplete inside of our TFS setup (although I suspect this is an issue with other source control systems as well...)
I have a test project inside of our main application solution in TFS that contains .tc8Test files for each of the Test Items in my TestComplete project. Each of these tests is associated with a Test Case in TFS. My TestComplete project is also stored in TFS source control in the same Team Project.
The issue arises when I want to add a new test to my test project. If I write a new routine in TestComplete and add a new Test Item to the TestComplete project, then add a new .tc8Test file to our test project, I have to go into each existing .tc8Test file and refresh it so it "sees" the new test. If I do not do this, I get an error message when I try to run automation that says "TestComplete project changed" and the tests do not run.
This is made worse by the fact that after I refresh each test I have to individually uncheck all Test Items except the one I want to run. I cannot uncheck the main project node in the tree (which unchecks all child test items). If I uncheck the main project, the test does not run. (See the attached screenshot for an image of what I mean...)
Are there any workarounds for this? My list of tests is growing daily and it is way too time-consuming to have to refresh every existing test just to add a few new ones...
I had another thought. What if, instead of creating a new TestItem for each test, you created a single test item that pointed to some other object (a script routine or a keyword test or something) that contained all the tests you want to execute. That way, you only need to check the one test item in TFS and, when you add new tests, all you need to do is update that code routine.
It's a bit of a kludge because it could end up being a rather LARGE routine containing lots of tests but it would be interesting to see if that is a sufficient work around.
Thanks for your continued thoughts on this issue...
I'd actually tried this before and it does work. It is much easier and solves the issue... The only problem with it is that we have individual test cases in TFS, and we lose the ability to track the individual cases using this method. Since we have separate testers who write test cases and set their Automation Status to Planned (which is what I use as my 'to do' list), we need to be able to track down to the case level.
I really appreciate your ideas and input though! I guess I just have to hold out hope that someone from AQA sees this and someday fix it. Seems like a pretty simple thing to at least fix it to allow me to sequentially add cases like you suggested on the AQA forums.