How do you load GUI map

1.What is the disadvantage of loading the GUI maps through start up scripts?

We can load a GUI Map by using the GUI_load command.
Syntax: GUI_load();

• If we are using a single GUI Map file for the entire AUT then the memory used by the GUI Map may be much high.

• If there is any change in the object being learned then WinRunner will not be able to recognize the object, as it is not in the GUI Map file loaded in the memory. So we will have to learn the object again and update the GUI File and reload it.

2.How do you unload the GUI map? What actually happens when you load GUI map?

We can use GUI_close to unload a specific GUI Map file or else we call use GUI_close_all command to unload all the GUI Map files loaded in the memory.
Syntax: GUI_close(); or GUI_close_all;

When we load a GUI Map file, the information about the windows and the objects with their logical names and physical description are loaded into memory. So when the WinRunner executes a script on a particular window, it can identify the objects using this information loaded in the memory.


3.What is the purpose of the temp GUI map file? What is the extension of GUI map file?

While recording a script, WinRunner learns objects and windows by itself. This is actually stored into the temporary GUI Map file. We can specify whether we have to load this temporary GUI Map file should be loaded each time in the General Options.
The extension for a GUI Map file is “.gui”.

Purpose of set_window command

Set_Window command sets the focus to the specified window. We use this command to set the focus to the required window before executing tests on a particular window.

Syntax: set_window (, time);
The logical name is the logical name of the window and time is the time the execution has to wait till it gets the given window into focus.

When you create GUI map do you record all the objects of specific objects?

If we are learning a window then WinRunner automatically learns all the objects in the window else we will we identifying those object, which are to be learned in a window, since we will be working with only those objects while creating scripts.

View the contents of the GUI map

GUI Map editor displays the content of a GUI Map. We can invoke GUI Map Editor from the Tools Menu in WinRunner. The GUI Map Editor displays the various GUI Map files created and the windows and objects learned in to them with their logical name and physical description.

Different between GUI map and GUI map files

1) The GUI map is actually the sum of one or more GUI map files. There are two modes for organizing GUI map files.

• Global GUI Map file: a single GUI Map file for the entire application
• GUI Map File per Test: WinRunner automatically creates a GUI Map file for each test created.

2) GUI Map file is a file which contains the windows and the objects learned by the WinRunner with its logical name and their physical description.

WinRunner fails to identify an object on the GUI

WinRunner fails to identify an object in a GUI due to various reasons.

• The object is not a standard windows object.
• If the browser used is not compatible with the WinRunner version, GUI Map Editor will not be able to learn any of the objects displayed in the browser window.

Logical name of the object: An object’s logical name is determined by its class. In most cases, the logical name is the label that appears on an object.

If the object does not have a name then what will be the logical name?

If the object does not have a name then the logical name could be the attached text.

Purpose of loading WinRunner Add-Ins

Add-Ins are used in WinRunner to load functions specific to the particular add-in to the memory. While creating a script only those functions in the add-in selected will be listed in the function generator and while executing the script only those functions in the loaded add-in will be executed else WinRunner will give an error message saying it does not recognize the function. Add-Ins are used in WinRunner to load functions specific to the particular add-in to the memory. While creating a script only those functions in the add-in selected will be listed in the function generator and while executing the script only those functions in the loaded add-in will be executed else WinRunner will give an error message saying it does not recognize the function.

Integrated your automated scripts from Test Director

When you work with WinRunner, you can choose to save your tests directly to your Test Director database or while creating a test case in the Test Director we can specify whether the script in automated or manual. And if it is automated script then Test Director will build a skeleton for the script that can be later modified into one which could be used to test the AUT.

Use of Test Director Software

Test Director is Mercury Interactive software test management tool. It helps quality assurance personnel plan and organize the testing process. With Test Director you can create a database of manual and automated tests, build test cycles, run tests, and report and track defects. You can also create reports and graphs to help review the progress of planning tests, running tests, and tracking defects before a software release.

How do you analyze the results and report the defects?

