Unlike typical industry standard testing tools, Testac is a domain specific productivity tool. A functional framework of the related business segment is embedded in the tool. Most of the common product profiles (and related attributes and rules) and transaction profiles (and related rules) for a specific domain are embedded in the tool. The tool also permits creation of new rules and attributes.

In carrying out test design for a roll-out, the testing team needs to only customize the functional framework in the tool to the specific context and define boundaries of testing in order to generate a design pack.

Questionnaire-led check-lists enable easy capture of all product information, rules, attributes and transactions. Even in the absence of good documentation, the tool ensures that the testing teams ask all the right questions during the test design phase.

Boundary Definition

A questionnaire-led interaction process, where information is collected from business users and specification documents helps in defining the functional boundary of tests. Information is captured on business segments, products offered, transactions / lifecycle events etc.

Matrix definition

Provides for review and definition of various rules relating to Products or Transactions and results in generation of the minimum set of Test Conditions for each Product and Transaction. These are termed as ‘Product Matrix’ and ‘Transaction Matrix’

Scenario generation

Generates end-to-end business scenarios (both positive and negative) by stitching together the product and transaction level conditions obtained in the Product and Transaction Matrix. This is based on

• defined process flows,

• rules related to linking of transactions,

• fees and charges related structures and

• feeds from Support Components (for example loan, deposit and interest schedules)

An application mapping exercise at this stage generates a ‘Workflow Matrix’ that fits the scenarios to application screens/steps and simplifies execution of the same

Run plan generation

Converts the Scenarios into a Run Plan indicating Logical and Physical dates on which various set-up and transactions are to be put through along with the associated batch processes to be executed and expected results to be verified. This takes into consideration the following inputs

• Calendar definition,

• Batch Processing rules,

• Date feeds from Support Components (Loan, Deposit and Interest Schedules)

Analytics

Provides drilldown analytics relating to rules, conditions and scenarios to enable a review of results and identify gaps if any and focus on possible areas that may require additional tests to be designed.

A Functional Decomposition maps the conditions / scenarios to attribute values and rules to ensure comprehensive coverage is achieved