original-software-i400quality-ibmi-registered-partner-logo

Unit Testing for IBM i, IBM iSeries, AS/400 Testing

i400Quality-TestBench-testing-for-developers-image-01

Unit Testing Overview

Discover at the database level and beyond what really happens during the course of a test.

Generally, at least 60% of an IBM i application is made up of ‘batch’ processes; processes without a User Interface. Information enters and leaves the system as messages on data queues and MQ Queues, as well as through a User Interface. This makes a large portion of the application a ‘black box’. As a developer you can resort to using debug techniques to see what is going on, but these are slow to use and laborious to set-up.

What you really need is a test-harness that will enable you to test components in isolation and provide diagnostic feedback as to what those components are doing; passing and receiving parameter values, reading from and writing to a queue, updating data in the database as well as triggering down-stream processes, and knowing what those triggered processes are doing.

Definition

Execution

Results

TestBench IBM i Modules

Solutions to cover every aspect of test data management

Data Extraction

Stop copying the entire live database and hone in on the data you really need. Select or sample data with full referential integrity preserved.

Data Masking

Simply decide which fields need to be protected and use a variety of obfuscation methods to protect your data.

Data Validation

Track every insert, update and delete including intervening data states. Create rules so that data failures are flagged to you automatically.

Data Reset

Avoid the painful save/restores and stop attempting to explain bad test results based on poor initial data.

File and Report Compare

Comparing outputs is a well proven method to verify your test results but it can be laborious and prone to error.This unique solution can save hours. ​

Unit Testing

Get under the covers and analyse at a program/module level what happens in the database, APIs, parameters, messages and beyond.

Data Extraction

Stop copying the entire live database and hone in on the data you really need. Select or sample data with full referential integrity preserved.

Data Masking

Simply decide which fields need to be protected and use a variety of obfuscation methods to protect your data.

Data Validation

Track every insert, update and delete including intervening data states. Create rules so that data failures are flagged to you automatically.

Data Reset

Avoid the painful save/restores and stop attempting to explain bad test results based on poor initial data.

File and Report Compare

Comparing outputs is a well proven method to verify your test results but it can be laborious and prone to error.This unique solution can save hours. ​

Unit Testing

Get under the covers and analyse at a program/module level what happens in the database, APIs, parameters, messages and beyond.

i400Quality-TestBench-test-data-management-image-01

Test Data Management

Best Practice Guide