User Interface Testing: More guide lines

Hey friends, you know woah..

User Interface Testing presents software teams with significant challenges. Simple UIs reveal a surprisingly large number of possible interactions, and therefore potential bugs. Lets see how we can start the UIT. When we test the Colors what do we have to consider?

Well, I try to answer these questions Yes- Are hyperlink colors standard?,are the field backgrounds the correct color?, are the field prompts the correct color?Are all the buttons in standard format and size?Is the page background (color) distraction free?Are the screen and field colors adjusted correctly for non-editable mode?Does the site use (approximately) standard link colors?

Hey, what about the content? Do you all check All fonts to be the same,are all the screen prompts specified in the correct screen font? Does content remain if you need to go back to a previous page, or if you move forward to another new page?Are all texts properly aligned?Is the text in all fields specified in the correct screen font?Are all heading left aligned?

Any idea to test the navigation? oki doki. I try to fill these gaps.Are all disabled fields avoided in the TAB sequence?Are all read-only fields avoided in the TAB sequence?Can all screens accessible via buttons on this screen be accessed correctly? Does a scrollbar appear if required?Does the Tab Order specified on the screen go in sequence from Top Left to bottom right? (This is the default unless otherwise specified)Is there a link to home on every single page? On open of tab focus will be on first editable field When an error message occurs does the focus return to the field in error when the user cancels it?

Finally, what about the Usability. These are the stuff i learnt from test gurus' and i strictly practice. Are all the field prompts spelled correctly? Are fonts too large or too small to read? Are names in command button & option box names not abbreviations.Assure that option boxes, option buttons, and command buttons are logically grouped together in clearly demarcated areas "Group Box" ,Can the typical user run the system without frustration?Do pages print legibly without cutting off text? Does the site convey a clear sense of its intended audience? Does the site have a consistent, clearly recognizable "look-&-feel"? Does User cab Login Member Area with both UserName/Email ID ?Does the site look good on 640 x 480, 600x800 etc.? Does the system provide or facilitate customer service? i.e. responsive, helpful, accurate?Is all terminology understandable for all of the site’s intended users?

Hope, its enough for the day..

Coders and Testers : Friends or Foes?

As a tester , dealing with coders is inevitable. The sad reality is that the relationship or the link in both communication and understanding between coders and testers have not been so smooth in the recent past. Many research evidences support this reality. However, in my personal life I always some how manage to build a good relationship with coders. Our experience affect how we understand programmers and how, when we work as testers, we work with programmers. In my current work place I enjoy my work as a tester. Let me tell you how I move with coders.

From my experience, the best way to learn how to interact with coders is to become and to work with other coders as our peers for a while. I have a development background. I came to testing after I have written some production code, had it criticized, condemned and praised by testers, users and managers. We, testers and coders work under different conditions. coders focus on their own theory. They have models for how the system components are related, which components are reliable and how errors proper gate. they must work from their mental model. when they tell that a bug we reported cant happen, they are not saying they are infallible. they are saying this type of error doesn't fit with their model and what they believe to be true. we testers better have to focus on observation and evidences. This tests their model.I always Keep clear notes and logs, focus on reports on what I have actually seen and let them find the flaws in their reasoning.

We will be effective if the coders share information with us such as their plans , early drafts, design docs, prototypes, etc.I find out what kind of feed back they want and give it to them. I always offer to assist coders directly. This builds trusts and proves that I am some one they should cooperate with.

Consideration when testing a web based project GUI

Company to company their testing principles and standards varies. Many software test giants in leading companies follow their own testing standards like ISO, Six Sigma and CMM level etc.. Especially for web site testing we need to follow some basic testing rules. In my opinion when I test the GUI of the web in smoke level I test the following.

1.Page completes loading
2.Loading completes in a reasonable amount of time
3.Page loading consistent between browser versions
4.Page loading time reasonable under load
5.Graphics, text and other elements seem to be in correct locations
6.Page has logical flow
7.Color contrast issues
8.Graphics loading completely
9.Graphics completed loading within same time frame,Consistently loading every time
10.Non-browser safe color pallet used
11.Scaling, cropping or image quality problems
12.Highly artifact (distorted) image quality
13.Unpredictable color rendering at various bit depths
14.Rollover graphics displaying correctly
15.Graphic rollover state providing correct transition illusion
16.Preloaders working correctly for quick screen redraw
17Graphical text within graphic is legible Correctly spelled text within graphic

I am curious to know other issues to be notified. I welcome your suggestions