Browse Prior Art Database

Method for user interface tokenisation in multilingual environments - applicability to thin client systems and user interface automation systems

IP.com Disclosure Number: IPCOM000032751D
Original Publication Date: 2004-Nov-11
Included in the Prior Art Database: 2004-Nov-11
Document File: 3 page(s) / 68K

Publishing Venue

IBM

Abstract

System and Method for User Interface Tokenisation

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

Page 1 of 3

Method for user interface tokenisation in multilingual environments - applicability to thin client systems and user interface automation systems

Abstract

The application of automation in a language neutral way is a effort which has gained recognition over the recent years. Many solutions providers that offer automation solutions now realise that in large corporations a solution whereby automation can be written and executed in a language neutral way is useful, as testing of the localized/globalized/translated applications now means a large percentage of the overall testing effort. To date script writers have concentrated their efforts in providing additional functionality to the script writer. This basically offers the script writer additional intelligence to develop specialised automation in a way where they can build an integrated language solution (e.g. Segue provides a solution where one can build independent language streams of an automation script for application to a system built in that language). To date none of these efforts have concentrated on a language neutral application of automation.

    The rewards associated with providing a solution to the application of language neutral automation are evident for the script writer - in that they can write automation in a way that allows it to be applied to all translated variants of the application unchanged. The technical advantage to script writer is that they can develop solutions to the application of automation in a generic way.

System and Method for User Interface Tokenisation

    This article promotes the idea of user interface automation running in a language neutral way. User interface automation involves the development of technical test scripts which will execute and which will allow an application to be navigated and tested in an automated way - i.e. with no user intervention. If the automation scripts are well written then errors/bugs will be automatically recorded so that an engineer can acknowledge and address these bugs when the automation scripts have run to completion (or during execution). Once the bugs are fixed it is a common practice to execute the automation scripts again, thereby proving that the application being tested is bug free.

    Several software vendors write automation so as to 1) significantly speed up the software testing process, 2) allow automation to run when engineers are away from the office (e.g. at night), 3) develop test cases which are complete and comprehensive. Automation is therefore a useful tool/methodology for reducing quality engineering and testing costs. One of the main problems/drawbacks with conventional automation methodologies is that they need to be heavily modified so as to execute on translated versions of the application (and it is common knowledge that testing on translated versions of the application accounts for over 80% of a Software Company's World Wide testing effort). For example, the automation script might have a comma...