Is my website test approach comprehensive enough?



  • I am working on a test automation project for a webpage portal.

    What I want to achieve is:

    1. Perform a HTML encoding conformance test; I have noticed that there are a number of missing tags, un-escaped characters and etc in its HTML.
    2. Spider this web and index all items for comparison purpose; by doing this, I can find out if a new element is added or if an element is missing.
    3. Take a snap shot of the Q&A section as I have noticed a large portion of its text is not in English. After the developers (based in a foreign country) write Q&A in English, I want to make sure texts stay in English.
    4. Click on all "link" elements, making sure they are valid, e.g. there is no 404.
    5. Implement automated tests on filling a form, inputting a password, making a choice from a drop down list and etc. (This is the bulk of this project)

    Is there any other things I am missing from my list?

    Thanks



  • Is there any other things I am missing from my list?

    You mentioned "Click on all "link" elements, making sure they are valid, e.g. there is no 404." Is that good enough? Shouldn't you check that the links actually go where they are intended to go?

    Are you checking for consistency on all the pages? Should they all have the same look & feel?

    Are you looking for missing elements? Is there a way to logout? Does Help exist? Is there a 404 page? Does the site have a favicon?

    Are you planning to perform crossbrowser testing? Performance testing? Load testing?

    What about security testing?

    Are you required to do testing of any content? Or just the "Q&A" section? What about testing for broken images?

    Do you have any formal Requirements at all that will guide some of your testing? If not, this might help: http://www.allthingsquality.com/2010/04/there-are-always-requirements.html



Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2