Testing itself does not have an objective but it has a definition:
Testing is the practice of finding something out about something.
For instance, to find out how long a piece of string is, you would apply the 'Measure with a ruler test'. The test objective here is to find out the length of a piece of string.
The super-objective here (there is no stand-alone reason to establish the length of a piece of string) could be 1. to establish wether it is the correct length to sell or 2) to establish wether it is the correct length for incorporation into some sort of component based product like a model ship for example.
Answer questions please:
Why do you need to know the objective of testing - my answer could be much less abstract if your question has more background.
What is the nature of your business?
What are you going to test?
My name is Julian PURSELL not Julian Patel. I am english - not indian (although I wouldn't mind being indian because I wouldn't have to spend so much time sunbathing in order to rid myself of my default pasty-white appearance!)
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by Prasad: What is objective of testing?
To find as much defects as possible with regard to available time, resources etc. and to ensure that your requirements are fulfilled.
This, in turn, should make you confident about the tested SW i.e you feel that you can trust it according to the requirements and agreements that may have been settled.
1. You can never prove that everything is correct.
2. You can never find all defects.