As a SQA we come across various types of web sites to test on. Every site is different in their own way depending on their need of existence.
The common thing between webpages is the web elements present on it. It can be diverse but countable and testable
SQA person needs to be diligent all the way while testing web sites, moreover the functionalities allied with the web elements. If we look intensively into a site it’s merely a combination of controls that take inputs from a user, save in database and then again shows the same data on the user interface. We as QA personnel are held responsible for all kind of testing performed. Moreover the website should run flawlessly in different set of browsers like Internet Explorer, Firefox, and Safari etc. Some sites are so intricate in their designs/ functionality, so if we could take care of some basic steps it may help in achieving a great quality of product.
Here are some of the checks that can be helpful for testing the various controls we encounter on a web page and should be followed according to the project scope.
Checklist for testing a textbox control:
- Look/feel and label associated with it
- Enabled/Disabled
- Tool tip
- Editable (If enabled)
- Types(numbers, alphabets, special chars, cases (upper, lower), spaces)/combination of characters that can be entered
- Char limits
- Validation if any
- Tab order
- Multilingual characters check (if in scope of project)
Checklist for testing a Button control:
- Look/feel and label associated with/on it
- Enabled/Disabled
- Tool tip
- Clickable if Enabled
- Validation if any
- Tab order
Checklist for testing a Dropdown control:
- Look/feel and label associated with it
- Enabled/Disabled
- Tool tip
- Correctness of information shown
- May/may not contain “Select” as first value (i.e. zero index)
- Validation if any
- Tab order
Checklist for testing a checkbox control:
- Look/feel and label associated with it
- Enabled/Disabled
- May/may not contain tool tip for every checkbox
- Check/uncheck single/multiple
- Validation if any
- Tab order
Checklist for testing a Radio button control:
- Look/feel and label associated with it
- Enabled/Disabled
- May/may not contain tool tip for every radio button
- From a group only one should get selected at once
- Validation if any
- Tab order
Checklist for testing a Multiline/Rich text box control:
- Look/feel and label associated with it
- Enabled/Disabled
- Tool tip
- Editable (If enabled)
- Types (numbers, alphabets, special chars, cases (upper, lower), spaces, html, images, videos etc.)/combination of characters that can be entered
- Char limits
- Multilingual characters check (if in scope of project)
- Validation if any
- Tab order
Checklist for testing any text:
- Look/feel and color
- Relevance
- Spellings
Checklist for testing an Image/Picture:
- Look/feel and label associated with it (if any)
- Enabled/Disabled
- Alternate text property should always be provided
- Validation if any
- Clicking on images (if clickable, navigation to desired destination)
- Tab order
Checklist for testing a video:
1. Look/feel and label associated with it (if any)
2. Enabled/Disabled
3. Alternate text property should always be provided
4. Play, pause, forward, backward, volume, mute, maximize buttons, time etc
5. Audio and Video synchronization
6. Tab order
Checklists for testing a File upload control:
- Look/feel and label associated with it
- Enabled/Disabled
- Tool tip
- Uploading a file/doc
- Max/min file size allowed
- Multiple file uploading (if allowed)
- Tab order
- Validation if any
Checklist for testing a Calendar control:
- Look/feel and label associated with it
- Enabled/Disabled
- Tool tip
- Selecting suitable dates
- Manually entering dates (if allowed)
- Tab order
- Validation if any
Checklists for testing links:
- Look/feel and text associated with it
- Enabled/Disabled
- Tool tip
- Clickable (navigation to desired destination)
- May/may not have distinct color for a link (different color recommended)
Checklists for testing Data grids/tables:
- Look/feel
- Enabled/Disabled
- Sorting of columns (recommended, depends on project scope)
- Pagination
- Tab order
Albeit we can have many more scenarios that need to be tested comprehensively, above are the minimal sets of steps on which without contemplation we can start with. As said discovering the unexpected is more important than confirming the known.
Be Skeptic, Test More
No comments:
Post a Comment