Forum Discussion

BigBear's avatar
BigBear
Occasional Contributor
7 years ago

TestComplete working with TFS as a source control system, checked-in test scripts are not visible

We currently encountered a problem with TestComplete working with TFS as a source control system. When a user checked-in a new keyword test to TFS, the test is not visible to other users in TestCompl...
  • tristaanogre's avatar
    tristaanogre
    7 years ago

    Ok, actually, it seems you may have a couple of problems.  The two errors you recently posted appear to be a latency problem with TFS itself that it's taking too long to communicate with the server to process the check in.

     

    Prior to that, though...

     

    when you add a test case, there are actually two files that need to be checked in: the test case itself and the KeywordTests.tcKDT file.  That second file is what the project uses to "know" what test cases belong to it.  If you check in only the test case itself and not that second file, then you'll get the behavior your reported... that the test case is in the source control, but when other users open the project, they don't see it as part of the project.

BigBear's avatar
BigBear
Occasional Contributor

When I added "an existing item", the test was added (with no error). Then I tried to check-in the added test, it showed the error in TestCompleteError.bmp (please see attachment 1) and I had to click on No (select Yes will keep the same message display again and again). Then it showed 2nd error in Error2.bmp (please see attachment 2). Maybe the error is because it is already in TFS and I tried to check it in again. But it didn't display in TestComplete the 1st time when it was check-in.

 

tristaanogre's avatar
tristaanogre
Esteemed Contributor
7 years ago

Ok, actually, it seems you may have a couple of problems.  The two errors you recently posted appear to be a latency problem with TFS itself that it's taking too long to communicate with the server to process the check in.

 

Prior to that, though...

 

when you add a test case, there are actually two files that need to be checked in: the test case itself and the KeywordTests.tcKDT file.  That second file is what the project uses to "know" what test cases belong to it.  If you check in only the test case itself and not that second file, then you'll get the behavior your reported... that the test case is in the source control, but when other users open the project, they don't see it as part of the project.

  • BigBear's avatar
    BigBear
    Occasional Contributor
    7 years ago

    I got it now. When I am adding a new test to the project, TestComplete will ask me to check out KeywordTests before I can add a new item. After I add the new test and check-in my new test, I also need to make sure that I check-in KeywordTests. If something happens in between that I only check-in my test without check-in the modified KeywordTests (modified by TestComoplete tool), then I will get the situation like I described here. That clears my doubts about why it happens. Thank you very much, Tristaanogre.