Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide


  1. 1. QA - Directions Reea Robert Dămoc 2010, autum
  2. 2. Web application testing <ul><li>Functionality Testing
  3. 3. Usability testing
  4. 4. Interface testing
  5. 5. Compatibility testing
  6. 6. Performance testing
  7. 7. Security testing </li></ul>
  8. 8. <ul>Functionality Testing </ul><ul><li>All the links in web pages
  9. 9. Database connection
  10. 10. Forms used in the web pages for submitting or getting information from user
  11. 11. Cookie testing </li></ul>
  12. 12. Check all the links <ul><li>Test the outgoing links from all the pages from specific domain under test.
  13. 13. Test all internal links.
  14. 14. Test links jumping on the same pages.
  15. 15. Test links used to send the email to admin or other users from web pages.
  16. 16. Test to check if there are any orphan pages.
  17. 17. Lastly in link checking, check for broken links in all above-mentioned links
  18. 18. Link the product attributes to customer needs </li></ul>
  19. 19. Test forms in all pages <ul>Forms are the integral part of any web site. Forms are used to get information from users and to keep interaction with them. So what should be checked on these forms? <li>First check all the validations on each field.
  20. 20. Check for the default values of fields.
  21. 21. Wrong inputs to the fields in the forms.
  22. 22. Options to create forms if any, form delete, view or modify the forms. </li></ul>
  23. 23. Cookies testing <ul>Cookies are small files stored on user machine. These are basically used to maintain the session mainly login sessions. Test the application by enabling or disabling the cookies in your browser options. Test if the cookies are encrypted before writing to user machine. If you are testing the session cookies (i.e. cookies expire after the sessions ends) check for login sessions and user stats after session end. Check effect on application security by deleting the cookies. </ul>
  24. 24. Validate your HTML/CSS <ul>If you are optimizing your site for Search engines then HTML/CSS validation is very important. Mainly validate the site for HTML syntax errors. Check if site is crawlable to different search engines. <li>
  25. 25. </li></ul>
  26. 26. Usability Testing <ul><li>Test for navigation - means how the user surfs the web pages, different controls like buttons, boxes or how user using the links on the pages to surf different pages.
  27. 27. Web site should be easy to use. Instructions should be provided clearly. Check if the provided instructions are correct means whether they satisfy purpose.
  28. 28. Main menu should be provided on each page. It should be consistent </li></ul>
  29. 29. Content checking <ul><li>Content should be logical and easy to understand.
  30. 30. All the anchor text links should be working properly.
  31. 31. Images should be placed properly with proper sizes. </li></ul>
  32. 32. Other user information for user help <ul>Optional <li>Sitemap - should be present with all the links in web sites with proper tree view of navigation.
  33. 33. Check for all links on the sitemap.
  34. 34. “Search in the site” option will help users to find content pages they are looking for easily and quickly. </li></ul>
  35. 35. Interface Testing <ul>The main interfaces are: <li>Web server and application server interface
  36. 36. Application server and Database server interface </li></ul>
  37. 37. Compatibility Testing <ul>Compatibility of your web site is very important testing aspect. See which compatibility test to be executed: <li>Browser compatibility
  38. 38. Operating system compatibility
  39. 39. Mobile browsing
  40. 40. Printing options </li></ul>
  41. 41. Performance testing <ul>Web application should sustain to heavy load. Web performance testing should include: <li>Web Load Testing
  42. 42. Web Stress Testing </li></ul>
  43. 43. Security Testing <ul><li>Test by pasting internal url directly into browser address bar without login. Internal pages should not open.
  44. 44. If you are logged in using username and password and browsing internal pages then try changing url options directly.
  45. 45. Try some invalid inputs in input fields like login username, password, input text boxes. Check the system reaction on all invalid inputs.
  46. 46. All transactions, error messages, security breach attempts should get logged in log files somewhere on web server </li></ul>
  47. 47. Security Testing II <ul><li>Web directories or files should not be accessible directly unless given download option.
  48. 48. Test the CAPTCHA for automates scripts logins.
  49. 49. Test if SSL is used for security measures. If used proper message should get displayed when user switch from non-secure http:// pages to secure https:// pages and vice versa. </li></ul>
  50. 50. GAME OVER <ul><ul><ul><ul><li>Multumesc! </li></ul></ul></ul></ul>