Programming Portal: Script Environment in Software Testing

The basic idea of setting the Test Bed is that the Test Suite must be potable and can readily be ran in any environment given the initial conditions. For this to happen, the automation tool supports a lot of functions to evolve a generic methodology where we can wrap up the entire built-ins to run before the Test Suite start executing the Script. In other word the fashion of organizing the Test Scripts remain in the developer’s mind to harbinger the issues and hurdles that can be avoided with little or less of programming.

Common Functions that get into Initialization Script are

1. Usage of built-in commands to keep the test path dynamically loaded. Options to rule out the possibility of Test Path Definitions

2. Close all the object files and data files in the Initialization Script

3. Connection to the database should be done in the Inits Script

4. Always Unload and Load the Object library, and it should be done only in Inits Script.

5. Define all the “public” Variables in the Inits Script

6. Establish the db connections in the Inits Test Script

Test Scripts Elements:

Prior to the development of Test Scripts the fashion of arranging the Test Scripts needs a proper planning. Lets look at few inputs on arranging the Test ware.

Test Ware	Test Repository
Test Suite	Should contain Sub Folders, Exception Handlers, Global Object files, Set Data file, Driver Scripts, Initialization & Termination scripts
Driver Script	Object Checks, Bit Map Checks, Text Check, Web Check, User defined Functions, Global test Report Folder
Driven Script	GUI/Bit/Text Check, External Libraries, I/O Handlers

5.1

Programming Portal

Top Tabs

Script Environment in Software Testing

Test Scripts Elements:

No comments:

Post a Comment