Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Method and System for Automating the Manual Testing for Legacy or Web Services based Airline Reservation Systems

IP.com Disclosure Number: IPCOM000202413D
Publication Date: 2010-Dec-15
Document File: 5 page(s) / 103K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method and system for automating the manual testing for legacy or web services based airline reservation systems is disclosed.

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

Page 01 of 5

Method and System for Automating the Manual Testing for Legacy or Web Services based Airline Reservation Systems

Disclosed is a method and system for automating the manual testing for legacy or web services based airline reservation systems. An automated tool is developed using J2EE* and web services technology with data repositories and configuration parameters stored in simple spreadsheets. As the automated tool is Java* based, it can be easily integrated with legacy or web services based airline reservation systems. Thus, the automated tool automates existing manual regression testing process for both legacy based reservation systems as well as web services based reservation system without making any kinds of changes in the source code. In order to connect to mainframe based reservation system, a vendor specific personal communication system or other communication systems available in the market may be utilized.

The automated tool provides flexibility to business analysts so that the analysts can customize each test cycle either at a scenario level or at a test case level. In a scenario, the automated tool also allows the flexibility to setup the test environment prior to execution of test cases. The number as well as order of functional scenarios and test cases can be configured using input repository data such as, the spreadsheets. As the input data repository corresponding to testing configuration is maintained in spreadsheets, any user can understand and maintain it easily. The functional scenarios and test cases can be configured without making any kind of changes in the code.

Further, the scenarios can be customized in accordance with the business processes as the automated tool is functionality driven and can be automated per business needs. As the tool does not use any script and provides data driven execution, a new scenario can be accommodated with a mere change in source configuration. Additionally, the analysts may also define time of execution and analyze test cycle results in a graphical format using the automated tool.

For example, consider a scenario where a web based or a stand-alone user interface is provided to capture user input. An example of the stand-alone user interface is a swing** based user interface. On selecting a Terminal (host) or Web (services), respective scenarios are populated as specified in source data. After the scenarios are populated, the user can select some or all the scenario, and provide the valid credentials for accessing the respective system. Thereafter, the user can specify a time for executing the scenarios. For example, a prompt may be provided to the user asking the user whether the user wishes to execute the scenarios now or at a later time. After the user submits the specified time, the request is forwarded to a controller. The controller performs form validation and thereafter delegates the request to JAVA process for execution. For example, the controller may delegate the...