Test Carried out | Expected | Actual (Yes or No ) | Remarks | Ticket Reference (Corresponding bug id if u have any bug tracking tool ) |
1. Functionality | ||||
1.1 Links | ||||
Internal Links | Should be present |
|
|
|
External Links | Should be present |
|
|
|
Mail to links | Should open mailbox |
|
|
|
Orphan pages (a page that has no links to it) | Should not be present |
|
|
|
Broken links | Should not be present |
|
|
|
Are all referenced web sites or email addresses hyperlinked? |
|
|
|
|
If we have removed some of the pages from our own site, set up a custom 404 page that redirects your visitors to your home page (or a search page) when the user try to access a page that no longer exists. |
|
|
|
|
|
|
|
|
|
1.2 Forms | ||||
Acceptance of invalid input |
|
|
|
|
Input longer than field allows | Checked Unique records, Date validation |
|
|
|
Functional checks | Create, modify, view and delete are working. |
|
|
|
Error Handling for wrong inputs or actions. | Appropriate error messages to be displayed. |
|
|
|
Optional and mandatory fields. | Mandatory field should not be left blank. Optional should allow the user to skip the field. |
|
|
|
|
|
|
|
|
1.3 Cookies | ||||
Check to see what happens if a user deletes cookies while in site |
|
|
|
|
Check to see what happens if a user deletes cookies after visiting a site |
|
|
|
|
|
|
|
|
|
1.4 Data integration | ||||
Check the maximum field lengths to ensure that there are no truncated characters? |
|
|
|
|
If numeric fields accept negative values can these be stored correctly on the database and does it make sense for the field to accept negative numbers? |
|
|
|
|
If a particular set of data is saved to the database check that each value gets saved fully to the database. (i.e.) Beware of truncation (of strings) and rounding of numeric values. |
|
|
|
|
|
|
|
|
|
1.5 Data field check | ||||
Assure that leap years are validated correctly & do not cause errors/miscalculations. |
|
|
|
|
Assure that Feb. 28, 29, 30 are validated correctly & do not cause errors/ miscalculations. |
|
|
|
|
|
|
|
|
|
1.6 Numeric fields | ||||
Assure that lowest and highest values are handled correctly. |
|
|
|
|
Assure that numeric fields with a blank in position 1 are processed or reported as an error. |
|
|
|
|
Assure that fields with a blank in the last position are processed or reported as an error |
|
|
|
|
Assure that both + and - values are correctly processed. |
|
|
|
|
Assure that division by zero does not occur. |
|
|
|
|
Include value zero in all calculations. |
|
|
|
|
|
|
|
|
|
1.7 Alphanumeric field checks | ||||
Use blank and non-blank data. |
|
|
|
|
Include lowest and highest values. |
|
|
|
|
Include invalid characters & symbols. |
|
|
|
|
Include valid characters. |
|
|
|
|
Include data items with first position blank. |
|
|
|
|
Include data items with last position blank. |
|
|
|
|
|
|
|
|
|
2. Usability: How Simple Customer can browse the website | ||||
2.1 Navigation: It describes the way user navigate with in a webpage, between different user interface controls ( buttons, text boxes, combo boxes, drop down lists etc) | ||||
Navigation through Mouse | Should be proper |
|
|
|
Navigation through Tab | Should be proper |
|
|
|
Main features access | Should be accessed from home/Main page |
|
|
|
Hot Keys, Control Keys for menu or action | Should work |
|
|
|
|
|
|
|
|
2.2 Content: Correctness is whether the information is truthful or contains misinformation. The accuracy of the information is whether it is with out grammatical or spelling errors. | ||||
Spelling and Grammar | To be proper |
|
|
|
Updated information’s. | Past events/ information’s to be removed. |
|
|
|
|
|
|
|
|
2.3 General Appearance | ||||
Page Appearance | Should not be any overlapping, missing etc., |
|
|
|
Colour, font and size | Should be as per standard |
|
|
|
Frames | All frames to be appeared |
|
|
|
Consistent Design | Everywhere in the website consistent layout and design should be carried out. |
|
|
|
Favicon, logos and symbols |
|
|
|
|
|
|
|
|
|
3. User Interface : All about how exactly website look like | ||||
3.1 Screen resolution | must be tested with various screen |
|
|
|
3.2 Varying font size |
|
|
|
|
3.3 View in text browser |
|
|
|
|
3.4 Without Javascripts |
|
|
|
|
3.5 Without plug-in if any |
|
|
|
|
3.6 Without images |
|
|
|
|
3.7 Page titles |
|
|
|
|
3.8 Hyperlink colors | It should be standard |
|
|
|
3.9 All the fonts to be same |
|
|
|
|
3.10 All images are optimized for quick downloads |
|
|
|
|
3.11 Alt tag for all images |
|
|
|
|
3.12 Are all disabled fields avoid in TAB sequence |
|
|
|
|
3.13 Are all read only fields avoid in TAB sequence |
|
|
|
|
3.14 Link to home on every single page |
|
|
|
|
3.15 Default value of the drop down box | Should have meaningful sentence such as "Choose one" or "Select" |
|
|
|
3.16 Cursor will be on first editable field |
|
|
|
|
3.17 When an error message occurs does the focus return to the field in error when the user cancels it? |
|
|
|
|
3.18 Persistancy of all values ( When you enter values in a form, and move on the next page and then return to change one of the previous screen. The user must not be forced to reenter all the values once again, this must be checked and ensured. ) |
|
|
|
|
3.19 Pagination | Use where appropriate |
|
|
|
3.20 Error messages | Illegal operations should give error messages and they should be simple and clear |
|
|
|
3.21 Success messages | Should display |
|
|
|
3.22 Horizontal scrolling | Avoid horizontal scroll bar ensure that the use of vertical scroll bar is judicious |
|
|
|
|
|
|
|
|
4. Server Side Interface |
|
|
|
|
4.1 Server Interface | Communication should be correct with respect to Web server, App server and DB server |
|
|
|
4.2 Compatibility with server hardware, Sw, network connections | Should be proper. |
|
|
|
4.3 Database compatibility[s1] | Should be easily portable to other database. |
|
|
|
|
|
|
|
|
5. Client side Compatibility | ||||
5.1 Platform | ||||
Windows2000, NT | Should be working |
|
|
|
Unix | Should be working |
|
|
|
Linux | Should be working |
|
|
|
Solaris | Should be working |
|
|
|
Macintosh | Should be working |
|
|
|
|
|
|
|
|
5.2 Browsers | ||||
I.E | Should work in all versions above 4.x |
|
|
|
Firefox | Should work in all versions above 2.x |
|
|
|
Safari |
|
|
|
|
Opera |
|
|
|
|
|
|
|
|
|
Graphics | Load of images, graphics should be proper |
|
|
|
|
|
|
|
|
4.3 Printing | ||||
|
|
|
|
|
Text and alignment | Should be proper |
|
|
|
Colours of text, foreground and background | Should be readable. |
|
|
|
Scalability to fit paper size. | Should print in A4, Letter size. |
|
|
|
Tables and borders. | Should be proper. |
|
|
|
|
|
|
|
|
6. Performance | ||||
6.1 Connection speed | ||||
Should be measured in 14.4, 28.8, 33.6, 56.6, ISDN, Cable and DSL |
|
|
|
|
Timeout | Should give appropriate time to search. Incorrect message, data loss should not be present. |
|
|
|
|
|
|
|
|
6.2 Load | ||||
Estimated users. | Per requirements |
|
|
|
Peak load | Should withstand |
|
|
|
Large amount of data from users | Should accept |
|
|
|
|
|
|
|
|
6.3 Stress | ||||
System Crash | Should not be present |
|
|
|
Error in Sw, HW, Memory | Leakage, overwrite should not happen. |
|
|
|
|
|
|
|
|
6.4 Continuous use | ||||
Estimate whether available for 24 Hrs, 7 days a week | Try with various timings. |
|
|
|
Downtime | Measure the downtime |
|
|
|
Memory or disk space | Should not run out of memory or disk space. |
|
|
|
|
|
|
|
|
7. Security | ||||
7.1 Valid and Invalid | Should not enter with Invalid login |
|
|
|
7.2 Number of tries | Should not be more than 3 times for invalid try. |
|
|
|
7.3 Enter url directly without logging in. | Should not display information. |
|
|
|
7.4 Log files | Should be maintained |
|
|
|
7.5 Access to server scripts | Authenticated. |
|
|
|
7.6 Does the application include time-outs due to inactivity? |
|
|
|
|
7.7 Is bookmarking disabled on secure pages? |
|
|
|
|
7.8 Is Right Click, View, Source disabled? |
|
|
|
|
7.9 SQL injection |
|
|
|
|
7.10 Java script injection |
|
|
|
|
8. HTML Validations | ||||
HTML Validation |
|
|
|
|
CSS Validation |
|
|
|
|
Styles should be always placed in external CSS files. |
|
|
|
|
Content should be formatted through cascading styles (CSS). |
|
|
|
|
|
|
|
|
|
9 SEO | ||||
9.1 Domain name | ||||
Main keyword in the domain name |
|
|
|
|
Easy to spell and remember |
|
|
|
|
Without hyphens were possible |
|
|
|
|
Domain extension |
|
|
|
|
Host location |
|
|
|
|
|
|
|
|
|
9.2 URL | ||||
URL structure | Avoid using lengthy URLs with unnecessary parameters and session IDs. |
|
|
|
Directory structure | Create a simple directory structure |
|
|
|
Unique to each page | Do not have duplicate ones like http://www.mywebsite.com/ and http://www.mywebsite.com/index.php. |
|
|
|
Mixing www. and non-www. versions of URLs |
|
|
|
|
Odd capitalization of URLs |
|
|
|
|
Extension | Aim to hide the underlying technology of your website and thus remove the extension, creating clean and descriptive URLs. |
|
|
|
Keywords in URL | Should include relevant keywords – Avoid keyword duplication. The keyword should be mentioned sooner in the URL |
|
|
|
|
|
|
|
|
9.3 Page Title | ||||
Unique |
|
|
|
|
Informative |
|
|
|
|
Keyword in title |
|
|
|
|
|
|
|
|
|
9.3 Meta tags | ||||
9.3.1 Description meta tag - Limit to 150 characters | ||||
Summary of the page content |
|
|
|
|
Unique description for each page |
|
|
|
|
9.3.2 Description meta tag | ||||
Number of keywords | don’t use more than 7 to 10 words for your meta keywords |
|
|
|
Unique and relevant keywords | Use unique and relevant meta keywords for every single page, related to page content. Do not repeat any word more than 3 times. |
|
|
|
Usage of capital letters | Don't use all capital letters unless the word is an acronym, like "SEO", which is short for Search Engine Optimization. |
|
|
|
9.3.3 Robots Meta Tag (add in live server) | ||||
Check | This is specified if the current page should not be indexed by the search engines, as in the case of a custom error page. |
|
|
|
|
|
|
|
|
9.4 Page contents | ||||
Number of words | Each page of your content should contain about 250 – 600 words of unique content with 4 or 5 occurrences of your targeted keywords. |
|
|
|
Keyword density | At least 3 keywords in a page. Your keywords should be toward the top of your page and your keyword phrase is in either every paragraph or every second paragraph depending on your paragraph length. |
|
|
|
Hyper linked keyword | Include your most important keyword in hyper linked text. |
|
|
|
|
|
|
|
|
9.5 Alt tag | ||||
Alt tag for images |
|
|
|
|
Keywords as alt tag | Wherever possible, put PROPER KEYWORDS in the ALT tags. Don’t go wild with this and don’t miss-label any pictures. |
|
|
|
Alt tags for navigation buttons |
|
|
|
|
|
|
|
|
|
9.6 Sitemap | ||||
Sitemap.xml |
|
|
|
|
|
|
|
|
|
9.7 Anchor tag | ||||
|
|
|
|
|
9.8 Robots.txt | ||||
|
|
|
|
|
9.9 Page size | ||||
Check page size | Good SEO site page size ideal should be 15KB, can exceed up to 50 KB. |
|
|
|
|
|
|
|
|
9.10 Error page | ||||
Check for custom error page |
|
|
|
|
|
|
|
|
|
9.11 Redirection | ||||
301 redirection | Check for permanent redirection |
|
|
|
302 redirection | Temporary redirection |
|
|
|
|
|
|
|
|
Wednesday, April 1, 2009
QA Check list
Subscribe to:
Post Comments (Atom)
1 comment:
Post a Comment