Browse Prior Art Database

Object Relational Code Test Coverage Methodology

IP.com Disclosure Number: IPCOM000228175D
Publication Date: 2013-Jun-10
Document File: 4 page(s) / 82K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method to simplify and improve the efficiency of testing within a systems complex used as a platform for a mainframe server operating system. The invented approach creates an object and then populates that object from the lexicon within the desired operating system and with available commands and keywords within the operating system product family. The outcome provides the programmer with a holistic view of how the workload is executing across the systems complex as well as on remote sites.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 4

Object Relational Code Test Coverage Methodology

Testing with a systems complex as a platform for a mainframe server operating system is becoming increasingly complicated as customer environments become more sophisticated and code bases expand. The relational model used today to diagnose system coverage is embedded within the system stack or native to that Original Equipment Manufacturer (OEM) product. Recreating and mimicking customer environments is a daunting task within a hardware, software, and systems provider, and is sometimes unattainable because of the expansive nature of customer environments.

There are many ways to compute what is important to the programmer in a search. This can include code coverage specifically with keywords or dataset count combined with certain commands. Many times within a testing environment, the system is configured for particular testing and needs generalization to cover the vast number of permutations within a test infrastructure.

An additional solution is needed to relate the efficiency of test systems to each other across the systems complex, across products, and to other neighboring systems complexes. This would provide a view of code coverage that can help reproduce or recreate problems. Beyond invoking queries about certain relations within the system, such as hardware dependencies or flash copy relations, an objective method is needed quantify the code coverage within the system. Code coverage can tell the utilization within the product, for instance, and the amount of invocations within the systems complex. A view such as this can give the tester a holistic view of how the product is being used. The desirable features are:


• For the relational object to be populated at the functions compile time and command keywords presented to the user


• For the object to be filled with user information as the job is executed throughout the complex


• For a snapshot of the data to be collected after a time stamp for completing the object


• For the objects, after creation, to be stored within a data structure and used to relate how different Logical Partitions (LPARs) within the systems complex are invoking operating system functions

The invention is a method for creating an object and then populating that object from the lexicon within the desired operating system and with available commands and keywords within the operating system product family.

When the user executes a job(s) within the systems complex, this object (or many objects) is created by storing, in an encapsulated way, information about: how many times a function is exposed within a test space, the number of functions, and the data that is present w...