[A] Functionality Testing:
While testing the functionality of the websites the next areas should hold upwardly tested.
a) Links/URL Testing: There are mainly four types of links inwards most websites.
» Internal links [Test the links that hollo for to the pages of the same website.]
» External links [Test the links that hollo for to external websites.]
» Mail links [Test if the e-mail links opened upwardly the default e-mail client alongside the recipient e-mail ID already filled inwards the “To” field.]
» Broken links [Test if whatsoever of those links are broken or dead! Free tools similar Ben Simo has a prissy article that y'all mightiness expose interesting.
e) Testing optional too mandatory fields: Test if the spider web forms grip the optional too mandatory fields efficiently. Ideally, the application should non allow y'all to continue unless y'all conduct maintain filled inwards ALL the mandatory fields too should non bound y'all from proceeding if y'all conduct maintain left ANY of those optional fields unfilled!
f) Database Testing: Most of the modern hateful solar daytime websites come upwardly alongside a backend database (unless it’s a site consisting of purely static spider web pages). So testing the database for its integrity becomes essential to brand certain the website is able to grip the information processing effectively.
g) Cookies Testing: Influenza A virus subtype H5N1 cookie is information that a website (server side) puts on your difficult disk (client side) therefore that it tin recall something almost y'all at a later on time. If your website sets cookies at the client machines too therefore examine to banking concern tally that cookies too other session tokens are created inwards a secure too unpredictable way. Poor treatment of cookies tin resultant inwards safety holes too vulnerabilities that tin hold upwardly taken wages past times malicious users too hackers. Here is a prissy article on load/stress testing. Performance testing tin hold upwardly applied to sympathise the website’s scalability, whatsoever loopholes inwards the charge balancing too to examine the answer fourth dimension betwixt a asking (from the client) too the respond (from the server) too the sum of load/stress the site is able to sustain. Scott Barber’s testing the usability of a website are:
» Ease of learning (How intuitive too self-explanatory the site is).
» Navigation.
» User satisfaction.
» Web accessibility testing (If all the content too parts of the site are accessible).
» General appearance (Look too feel).
[E] Testing Client-Server Interface:
[E] Testing Client-Server Interface:
In spider web testing the server side interface is tested to verify that communication is properly established alongside the client. In instance of n-Tier architecture based spider web applications, the middle-tier Business Logic APIs should also hold upwardly tested (even if they are third-party shrink-wrapped softwares) for whatsoever communication/interface malfunctioning!
[F] Compatibility Testing:
[F] Compatibility Testing:
Test your website to verify that it’s pages homecoming adequately inwards dissimilar browsers (e.g. IE 5, IE 6, IE 7, Firefox 2, Opera, Safari etc) using dissimilar operating systems (Win XP, Vista, Linux, Mac etc) on dissimilar hardware platforms. Different versions, configurations, display resolutions, too Internet connect speeds all tin affect the conduct of the spider web pages too tin innovate embarrassing (and oft costly) bugs. However, an of import matter to recall patch testing the spider web compatibility is – nosotros should showtime position the major client base of operations for the website too and therefore determine the top dog browsers too OS to examine for. Some typical compatibility tests include testing your application:
» Using diverse browsers.
» Using diverse window sizes.
» Using diverse font sizes.
» Using browsers alongside CSS, JavaScript turned OFF!
» Using browsers alongside pop-up blockers!
» On diverse Operating Systems.
» With dissimilar covert resolutions too colouring depths.
» On diverse client hardware configurations.
» Using dissimilar retentiveness sizes too difficult stimulate space.
» In dissimilar network environments.
» Ability to conduct maintain printouts alongside dissimilar printers (Printer-friendly Versions)
[G] Web Security Testing:
[G] Web Security Testing:
Often Web Security Testing is also referred to every bit Penetration Testing. The primary objective for testing the safety of a website is to position potential vulnerabilities/security holes too to patch/repair them. For example, if your website allows closed to files to hold upwardly uploaded, your spider web server should conduct maintain proper automated antivirus checking inwards house to expose too disable whatsoever endeavour of virus uploading past times the client side. Some of the major aspects of spider web safety testing are:
» Network Scanning.
» Vulnerability Scanning.
» Password Cracking.
» Log Review.
» Integrity Checkers.
» Virus Detection.
Hope this article helps inwards giving a fossil oil coverage of areas that needs attending patch testing a website. Did I missy something hither that should conduct maintain been included inwards the checklist? Feel gratuitous to allow me know past times commenting too I volition update this post along alongside proper credit to you.
Hope this article helps inwards giving a fossil oil coverage of areas that needs attending patch testing a website. Did I missy something hither that should conduct maintain been included inwards the checklist? Feel gratuitous to allow me know past times commenting too I volition update this post along alongside proper credit to you.
Update: An of import facial expression of website testing that I had missed to include inwards my cheat-sheet is Testability Testing. Thanks to Michael Bolton for his comment.
Happy Testing…