Embed Size (px)
Citation preview
Automation Test In MainframeAutomation Regression Test Inside Mainframe16th November, 2016
Mainframe“Big Iron” other name of mainframe. Basically a computer system that can use for large organizations for critical applications, bulk data processing and big amount of calculation. International Banking systems, Insurance Company and many 0thers large Corporation use mainframe. From 1960 to now it is developing continusly by lots of Company.
Now a days mainframe can be run from a laptop and connect 2 computersDefine by their OS( IBM's z/OS, OS/390, MVS, VM, and VSE. ) not the size. Basically every mainframe should come with 4 features
* Reliable single-thread performance.*Maximum I/O connectivity.* Maximum I/O bandwidth.*Reliablity on their service and maintain.
Mainframes process roughly 30 billion business transactions per day, including most major credit card transactions and stock trades, and money transfers.
It is estimated that 80% of the world’s corporate data resides or originates on mainframes.
~70% of all enterprise transactions touch a System z
55% of all enterprise applications need the mainframe to complete transactions
91% of surveyed CEOs said that new customer-facing applications are accessing the mainframe
• The First movement start with IBM ASCC in 1944.• Contain thousand of vacuum tube. • Can solve a complex calculation in six second • Step much forward to RAM and Data calculation.
• UNIVAC in 1952 by Dr. J pesper and and Dr. W Mauchy. • 352 sq-ft and have 5400 vacuum tube. • It also predicted the 1952 Us election result between Eisenhowen And Stevenson that Eisenhowen will be president.
• CRAY-1 the first evulation in computing era(1976). • First vector computer with 8mb main memory• Can do million calculation in second. • 8 million dollar range with high tech cooling system with Freon.
Mainframe Today
z13 – built for todays mobile workload• Latest Z13 processor with
machine(2015).• Security• Scalability• 100 cyber Mondays each
day• Up to 10 TB of memory
Automation testing
In a simple word, A software that can test another software continuouslyAnd predict outcome of the software is basically call automation testing.
There is several 5 type and tools for Automation testing
Types:
1. Code Auditing 2. Coverage Monitor (Vital for glass-box testing)3. Functional Tests (can be replace black-box testing)4. Load Tests 5. Test Management
Cons• Script should be written by a scripter.
• Manual test case to be written first then automated.
• Require a testing platform.
• Not cost effective less than three test cycle .
Pros• Faster Test Cycle
• Able to identify more defects
• Excellent way to testing needs of agile development.
• Easy to focus at all sections.
• Higher product quality
Decision to Test
Tools acquistion
Testing Introduction
Process
Test Planning, Design,
Development
Execution and management of
Test
Test Review and Assesment.
ATLC
Automation in MainFrameAutomated Software testing has become a key player in Mainframe with continue development In agile software and processes whose target is “better software, faster.”
Mainframe Testing is similar to web based testing. The application (otherwise called job batch) is tested against the test cases developed using requirements..
o Performed on the deployed code by input data combination set into input file.o Testing software can run through emulator .o Tester should have idea how navignate CICS screen. Not that much coding experience or knowledge
need for testing.
Skill should have test in mainframe
COBOL DB2 JCL CICS Assembler VSAM ISPF/TPF
There is some tools available for mainframe testing .
* CA-Verify * IBM Rational Functional Tester *QTP (Quick Test Professional) *Claim Repository *TN3270 Plus
Some name(Attributes )
Virtual Storage: Actually using a disk storage as an extension of real storage.
Batch job: programme execute by sequence. Information providing through JCLKnown as background process
Time sharing(TSO): foreground processUsing system through terminal.
Spooling (Simultaneous Peripheral Operations Online.):Store output from program.Help to make efficient output device by using buffering advantages.
METHOD. step 1: Shakedown/Smoke TestingBasically Focus on code environment and error.
Step2:Sytem testing:
• Batch Testing : can be done by record data change done by batch job processing.• Online Testing: done on the front end of mainframe software.
• Database Testing : (IMS, IDMS, DB2, VSAM/ISAM, Sequential datasets, GDGs)testing their layout and the data storage.
Step 3: System Integration TestingThe primary purpose of this testing is to validate the functionality of the systems which are interacting with the system under test.
Step 4:
Regression Testing
Regression Testing is a common phase in any type of testing project. This testing in Mainframes ensures that batch jobs and the online screens which do not directly interact with the system under test (or do not come in the scope of requirements) are not affected by the current project release.In order to have effective regression testing, a particular set of test cases should be shortlisted depending on their complexity and a regression bed (Test cases repository) should be created. This set should be updated whenever there is a new functionality rolled out into the release
Modify programme +run
again
Execute and save(phase1)
Compare the both run
Check(soft/data)+exer the func.
Development progress()
Testing Planning() Create or change source.
Repeat session
Prepare Input/output files
Exit CA Verify
Enable CaverifyCA11
Log on(tpx)(A11VFY1)
Correct any error (library, Script)
Record the TEST
Save the Job
Create A JCL Run the Script
Demonstrate a Test with CA Verify
STep5: Performance Testing This testing is done to identify the bottlenecks in high hit areas like front end data, upgrading online databases and to project the scalability of the application.
Step 6 : Security TestingThis testing is done to evaluate how well the application is designed and developed to counter anti-security attacks.Two fold security testing should be done on the system – Mainframe security and Network security.The features which need to the tested areIntegrityConfidentialityAuthorizationAuthenticationAvailability
Commands used in Mainframe Testing1.SUBMIT – Submit a background job.2.CANCEL – Cancel background job.3.ALLOCATE – Allocate a dataset4.COPY – Copy a dataset5.RENAME – Rename data set6.DELETE – Delete Dataset7.JOB SCAN –To bind the JCL with the program, libraries, file, etc. without executing
Issues During Testing:Job Abends – For successful completion of the job, you should check the data, input file and the modules present at the specific location or not.
Output file empty–Though the job might run successfully , the output might not be as expected. So before passing any test case, the tester have to make sure that the output is cross verified. Only then proceed further.
Input file empty – In some applications, files will be received from the upstream processes. Before using the received file for testing current application, the data should be cross verified to avoid re-execution and rework.
Challenges Approach
Incomplete / Unclear Requirements Testers should be involved in the SDLC from the requirements phase onwards.
Data Setup/ Identification For data setup, homegrown tools can be used as per the need.
Job Setup Job setup tools should be used so as to overcome human errors made during setup.
Ad-hoc RequestThere may be situations when end to end testing needs to be supported due to a application issues.
Use of automation scripts, regression scripts, and skeleton scripts could help in reducing the time and effort overhead.
Challenges
Summary:
•Mainframe testing is like any other testing procedure starting from Requirement gathering, test design, test execution and result reporting.
•In order to test the application effectively, the tester should participate in design meetings scheduled by development and business teams.
•It is mandatory for the tester to get accustomed to various mainframe test function. Like screen navigation, file and PDS creation, saving test results, etc. before the test cycle begins.
•Mainframe application testing is a time taking process. A clear test schedule should be followed for test design, data setup and execution.
•Batch testing and Online testing should be done effectively without missing any functionality mentioned on Requirement document, and no test case should be spared.
ReferencesIBM knowledge Centre:https: https://www.ibm.com/support/knowledgecenter
CA DocOps: https://docops.ca.com/home
Rosalind Radcliffe video about mainframeLink: https://www.youtube.com/watch?v=7pSGb5DGI1w
Wikipedia
Photoes: Open wiki license photo from(WikiMedia).
