Skip to content

Documentation Testing

I had tested a product before a year ( Beta tester ) and the product was released to the customer. After a year, I was invited to be beta tester again. There were documents which conveyed what has been changed from the last year. After testing those changed modules other testers said it is ready for release. But, I thought why the test cases did not involve any testing related to Help Documents ( You see how test cases can affect your testing activity ).

What happened was when test team got the requirement document there were only feature changes that have been done.  Then I looked into the Help & Documentation, and I was completely shocked by seeing different content which was not related to the product.

It said, to register you need to click on “Member” -> “Register”. But, there was no menu which included it. As there was feature change it has been wiped out and it was “Community” -> “Sign up”.

So the purpose of Help Documentation was completely in vain. I reported this to the product owner and he was shocked too that how test cases did not find this because test cases were written on changed requirement documents.

Tips for Documentation Testing

  1. Spell & Grammar check
  2. Claim Testing – What is in the help document is in the feature
  3. Checking if there is some feature in help document but it is not in the product
  4. And many other things that you can think of

 

Tips for improving your testing activity

  1. Learn Exploratory Testing
  2. Learn different skills
  3. Give freedom to tester to test using his / her test ideas
  4. Learn Session Based Test Management

 

Thanks for your time in reading this blog post.

SanthoshTuppad

I have been as a software tester for over 5 years. I am a hands-on tester and I've been winning bug battles & testing competitions across the world. I am a testing enthusiast, who conducts free workshops on security testing across India (Covered locations: Bengaluru, Pune, Hyderabad & Chennai. Invite him to come to your location), and monthly meets for testers in Bengaluru. I am also an avid testing blogger.

My interests include traveling, driving my SUV, health & fitness and many others. I mentor budding entrepreneurs, testers, teams in any profession.

Latest posts by SanthoshTuppad (see all)

Share/Bookmark

2 Comments

  1. Mohit Verma wrote:

    once again Nice share.

    Its a co-incidence that you have publish this post when I am also reviewing the user manual of a product on which I am working.

    I am agree what you have said. It generally happens that we test all the changes in the application but forget to review/update the manuals and other documents. To avoid all these mis-happenings, there should be a proper change control process.

    With Regards
    Mohit

    Thursday, April 22, 2010 at 12:59 am | Permalink
  2. @Mohit,
    Agreed. If you consider freshers in the way they are trained by these institutes, they do not know about all this. But, the only Indian Tester who coaching is excellent ( These words are not enough to tell about him ) when it comes to train freshers or testers. India needs many Pradeep Soundararajan’s and slowly there is a change happening.

    Thanks,
    Santhosh Shivanand Tuppad

    Thursday, April 22, 2010 at 1:51 am | Permalink

Post a Comment

Your email is never published nor shared. Required fields are marked *
*
*