ALM Project Database Reference Version 12.55
td.TESTCYCL Table
Project Data Tables Database > td Schema : td.TESTCYCL Table
Description
Instances of design tests in test sets.
Remarks

A test can be used more than once in a test set. Each use is an instance. This table stores the position (order) of each instance and some data about the instance.

Multiple values for fields are maintained in the TESTCYCL_MULTIVALUE Table.

Columns
 Column NameDescriptionDatatypeLengthAllow NullsDefaultFormula
Primary Key TC_TESTCYCL_IDThe record ID.int4   
 TC_CYCLE_IDThe CYCLE.CY_CYCLE_ID of the test set containing this test.int4   
 TC_TEST_IDThe TEST.TS_TEST_ID of the design test of which this is an instance.int4   
 TC_TEST_CONFIG_IDThe TEST_CONFIGS.TSC_ID of the configuration used by this test instance.int4   
 TC_CYCLEFor backward compatibility. Field may be removed in future version.varchar255  
 TC_TEST_ORDERThe order in which the test instance appears within the test set in the user interface.int4  
 TC_STATUS

The status of the last run of the test instance. The values are from the Status custom list.

Typical values are: Not Completed, No Run, Passed, N/A, Failed.

varchar70  
 TC_TESTER_NAMEThe user name of the person responsible for running the test.varchar60  
 TC_EXEC_DATEThe date on which the test was last executed.datetime4  
 TC_EXEC_TIMEThe time at which the test was last executed.varchar10  
 TC_PLAN_SCHEDULING_DATEThe date on which the tester plans to next run the test.datetime4  
 TC_PLAN_SCHEDULING_TIMEThe time at which the tester plans to next run the test.varchar10  
 TC_HOST_NAMEThe name or IP address of the host server on which the test is planned to be executed.varchar50  
 TC_EPARAMSThe application-dependant configuration string created by the testing tool.varchar16  
 TC_ATTACHMENTA value of Y indicates that the test instance has at least one attachment.varchar1  
 TC_USER_01User-defined field.varchar40  
 TC_USER_02User-defined field.varchar40  
 TC_USER_03User-defined field.varchar40  
 TC_USER_04User-defined field.varchar40  
 TC_USER_05User-defined field.varchar40  
 TC_USER_06User-defined field.varchar40  
 TC_USER_07User-defined field.varchar40  
 TC_USER_08User-defined field.varchar40  
 TC_USER_09User-defined field.varchar40  
 TC_USER_10User-defined field.varchar40  
 TC_USER_11User-defined field.varchar40  
 TC_USER_12User-defined field.varchar40  
 TC_TEST_VERSIONFor backward compatibility. This field may be removed in a future version.int4  
 TC_TESTCYCLE_VER_STAMPThe revision number of this record. Increments each time the record is updated.int4  
 TC_EXEC_EVENT_HANDLEThe actions to be executed in response to various test set execution events. This field is in a proprietary format.varchar16  
 TC_VTSThe time this record was last updated according to the database server clock.varchar20  
 TC_TEST_INSTANCEThe number of this test instance inside the cycle. This field enables several test instances with the same TC_TEST_ID to reside within the same test set.int4   
 TC_USER_13User-defined field.varchar40  
 TC_USER_14User-defined field. User-defined field.varchar40  
 TC_USER_15User-defined field.varchar40  
 TC_USER_16User-defined field.varchar40  
 TC_USER_17User-defined field.varchar40  
 TC_USER_18User-defined field.varchar40  
 TC_USER_19User-defined field.varchar40  
 TC_USER_20User-defined field.varchar40  
 TC_USER_21User-defined field.varchar40  
 TC_USER_22User-defined field.varchar40  
 TC_USER_23User-defined field.varchar40  
 TC_USER_24User-defined field.varchar40  
 TC_OS_CONFIGFor future use.varchar40  
 TC_ACTUAL_TESTERThe user who last executed this test instance.varchar60  
 TC_DATA_OBJAn XML string containing parameter values for Business Process Test iterations.varchar16  
 TC_ITERATIONSContains information about the BPT test iterations that will be performed when executing this test. The format is: <total defined iterations>;<first iteration>;<last iteration>. If all defined iterations are to be run, the field may be empty.varchar255  
 TC_ASSIGN_RCYCThe RELEASE_CYCLES.RCYC_ID of the release cycle with which the test instance is associated.int4  
 TC_PINNED_BASELINEThe Baselines.BL_ID of the baseline to which this test instance is pinned.int4  
 TC_SUBTYPE_IDThe type of the test that was run.varchar100  
 TC_IS_DYNAMIC

For internal use by HP.

varchar1  
 TC_ENVIRONMENTThe ID of the td.ENVIRONMENTS Tableint4  
Indexes
IndexDescriptionPrimaryUnique
TC_ASSIGN_RCYC_IDX   
TC_PRIMARYKEY 
TC_STATUS_LWR_IDX   
TC_TEST_CONFIG_ID_IDX   
TC_TEST_ID_IDX   
TC_TESTCYCLE_CVR_IDX   
TC_TESTCYCLE_IDX  
TC_TESTER_NAME_LWR_IDX   
TC_VTS_IDX  
Triggers
TriggerDescription
AUTR_363696399_TESTCYCL 
Objects that depend on td.TESTCYCL
 Database ObjectObject TypeDescriptionDep Level
AUTR_363696399_TESTCYCL triggerAUTR_363696399_TESTCYCLTrigger 1
td.V_TESTSET_REQ_COVER viewtd.V_TESTSET_REQ_COVERView 1
Objects that td.TESTCYCL depends on
 Database ObjectObject TypeDescriptionDep Level
td.AUDIT_LOG tabletd.AUDIT_LOGTableEvents on which history is recorded.1
td.AUDIT_PROPERTIES tabletd.AUDIT_PROPERTIESTableDetails of the changes recorded in the AUDIT_LOG table.1
td.BASELINES tabletd.BASELINESTableBaseline records.1
td.ENVIRONMENTS tabletd.ENVIRONMENTSTableTesting environments.1
td.RELEASE_CYCLES tabletd.RELEASE_CYCLESTableDetails of cycles. A release can contain a number of cycles.1
See Also

Related Objects

td Schema
Project Data Tables Database