Mainframe Manual Testing

Mainframe Testing is same as a  client-server applications testing.As in manual testing the mainframe testing also follows the model in which the testing involves after the development is done
In Manual Testing the tester will be provided with the application along with the JCLS.
The tester along with the test cases prepared on the basis of the business requirement specification.
The tester prepares the test data to satisfy the business requirement and execute the COBOL code with the provided JCL.
If the actual result matches with the expected result mentioned in Test case then it is pass else it is failed. For failed one, the defect is logged and after the defect is fixed, it is again tested and the cycle goes until It achieves the expected result.
 

Mainframe Automation Testing

In Automated Testing  activities are executed in following phases by adapting well defined process  that will suits the  requirement of test automation.

• CAPTURE THE CLIENT REQUIREMENT
• ANALYZING THE REQUIREMENT
• TEST PLAN
• DESIGN
• SCRIPTING
• TESTING
• TEST CLOSURE

Audit and reviews were conducted in every phase to check that the quality is delivered through automation scripts.
CAPTURE THE CLIENT REQUIREMENT:
This phase is to understand the requirement of the client like understanding of all the   transaction.
i.e. customized transactions that the client wants.
ANALYZING THE REQUIREMENT:
This phase is to analyze the client requirement like testing priorities and focus.The   main focus is on Identifying the testable requirement.
TEST PLAN
This phase is a Test strategy phase where senior QA managers are involved in it to   determine the cost and effort estimates of  a project & finalize it.
DESIGN
This phase is the detailed analysis of the scenarios that needs to be automated. When   this phase is completed the design document that defines as high level design of the   script is created.
SCRIPTING:
In this phase the automation scripts are being developed based on the record   of the script design developed .The script is executed and tested in the   development environment.
TESTING:
Automation scripts were tested on the customer centric environment or at the   production environment. To check that all the defects or bugs are being   identified and resolved before the final shipment to customer.
TEST CLOSURE:
Test Team will meet and discuss and formulate the artifact based on the   learning from the current test cycle so as to identify the strategies to be used   in future. Hence a Test closure report is prepared with a test metrics.
 

Mainframe Emulators

• Emulators means making a copy of functioning of one system using another system

• Another system behaves as of the first system or merely it can be said as mirror image of  previous system

• IBM 3270 is a terminal made by IBM since 1972
• These are also known as display device are used to communicate to communicate to IBM mainframes.

Below is the list of tools which will be used for Mainframe Testing

• Test Director
• QTP (Quick Test Professional)
• Claim Repository
• Foundation Testing Tool (FTT)
• TN3270 Plus
• Hiperstation
• Load Runner

Mainframe Testing Scope

• There is a huge demand for Mainframe Testing specifically from the banking, Insurance, Retail etc.
• Because of their ability to handle huge volume of data with Reliability, serviceability, availability.
• Mainframe Testing is used in business critical application and it requires specific skill set Has a broad scope.
• Mainframe Testing can be seen as mainframe SOA testing, Mainframe batch testing, Mainframe Test Data Management, Mainframe online   Testing and in various other forms.
• With the new generation of SOA, Cloud mainframe application are changing continuously so as to meet the business demand.
• Mainframe Automation has helped to reduce the time and thus opening more markets.

 

Types of Mainframe Testing

Batch testing
Batch testing is nothing but executing a JCL for a particular affected program with an input file contains our test data and getting the expected in Output file
Database testing
Database testing is nothing but we are executing a program with an input file and that file uploads the data to the tables in database.
In other way executing some query in the COBOL program and extracting the expected output form the tables and writing in an output PS file
Online testing
Online testing is nothing but entering values through online screen and checking through the database whether the values given in the online screens are entered in the appropriate table and in the correct fields.
Batch + Online + Database testing:
Executing a JCL for a particular affected program with an input PS file   contains our test data and getting the expected in Output file as well as   uploading the output to database.
While retrieving the data through the online screen, the data which   uploads though batch process Input PS file should be retrieved.