Following each test run, WinRunner displays the results in a report. The report details all the major events that occurred during the run, such as checkpoints, error messages, system messages, or user messages. If mismatches are detected at checkpoints during the test run, you can view the expected results and the actual results from the Test Results window. If a test run fails due to a defect in the application being tested, you can report information about the defect directly from the Test Results window. This information is sent via e-mail to the quality assurance manager, who tracks the defect until it is fixed.

How do you run your test scripts?

We run tests in Verify mode to test your application. Each time WinRunner encounters a checkpoint in the test script, it compares the current data of the application being tested to the expected data captured earlier. If any mismatches are found, WinRunner captures them as actual results.

Debugging of the scripts

We can debug the script by executing the script in the debug mode. We can also debug script using the Step, Step Into, Step out functionalities provided by the WinRunner.

Created test Scripts

It contains the statement in Mercury Interactive Test Script Language (TSL). These statements appear as a test script in a test window. You can then enhance your recorded test script, either by typing in additional TSL functions and programming elements or by using Win Runner’s visual programming tool, the Function Generator.

WinRunner evaluates test Results

Following each test run, WinRunner displays the results in a report. The report details all the major events that occurred during the run, such as checkpoints, error messages, system messages, or user messages. If mismatches are detected at checkpoints during the test run, you can view the expected results and the actual results from the Test Results window.

WinRunner recognize objects

How Does WinRunner recognize objects on the Application?

WinRunner uses the GUI Map file to recognize objects on the application. When WinRunner runs a test, it uses the GUI map to locate objects. It reads an object’s description in the GUI map and then looks for an object with the same properties in the application being tested.

GUI Map In Winrunner

What is Contained in the GUI (Graphical User Interface) Map ?

WinRunner stores information it learns about a window or object in a GUI Map. When WinRunner runs a test, it uses the GUI map to locate objects. It reads an object’s description in the GUI map and then looks for an object with the same properties in the application being tested. Each of these objects in the GUI Map file will be having a logical name and a physical description.

There are 2 types of GUI Map files.

• Global GUI Map file: a single GUI Map file for the entire application

• GUI Map File per Test: WinRunner automatically creates a GUI Map file for each test created.

WinRunner Testing Process

WinRunner testing process involves six main stages:

• Create GUI Map File so that WinRunner can recognize the GUI objects in the application being tested

• Create test scripts by recording, programming, or a combination of both. While recording tests, insert checkpoints where you want to check the response of the application being tested.

• Debug Test: run tests in Debug mode to make sure they run smoothly

• Run Tests: run tests in Verify mode to test your application.

• View Results: determines the success or failure of the tests.

• Report Defects: If a test run fails due to a defect in the application being tested, you can report information about the defect directly from the Test Results window.

WinRunner

WinRunner is an automated functional GUI testing tool that allows a user to record and play back UI interactions as test scripts. The software implements a proprietary Test Script Language (TSL) that allows customization and parameterization of user input.

This product is a mature tool that has been around since approximately 1995. It interfaces with most of the leading development toolkits using the WindowsAPI and toolkit DLLs to interface with the “Application Under Test”.

WinRunner offers a recording feature that will watch the individual tester and generate a test script to simulate the same actions just performed. The script is displayed as a program which can be enhanced with checkpoints, logic and special coding/programming.

WinRunner also has integration with Excel spreadsheets for data driven testing and the ability to write data out in Excel format or in simple text files.

Here is the description from the Mercury “Features and Benefits” section of the WinRunner web page:

Significantly increase power and flexibility of tests without any programming: The Function Generator presents a quick and error-free way to design tests and enhance scripts without any programming knowledge. Testers can simply point at a GUI object, and WinRunner will examine it, determine its class and suggest an appropriate function to be used.

Use multiple verification types to ensure sound functionality: WinRunner provides checkpoints for text, GUI, bitmaps, URL links and the database, allowing testers to compare expected and actual outcomes and identify potential problems with numerous GUI objects and their functionality.

