Scribd
Upload
403 views

09 Testing in Ingenium

This document provides tips for online and batch testing in Ingenium. For online testing, it recommends verifying screen titles, button bars, dropdown values, error messages, and data saving. It also provides tips for custom HTML, tab order, and testing boundary conditions. For batch testing, it recommends checking sysout/OCF, initialization, checkpoint restart, setup tables, control cards, and JCL standards like symbolic parameters and correct database targeting.

Uploaded by

Nagarajan Venkatesan
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
403 views

09 Testing in Ingenium

This document provides tips for online and batch testing in Ingenium. For online testing, it recommends verifying screen titles, button bars, dropdown values, error messages, and data saving. It also provides tips for custom HTML, tab order, and testing boundary conditions. For batch testing, it recommends checking sysout/OCF, initialization, checkpoint restart, setup tables, control cards, and JCL standards like symbolic parameters and correct database targeting.

Uploaded by

Nagarajan Venkatesan
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 10

Testing in Ingenium

Topics Covered

Online Testing Tips

Batch Testing Tips

Online Testing Tips


Placement of Cursor in any Screen.
Focus Field : Focus should always be on the first editable
field on the page. Otherwise, users need to hit tab many
times just to get the correct field.
When a page appears on the screen then the header part
of HTML should be at the top, even if the first editable
field is far below.

Screen Title
Screen title should be same as the PDS/Screen Shot given.
We should verify these for spelling mistakes.
Each screen should be checked for its title separately.
While moving from one screen to other we should keep
an eye out for any unexpected changes to the titles.
A common mistake here is that in the flow file we
forget to change the title to previous when going back
to the previous screen.

Online Testing Tips


Button Bar
Button Bars in any screen should be same as in the
requirement. While checking the buttons we must make
sure that
They lead to the correct screens.
Tool Tips or Alternate Text Property of the Button is
same as the text appearing on the button.
A common mistake is that we forget to change the
button bar when going to a previous screen.

Customisation
HTML customisation should be as close to the standards as
possible.
Use of non-standard tags should be kept minimal;
only to support exceptional situations.
Spelling check should be made on the HTML.

Online Testing Tips


Drop Downs EDIT, DMAV / DMAD
Verify the Code and Description match exactly to the
requirements
To verify that only correct code/description values are
populated into the list.
Verify that there are not spelling mistakes in the
Description

Error Messages
Check in every business process that error messages do
not have spelling mistakes, punctuation and grammatical
errors.

Online Testing Tips


Other Points
Spelling of Menu Items to be verified for Correctness.
While using Date Fields we should restrict the size of the
field to 10 using Max Length property.
The Maximum of other fields also needs to be checked so
that only the allowed number of characters are entered
into this field. We can use Jscript to automatically
truncate the Var Char Fields.
The Tab Order of fields is very important. The tab order
in any screen should be as given below.
Left to Right
Top to Bottom
Verify that the Data for any Create / Update business
process is truly getting saved to the Database.

Online Testing Tips


Other Points contd
Test for Boundary value conditions.
Header Information in any screen. This is usually the
non-editable data on any screen. While testing make
sure that
Header values are populated correctly
When moving across screens or flows the header data
should not get changed
In the complex flow, loop through the flow and keep
going and coming out of the flow. This will help is
catching the initialization problems if any and any other
flow related issues.

Batch Testing Tips


Sysout / OCF
OCF is the Output Control File. We need to have proper
information about the record, especially the key fields
like Policy ID, Client ID.
In the case of a file processing being done we need to
have the count of the record that is being processed.

Initialization
We need to initialize all the variables at the correct
position in the program.

Batch Testing Tips


Checkpoint Restart
The required working storage variables and counters
that are needed to restart the program in the event of an
Abend need to stored in the TCKPT area.
The skipping of records in the event of restart needs to
be carefully tested to make sure that we start again at
the correct position from where it was previously
COMMITted to DB.

Set up tables and Control Cards


Control Cards should be valid and check for this as
otherwise Ingenium Job will be forced to Abend.
The Batch set up tables like
TBPGA, TTEXT, TCKPT needs to have entries.

Batch Testing Tips


JCL Standards
Building of datasets using symbolic parameters should
be pointing to Production in the Catalogued procedure.
Check to make sure that the RUNP points to the correct
Database. (which has the Batch Program and Batch Plan
Name)

You might also like