Primary ATF Tables

The following are the major tables associated with the ATF module:

  • sys_atf_step --> Test Step - This table contains the definition of one specific test step which is part of a test.
  • sys_atf_step_env --> Test Step Environment - This table contains information regarding the configuration of the actual enivonment running the test steps on the instance and should never be transferred to the target clone instance.
  • sys_atf_schedule_run --> Scheduled Suite Run - This table contain the specific information associated with an individual scheduled run of a test suite.
  • sys_atf_test_result_step --> Step Result - This record contains the result information associated with the specific run of an individual test.
  • sys_atf_test_template --> Table which contain base templates which can be used as the starting point for making certain types of tests.
  • sys_atf_test --> This is the table that contains the actual test records on the instance, out-of-box sample tests as well as custom user created tests.
  • sys_atf_step_config_category --> Test Step Config Category - This table contains the various Step Type categories such as Server, Form, Rest, and Service Catalog.  These should generally not need to be retained during a clone unless, in the rare event, custom step configuration categories have been created.
  • sys_atf_variable --> This is the base class containing common fields used by the atf_input_variable and the atf_output variable extended classes.
  • sys_atf_test_result_item --> Test Result Item - This table contains the individual list lines that detail the specific results from one run of an ATF test.
  • sys_atf_test_suite_result --> This table contains the result sets for one specific run of one test Suite.
  • sys_atf_test_suite_test --> Test Suite Test - This table contains the associations of an ATF Test Suite to the individual tests which form that suite.
  • sys_atf_test_suite --> Test Suite - This table contains the details for a specific test suite as stored on the instance.
  • atf_output_variable --> Output Variables - This table contains the specific output variables as associated to a specific test case.
  • sys_atf_step_config --> Test Step Config - This table stores the specific configurable test types which an ATF user can add to a new test case.  These are generally read-only records and should not need to be transferred to the target clone instance.
  • sys_atf_transaction_mtom --> Step Result Transaction - This table contains the direct relationship amongst a specific test run (sys_atf_test_result_step) and a transaction (syslog_transaction) that had occurred during that run.  If this table is retained the syslog_transaction should also be retained.
  • sys_atf_agent --> Test Runner - This record type contains a current list of Test Runners that are on this instance.  These test runners are temporary and should generally not be retained on an instance during a clone.
  • sys_atf_schedule --> Suite Schedule - This table containing all the configured schedules for running test suites on the instance.
  • atf_input_variable --> Input Variables - This table contains records corresponding to specific Input variables as associated to a specific ATF test.
  • sys_atf_remembered_values --> Remembered Value - This table contains the values passed from one test step to another as assigned to a variable.  The records in this table are temporary and will normally only remain in the table as long as the test the variable is associated to is running.  This table should never need to be retained during a clone operation.
  • sys_atf_test_result --> Test Results - This table contains the specific individual test result as associated to one run of a specific test.
  • sys_atf_whitelist --> WhiteListed Client Error - This table contains a list of specific client side errors that the system should bypass and ignore if encountered when running a test.


Retaining ATF tables in instance clones

It is common, when cloning over a sub-production development instance, that an administrator may want to retain objects associated with the Automated Test Framework. However, ATF tables are not designed to be transferred to the target instance using the Data Preserver, but only through Update Sets.

Previous Test Results

In a new out-of-box instance the tables listed below are the main ones used by the ATF to store the results and related records from an ATF Test or Test Suite run:

  • sys_atf_test_result_item
  • sys_atf_test_result_step
  • sys_atf_test_result
  • sys_atf_test_suite_result

    Out-of-box included ATF Data Preservers

The individual transaction results from individual test runs are generally not required to be transferred to the target instance. However, if the administrator decides to transfer them,  the following two additional tables should also be added in the update set for their dependencies: 

  • sys_atf_transaction_mtom
  • syslog_transaction

The syslog_transaction table is actually not specific to the ATF, so it will also contain data that may not be needed.


ATF Tests and Test Suites


  • sys_atf_test
  • sys_atf_step
  • atf_input_variable 
  • atf_output_variable
  • sys_atf_variable

If the aft_input_variable, atf_output_variable, and sys_atf_variable records are not transferred, after the clone users may find test steps missing specific configurations that were previously there before the instance clone.

ATF Test Schema

ATF Test Suite Variable Schema



  • sys_atf_test_suite 
  • sys_atf_test_suite_test

It is possible to use the individual ATF test functionality without using the grouping of these tests into Test Suites. If the test suite functionality is not being used, the tables described in this section do not need to be included in the transfer update set.

 ATF Test Suite Schema


ATF Test Schedules:

  • sys_atf_schedule_run
  • sys_atf_schedule 

If ATF schedules are also being used on the instance, the following additional tables should also be included in the update set.

Note that ATF Schedules are designed to be used with Test Suites, thus, if schedules are in use, this also indicates that Test Suites are also in use on the instance.

ATF Test Suite Schedule Schema 

Other Table Types:

The sys_atf_test_template table should be included in the update set if test templates are in use on the instance. A test template is basically an outline which can be used as a starting point for creating new ATF tests of a specific type. If these templates are not used, there is no need to include the table in the update set, as the template table will otherwise be empty.

Similarly, if the ATF test users or administrators have created any custom records indicating specific Client Errors that should ignored during a test, the sys_atf_whitelist table should also be transferred.

These tables are part of the core platform or used by the system for temporary or short-term storage of data during test runs and should never be transferred:

  • sys_atf_step_env
  • sys_atf_step_config_category
  • sys_atf_step_config
  • sys_atf_agent
  • sys_atf_remembered_values 


Additional Information

Move automated tests from one instance to another


Article Information

Last Updated:2019-05-21 11:57:50