Project Log Panel shows incorrect number of tests executed
I have set up in Test Organizers to utilize network tasks which contain network jobs to utilize parallel execution.
When the a network task executes say 3 network jobs the Project Log Panel shows number of test items. Is it possible
to have it show that it executed 3 tests? It is misleading to reviewers of our test execution results.
If it is not possible to show that it executed 3 tests is it possible to disable that feature.
The reason being is that our test results are part of formal documentation for regulatory submission.
Thanks,
Jeff
It sounds like you need to do one of two things:
1) As part of your regulatory documentation submission, you have documented how to interpret the TestComplete logs to be able to match what the TC logs say to what the reg requirements are. Having worked in a regulatory environment before (pharmaceutical clinical trials), so long as there are documented policies, procedures, etc., to go along with the submitted documentation, the auditors are usually fine with that. If you can explain what is out put by the testing tool in language that co-incides with your reg requirements, they are happy.
2) You need to build into your automation solution a way of writing the output that displays as "3 tests". I've done this in the past using the Log.AppendFolder and Log.PopFolder methods to create sections in my log to outline the tests as they are executed. The reason why test complete shows things as "test items" is because, as the tool is designed, there is a great deal of flexibility as to what constitutes a "test". Is every Script function a test? Is every KeywordTest a test? Or is a test a combination of several keyword tests and/or script functions? Or is a test driven by an external data source which fires off different script functions which, themselves, don't constitute specific tests but are "building blocks" that create tests? In other words, how do you define "a test"? Whatever definition you use, you then need to write appropriate out-put code, either directly to TC's log or to some other source location (SQL, HTML, etc) that formats the output do match your definition of "test".
