GUI TESTING

GUI Testing

What is GUI Testing ? When is GUI Testing done ? How do you do GUI Testing ? Where is GUI Testing Used ? Why is GUI Testing done with automated tools ? Advantages and Dis-advantages of GUI Testing

GUI Testing

What is GUI Testing ?

- GUI means Graphical User Interface

- GUI Testing is done to check the look and feel of the application under Test.
- This means presenting to the end user which should be soothing his eyes - Look and feel emphasis's the alignments of the UI & its properties. - UI can also be called as CONTROLS. Its properties includes, * Label * The X- Co-ordinate * Height * Width * The Y- Co-ordinate * Font Size * Font Color * Font Type., etc,.

GUI Testing

To test any Windows based application following points are to be considered: - It is essential to have GUI consistency within the Application. - Should be alike in look and feel as per any other standard Window software. - Should have standard set of keys implemented for the software. - Should have clean and neat exit. While testing any Windows based application the testing can be broadly categorized into following compartments. They are: - Standardization Testing. - GUI Testing.

- Validation Testing.
- Functionality Testing.

GUI Testing

GUI Testing :
- Mainly emphasizes on the GUI - Graphics User Interface aspect of the Application. - It is not concrete that once GUI guidelines are set that can be followed blindly - GUI standards may vary from company to company and also from application to application.

- But still one can set general guidelines to have an overall idea on how to start GUI testing.
-Guidelines apply for every screen/ dialog box of the application

GUI Testing

General guidelines are:

1. All the dialog box should have a consistent look through out . For e.g.- If the heading within a dialog box is blue then for each dialog box the heading should be of this color. 2. Every field on the screen should have an associated Label. 3. Every screen should have an equivalent OK and cancel button. 4. The color combination used should be appealing. 5. Every field in the dialog box should have a Short Cut Key support. For e.g.- User Name 6. Tab order should be normally set horizontally for the fields. In some case as per the case the Tab Order can be set vertically. 7. Mandatory fields should have * (RED ASTERIK) marked to indicate that they are mandatory fields. 8. Default key <Enter> should be set as OK for the dialog box. 9. Default key <Esc> should be set as Cancel for the dialog box.

GUI Testing
When is GUI Testing done ?
-

Should be done during the design phase. Practically its conducted in system phase.

GUI Testing
How do you do GUI Testing? It can be carried out manually It can be carried out using automation tools also. Manually Testing :- We need Test case for GUI - To execute we need data, test data .. So its not possible ( difficult ). - So we use Checklist of GUI to test manually. - Its time consuming. - Perception varies from tester to tester and user to user. - So least used for testing GUI options.

GUI Testing
Testing principles applied to GUIs

Focus on errors to reduce the scope of the test Test design techniques where appropriate Test automation where ever possible

GUI Testing

Some GUI Standards:

All the dialog box should have a consistent look through out the Application system.
Every field on the screen should have an associated Label.

Every screen should have an equivalent OK and cancel button.

The color combination used should be unique. Every field in the dialog box should have a Short Cut Key support. Tab order should be normally set horizontally for the fields.

GUI Testing

Font and Color:

Is the general screen background the correct color? Are the field prompts the correct color Are the field backgrounds the correct color?

Are all the screen prompts specified in the correct screen font?
Is the text in all fields specified in the correct screen font? Are all the field prompts aligned perfectly on the screen?

Is all the error message text spelt correctly on this screen?

GUI Testing
Alignment:

Are all the field prompts aligned perfectly on the screen? Are all the field edit boxes aligned perfectly on the screen? Are all group boxes aligned correctly on the screen?

Are all character or alpha-numeric fields left justified?

Are all numeric fields right justified?

GUI Testing

Advantages:Checklists draw on range of issues that help in deciding where to concentrate efforts
Deadline and resource limitations can heat up the environment and in rush to deliver ,testers are liable to miss on critical and important checks. It is good structured base for testing. It is reusable . Other testers also use valuable tests across different projects. Checklists work as a remembers to testers

GUI Testing

Disadvantage:It heavily depend on the general data in the checklist as opposed to in text data, for practical evaluation.
Testing of a product remains as good or as bad as the previous product according to which the checklist were made.

Testers lose their independence and creativity if they keep following a predefined checklists.
It is difficult to prepare checklists because number of combinations are too large.

GUI Testing

Automation Tools:-

For sharp & better results , GUI testing is done with tools. Tools are freely available The application should satisfy W3C standards for web applications.

Few Automation Tools are :

Linux Desktop Testing Project by freedesktop.org Phantom Automation Language Microsoft Windows GUI Testing QAliber by QAlibers, free open source for testing applications and web over windows OS QF-Test by Quality First Software, for Java/Swing, Eclipse/SWT and HTML only HP QuickTest Professional (QTP) by Hewlett-Packard (formerly by Mercury) IBM Rational Functional Tester by IBM

GUI Testing

Advantages :-

These tools are efficient and effective compared to normal manual GUI testing. Time consumed is less . Output efficiency is high and precise.

Disadvantage:-

Few tools are very expensive . Needs high level knowledge for testing.

GUI Testing

Questions ???