System Engineering Automated Testing in T24

System Engineering Automated Testing (SEAT) is a framework by Temenos designed to automate the testing process, concentrating on both the technical and functional components of the T24 core banking system. It includes the creation and management of a repository of test cases (SEAT Scripts) that can be integrated into T24 builds to assess the system's performance and confirm that it fulfills defined requirements. SEAT assists in optimizing quality assurance by facilitating regression, functional, and integration testing for T24 features and services. SEAT is used to input transactions in T24 and launch enquiries.

CREATING SCRIPTS: Records and transactions are generated in T24 through the use of SEAT.SCRIPTS (abbreviated as SST). The script ID consists of 21 characters divided into two segments by a hyphen. The first segment represents the test case ID, while the second segment (after the hyphen) is referred to as the sequence number.

DESCRIPTION: A descriptive and meaningful summary of the test case COMPANY CODE: Which COMPANY is this record associated with? T24 can accommodate multiple company setups, and this field indicates the specific company for the transaction's creation.

SCRIPT.STATUS: This must be active if the script is to be executed. Scripts can be marked as Obsolete or put on hold if necessary. SCRIPT.SOURCE: The reason behind the creation of this script should be provided. Include the Defect ID or SI related to this script’s creation.

SELECT.ROUTINE: To link a sub-routine that adjusts a TXN ID of SEAT SCRIPTS, a routine must exist in PGM.FILE categorized as ‘S’. This routine will be invoked using either the SCRIPT ID specified in the TXN ID field, a Transaction reference, or without any TXN ID. It will read the Original script ID and output the TRANSACTION ID from the relevant Script record. BASE.RELEASE: Identify which release of T24 the execution of this script is intended for; this could be R17, 201704. A script may also be run across multiple releases a feature that will be covered in the discussion of SEAT.SCRIPT.ACTIVITY.

PRODUCT.GROUP: What team is responsible for this script? A selection can be made from the provided dropdown options. APPLICATION: Indicate the T24 application where the transaction should be created.

STATIC SETUP: Various configurations can exist in T24, such as single company, multi-company, trade dated, value dated, etc. Select the appropriate option from the dropdown. Note: Choosing this field is mandatory if updates to results are necessary. SE product in T24 consists of several applications. We will discuss six major SEAT applications

SEAT.SCRIPTS: Utilized to initiate transactions in T24, such as creating a CUSTOMER or LD contract. Additionally, SEAT.SCRIPTS can be employed to perform inquiries in T24.

SEAT.RESULTS: To verify the transaction status. Was the record successfully established in T24? Was there an ERROR preventing the record from being created? Does the record hold the anticipated values across various fields

SEAT.SCRIPT.FIELD.VALUES: Is employed to indicate the field names (along with the multivalue and subvalue positions) and the expected contents within those fields.

SEAT.SCRIPT.RESULT.FILES: While establishing the field values, we only denote the field name and its expected content. How will SEAT identify which file and record to take into account for this verification? When should this verification occur? After the CUSTOMER creation? Following ACCOUNT creation? These points are clarified in the SEAT.SCRIPT.RESULT.FILES.

SEAT.SCRIPT.ACTIVITY: SSA encompasses details about all the scripts that comprise a test case. For instance, a test case might consist of four scripts.

SEAT.SCRIPT.FORMAT.OUTPUT: Used when we seek to validate the outcomes from an Enquiry.

Open the TAFJ shell: To run the script, we need to issue the command tRun tSS SEAT. TAFJ commands are run from the command line via tRun. tSS functions similarly to tSA and tSM. SEAT is a Record Id within an application named OFS.SOURCE. By utilizing the values provided in the script, an OFS message is created to process the transaction in T24. 

SEAT RESULTS:

Generate Error	Upload Status	Overall Result
No	Error	-1
No	Processed	0
Yes	Error	0
Yes	Processed	-1

If you are interested in our automated functional and technical testing for T24 using SEAT, please reach out to us. We provide a wide variety of testing support, including upgrade testing, migration testing, and load and performance testing.

Keep up the great work ! Happy Performance Engineering!

#AutomatedTesting #CoreBanking #T24Automation