Forum Discussion

steveburton4's avatar
steveburton4
Occasional Contributor
13 years ago

Reporting test item results during test run via COM

Hi we have an application written in C# which we use for enabling all testers to run and schedule test runs on TestComplete/TestExecute.



For this we use the functionality of TestComplete via COM. This works fine and enabled us to complete the runs and using the GetLastResultDescription() method on ItcIntegration object we are able to report the result of the entire run.



However, we can not let the user currently know how the tests are progressing and how each test is going - whether each individual test item passes or fails. We use a complicated process involving the TC events, writing to text files and reading them in elsewhere to do it at the moment, but it is quite flaky.



Is there any way to do this via COM? Either through the main library or the TC internal interfaces library?

2 Replies

  • hlalumiere's avatar
    hlalumiere
    Regular Contributor
    13 years ago
    AFAIK there is no way to do this through the TestComplete libraries (which really are not libraries, but just a couple of members from the main application that are exposed Public...)



    What we do here is feed everything to a SQL database. It serves as a central hub for all the tools we created to manage the test environment. In our case we just feed the final log path to a table entry, but you could also write an entry in there for each subitem. One of our rows looks like this:



    ID    Duration    LogDate    Success    ResultsPath    ExBuildID    RunningNow    TestCode    EditionCode    LangCode    DbmsCode    MachineName    TestShortName    ProductName

    160    2.2    2012-11-29 14:50:19.197    1    \\LOGSVR\LOGS\MYPRODUCT\11.5.15.729\VMTESTSRV15\Results 2012-11-29\DBD-001 ERP ACCESS 1    8542    0    DBD-001    ERP    EN    Access    VMTESTSRV15    Dashboard test    MYPRODUCT




    Once everything is fed in there, you can run different queries on the table to get some metrics.  For example, we also cross reference the contents of the log table to our development tickets system to match tests to known issues waiting to be corrected, etc...