Checklist on how we do Website Testing
2017
QA Specialist TestOrigen Software Testing Pvt. Ltd.
Checklist for Website Testing 1/1/2017
WWW.TESTORIGEN.COM
Page 1
Checklist on how we do Website Testing
2017
Functional Testing: Checks for Functionality of Links: Tested by Tested on Pass or Fail
Remarks
1. Internal links wherever present, are working or not? 2. External links wherever present, are working or not? 3. Mail to links wherever present, are opening the mailbox or not? 4. Regardless of whether any vagrant pages are available or not? 5. Regardless of whether any broken connections are available or not?
Checks for Functionality and Integrity of Data Entry Forms
Tested by Tested on Pass or Fail
Remarks
1. Test the field level checks carried out such as checks for length, exceptional characters, numerical characters and so forth. 2. Test the field level validation carried out such as checks for unique records, date approval and so on. 3. Test the functional checks carried out such as Create, Modify, View and Delete are working legitimately. 4. Test the error handling for wrong information sources or activities completed such as proper error messages are getting shown or not? 5. Functionality Test for compulsory and optional fields completed such as a compulsory field should not be left clear and an optional should enable the client to avoid the field.
WWW.TESTORIGEN.COM
Page 2
Checklist on how we do Website Testing
Functionality Checks for Cookies
2017
Tested by Tested on Pass or Fail
Remarks
Tested by Tested on Pass or Fail
Remarks
Tested by Tested on Pass or Fail
Remarks
1. Functionality tests for Web Indexing 2. Check whether Meta labels are present or not? 3. Check whether Syntax of html is valid or invalid? 4. Check whether Frames are Ok or not?
Functionality Checks for Databases 1. Checks for database for its information integrity completed such as any lost or wrong information exhibit in the database or not? 2. Check whether the database for Output Errors tested such as any bugs in composing, perusing or altering operations display in the database or not?
Usability Testing: Navigation Test cases: 1. All pages of your site are easy to understand and utilize. 2. Shapes, Buttons and fields are advantageous for utilize. 3. There is an access to the Main menu from all pages.
WWW.TESTORIGEN.COM
Page 3
Checklist on how we do Website Testing
Content Test Cases:
2017
Tested by Tested on Pass or Fail
Remarks
Tested by Tested on Pass or Fail
Remarks
Tested by Tested on Pass or Fail
Remarks
1. There are no spelling mistakes and grammatical errors. 2. Pictures are set legitimately with appropriate sizes. 3. Check enhancement of the shading palette of the site and text dimensions. 4. Content should be enlightening, justifiable, organized and logically linked. 5. Guidelines are clear and contain revise data.
General Appearance Test Cases: 1. Check whether page appearance is appropriate with no covering, missing data? 2. Check whether shading, textual style and sizes are according to the standard or not? 3. Check whether all frames are getting shown or not? 4. Check whether format and outline of all aspects of the site is predictable or not?
Server Interfaces Test Cases: 1. Communication among web server, application server and Database server 2. Check whether compatibility among network connections, server hardware, Software is appropriate or not?
WWW.TESTORIGEN.COM
Page 4
Checklist on how we do Website Testing
2017
3. Check whether database compatibility has been checked for its simple convey ability to any other database.
Interface Testing: Server Interface Test Cases:
Tested by Tested on Pass or Fail
Remarks
Tested by Tested on Pass or Fail
Remarks
1. If site calls external servers for extra information, check that the product can deal with each conceivable message returned by the external server. 2. To test server interface and browser, run inquiries on the database to ensure the exchange information is being recovered and store suitably.
Error/bug Handling Test Cases: 1. Ensure framework can deal with application errors and bugs. 2. Ensure that framework can deal with other frameworks' errors such as losing the web connection from server to the external server. 3. How the exchange is handled, if client does not initiate interruption.
Performance Testing: Performance Checks for Connection speed.
Tested by Tested on Pass or Fail
Remarks
1. Check whether connection speed is measured in 14.4, 28.8, 33.6, and 56.6, ISDN, Cable and DSL?
WWW.TESTORIGEN.COM
Page 5
Checklist on how we do Website Testing
2017
2. Check whether proper timeout is given to seek or not? Regardless of whether error messages are getting shown and data loss is not there?
Performance Checks for Users Load.
Tested by Tested on Pass or Fail
Remarks
1. Check whether load necessities have been estimated according to client needs or not? 2. Check whether application can withstand the peak loads or not? 3. Check whether application can acknowledge large number of information from the clients or not?
4. Check whether application or framework crashes under stress conditions or not? 5. Check whether any bugs or issues in Software, Hardware or Memory such as Leakage, overwrite watched or not? 6. Check whether the application stays accessible for 24 Hrs, 7 days a week or not? Whether this aspect has been checked with various timings? 7. Check whether downtime has been measured when application went down because of consistent utilizes? 8. Check whether satisfactory memory or disk space has been given to the application to maintain continuous use? Testing Tools- latest Performance Testing Tools Suggested-Apache JMeter and LoadRunner
WWW.TESTORIGEN.COM
Page 6
Checklist on how we do Website Testing
2017
Compatibility Testing: Browser Compatibility Test cases: Test Functionality in Following Browsers: 1. 2. 3. 4. 5. 6. 7. 8.
Tested by Tested on Pass or Fail
Remarks
Internet Explorer 11(latest Version) Internet Explorer 10 Internet Explorer 9 Internet Explorer 8 Safari (latest Version) Firefox (latest Version) Chrome (latest Version) Opera (latest Version)
Phone Devices Compatibility Test cases: Testing of functionality of following devices:
Tested by Tested on Pass or Fail
Remarks
1. Android Smartphone (latest version) 2. Windows phone (latest version) 3. Apple iPhone (latest version) 4. iPad Air(latest version) 5. Samsung Galaxy Tab A (latest version) 6. Blackberry (latest version) 7. Moto E (latest version) 8. Moto E3 (latest version) 9. LG Nexux 5X (latest version) 10. HTC 828 (latest version) 11. MI 4I (latest version)
WWW.TESTORIGEN.COM
Page 7
Checklist on how we do Website Testing
2017
12. VIVO Y5IL (latest version) 13. Honor H30UI0 (latest version) 14. Lenevo A526 (latest version)
Checks for Client side Compatibility:
Tested by Tested on Pass or Fail
Remarks
1. Test whether checks have been performed for operation on stages like Windows2000, NT, UNIX, Linux, Solaris, and Macintosh and so on. 2. Test whether checks have been performed for legitimate capacity with programs like Internet Explorer Netscape Navigator 3.x and above? 3. Check whether loading of graphics and pictures is proper? 4. Check whether content and arrangement is appropriate during printing? 5. Check whether shades of content, frontal area and foundation are readable and appropriate during printing? 6. Check whether shades of content, frontal area and foundation are readable and appropriate during printing? 7. Check whether adaptability to fit on the desired paper size is appropriate? Such as, it should be conceivable to print in A4, A3 or Letter measure and so on. Testing Tools- Phone Compatibility Testing Tools Suggested- BrowserStack.
WWW.TESTORIGEN.COM
Page 8
Checklist on how we do Website Testing
2017
Security Testing: Security related Checks
Tested by Tested on Pass or Fail
Remarks
1. Test whether a client can enter the application with Invalid login? 2. Test whether a limit of maximum 3 tries for an invalid login gave or not? 3. Test whether log documents are maintained or not? 4. Test whether access to server scripts authentication gave or not?
WWW.TESTORIGEN.COM
Page 9