Interesting Video on Exploratory Testing

Friends,

I found an interesting video on Exploratory Testing in you tube and thought of sharing with you. :)

Go through it.. damn gud

Documentation Testing

From the childhood we are used to learn things from books. Hope all of you agree with me. :)

The enthusiasm in leaning new things will grow in us as we growup.

In this software era, how will we be learning about the softwares which hits our eye attention?

Documentation (ofcourse Soft copy of the BOOK again) helps us in doing this.

The Basic three questions which come into our mind when we think of Documentation testing:

What is Documentation?

Why should it be tested?

How should it be tested?

The general user's perspective:

Say One of my hobby is photo editing.

Hey!!! There is a new software, photo editer 1.0 released into the market with all good features like adding Beautiful frames to our image,making the image more attractive with different special effects etc.. and now i can create an album of my own and suprise everyone with my new album..

Now there comes many questions to the users mind.

How should i install this software? "Installation guide" helps me in doing this

oh great installation is successful :) but now...

How should i use it?? "Product Documentation/Help"

wow here this product has a very big documentation.. i think every feature is explained clearly..

and they had a search feature also..

let me check on "how to add frame to my photo".

hey its very clear and easy to use.. now let me try the remaining features..search -> Special effects to the photo.

kool my album is ready with all what i have expected.. All Happies!!!!! :D

Here ends the story of User.

While using the Software, the user does not think on who had developed the software and how did he develop it.. he just thinks of "HOW CAN I USE THIS?" to put it in other words "HOW IS THIS SOFTWARE USEFUL TO ME?"

This is the general tendency of the End User.

It might be a simple software like picasa, vlc media player or complex softwares like Java, any Business softwares..the user will just check how userfriendly and useful it is for him or his Business?

Finally the only thing that matters for us is "Customer/EndUser Satisfaction"

Regarding testing of Documentation:

The test engineers should keep in mind the following things:

User Perspective:

• Whether the user who does not have any idea on the product but wants to try it will be able to use the software easily with the documentation help provided?
• Are there any broken links in the documentation? etc..

Product Perspective:

• Did we document all the features that our product has? so that end user can make use of it use it fully.

Documentation should be tested thouroughly, as this also plays a primary role in selling the software/Gaining the user attention.