Home • Corporate • Contacts •

TETware Knowledgebase

Products

Solutions

Information

Datasheet

Documentation

FAQ

Knowledgebase

Return to Knowledgebase Index

35. How to identify test case timeouts in the journal file

Question

When tcc is invoked with the -t option, the journal reports the test purpose result for a timeout condition as NORESULT (auto-generated by TCC). How can I determine that the cause of this failure was a test case timeout?

Answer

The fact that tcc has timed out a test case or tool is indicated by the exit status in the Build End, Test Case End or Clean End line in the journal. The exit status appears in the 2nd subfield of the 2nd field on lines of type 130, 80 and 320. A timeout is indicated by a value of -2 in this field.

A zero or +ve exit status in the End line comes from the test case or tool, while -ve exit status indicates some condition that is reported by tcc. Your report writer should examine this field and generate a suitable message when the exit status value in the End line is non-zero. For the convenience of C language report writers, symbolic constants which relate to journal values are provided in the file tet-root/inc/tet3/tet_jrnl.h.

Users of Win32 systems are advised not to use tcc -t to time out test cases and tools.

See also

• "Journal line parameters" in the TETware Programmers Guide.

 

• "Test case termination'' in the "Implementation notes for TETware on Win32 systems'' in the TETware User Guide.

• "TETware journal lines'' in the TETware User Guide.

 

• The tcc manual page in the TETware User Guide.