Verify data integrity in your back-end database: Built-in Database Verification confirms values stored in the database and ensures transaction accuracy and the data integrity of records that have been updated, deleted and added.

View, store and verify at a glance every attribute of tested objects: WinRunner's GUI Spy automatically identifies, records and displays the properties of standard GUI objects, ActiveX controls, as well as Java objects and methods. This ensures that every object in the user interface is recognized by the script and can be tested.

Maintain tests and build reusable scripts: The GUI map provides a centralized object repository, allowing testers to verify and modify any tested object. These changes are then automatically propagated to all appropriate scripts, eliminating the need to build new scripts each time the application is modified.

Test multiple environments with a single application: WinRunner supports more than 30 environments, including Web, Java, Visual Basic, etc. In addition, it provides targeted solutions for such leading ERP/CRM applications as SAP, Siebel, PeopleSoft and a number of others.

Simplify creation of test scripts: WinRunner'

How to use Bugzilla

1.What is Bugzilla?

Bugzilla is a powerful bug tracking system which can make the reporting of bugs and responses run smoothly with our view in making our products better and more accessble for a large number of users. Through the use of Bugzilla , users can report their bugs , and receive feedback from a developer or an engineer. Bugzilla is not only for the real problem , but also for new functionality or product updates.

2.Before you use Bugzilla:


This Bugzilla handlesa all packages on TurboLinux's FTP site (ftp.turbolinux.com) except followings.
packages with version being before their Beta.
packages of commercial products
packages included in comanion CDs

Reported bugs will be closed when bug is fixed. However there are some cases that will be closed with the following reason.

1)Fail to make the bug duplicated:Bugs which cannot be duplicated will be closed after the period of 30 days.
2)Lose a contact with bug reporters:Lost contact with reporters could make invesitigation impossible. The result of CLOSED will follow 30 days of no contact.
3)Not a real bug:In the case you can think of the reported as not real problems ,such as just a qustion ,it will be CLOSED .
4)Feature request:This report will be closed as soon as TL respond to the reporter
a)TurboLinux decides to implement your request.
b)TurboLinux rejects the request.
In case of #2, the report will be closed immediately.
For #1 it will be closed when the request is actually implemented.

If TurboLinux has difficulty investigating your report, it may ask some guidelines for more detail via email.

3.Access to Bugzilla

You can access Bugzilla at http://dev.turbolinux.co.jp/bugzilla/

4.Getting your account.

You need your own account in order to use Bugzilla.It is available from the web site described above. You'll receive your password by mail just after getting your accounts at that web site.
Bugzilla will permit you to login with your email address you registered when you got the account and password you received by mail.
Information of your accessing Bugzilla was saved as cookies so that you can use the bugzilla without loging in when reaccessing Bugzilla as long as the cookies are remained available on disks.

5.Your mail addresses to the public

You can choose whether you will have your email address is visible to the public or not. The word "the public" means that anyone who has the right to look over your bug report will know your email address because your email address is on the bug report. The benefit you have for presenting the address to the public is that every time any information is added to Bugzilla, it will be automatically sent to the address. In other words , you will not recieve mail from Bugzilla if you don't have your address be to the public.

Because the system will assign a unique ID ,and replace with your email address on the log field of the bug report if you don't have the address be to the public ,and no one can know your address from the bug report. In this case ,you have to check the latest information manually.

You can change your address's publicity once after you reported the bug. Although information already described on the report will remain on the field, please take a note that the previous publicity setting will be remained in already reported bug.

6.Report / Search the bug

This section covers how to report new bugs and search those bugs.

a)Report a new bug

At the site http://dev.turbolinux.co.jp/bugzilla/ , click "Enter a new bug".
When asked to login , login the Bugzilla using your account (your email address) and
password you registered when you got the account.
Now you have the window for entering new bugs.

In the window you can see some fields to which you put some information.

a)Product
b)Product version
c)Platform
d)Package
e)Version/Release
f)Priority
g)Severity
h)Justification for P1
i)Assigned to
j)Cc:
k)URL
l)Summary
m)Description
n)Defect Type