How to perform Quality Assurance testing on a program

Thanks Srinivas.B.N,

>>>>>you need to write the Test Strategy and Test Plan

This is basically what I was asking:  I need to create a generic guideline / test strategy / test plan that can be out to use in any test.

I already know that such a plan need to be compiled.  My question is: is there any school of thought as to what should be contained within this strategy?  Any guideline that shoud be followed when compiling a strategy like this?  Any orginasations dedicated to quality control?

I can figure out the basics: a test strategy would test if the business requirements are met, is the program stable and is it user-friendly.  Unfortunately, I wish that my template document / guideline is very comprehensive and detailed.

Any thoughts?

Thank you Jeroen,

That looks like a comprehensive collection of information.  I will defenitely study it carefully but it looks like exactly the type of thing what I was looking for.

I do have a lot of ideas of my own but it is always good to know what the experts, best practices,  and standards have to say about the topic.

As far as I can tell, my generic template is meant to be used by a tester only.  It will used after the developers did whatever testing they feel is necessary.  

With regards to my own idea I thought of breaking the whole thing into 3 main sections:

1 - Exceptions - this module focusses on ensuring that no exception goes unhandled and also looks at how well the exceptions are handled.  Are they reported to the user in proper manner and more importantly, are they logged with enough detail to trace and correct.  Are the logs comprehensive enough to assist with preventative maintenance.  That sort of thing.

2 - Functionality - does the application do what it is meant to do. We usually describe the requirement and proposed functionality in a document called the Business Solution Specification (BSS) which gets signed off by the client before developement commences.  This sections will focus on the functionlity of the program to ensure that all requirements are met and done so with perfect accuracy.

3 - User experience.  This will probably be the largest section.  It will deal with anything that relates to the user experience and will include very simple things like mouse cursors, icons, detailed descriptions within message boxes, spelling, tab orders etc etc etc.


I will see how much your post influences my current idea and thought process.  Should be interesting!

Thanks again!  Will post back ASAP.

roos01,

>>>>just curious based on your nick, are you Dutch/read Dutch?

No I'm not Dutch.  I am South-African.  My first language is Afrikaans which is close to Dutch....  That's where the "Pantoffel" comes from.

Thanks for the checliksts - I might need some help on the lingo etc...

Thanks for the explanation :)
Just let me know If you need further support. Though I think the basic is already covered.

regards,
Jeroen

Thanks Jeroen,

Yes I do have a lot of stuff to work through now.  I just need to filter and sort all the new information in my mind to figure out what I need to use and how to use it.

Will post back ASAP

Thanks again!

Hello PantoffelSlippers,
Any luck so far or do you need further support on this question?
regards,
Jeroen

Hi Jeroen,

I am in the process of compiling my document based on all the information provided by yourself, other experts, friends and other sources.  Sorry for taking so long.  I should be done by middle of this week and then able to close the question.

Thanks

Thanks!