It is a basically the way we look to it a software programmer brings the product for demonstrating the program. So, what the person does is the test set, he will be running the program with the help of the test set to ensure or to show it is a functionally product can do something jobs. It is a basically functional testing, which means, it is some sort of a black-box testing, we are looking to.
So, here the program, what the programmer does is, he would like to show the program runs during the functional testing. And it solves the required problems in the right working environment.
Often the test is taken from the working environment and would ensure the program runs. So, from that point of view it is not a thorough testing.
Using the test set the software functioning is a demonstration.
There are no guidelines of how to obtain the test set. This is left to the programmer, often the person will be using a domain relevant or test set. One must realise the software does not pay you for use that domain relevant or test sets. But, what we call domain relevant from the environment the no sort of a test set should be useful but sort of a data would be going into the program. And if you try to provide that sort of a data the system is not likely to fail. However, when you try to do certain things beyond those specified norm, specified environments, that is where the problems will be coming. So, I this does not really tell us how to test those things.
Programs test select data could be biased, that is another one.
Now, finally one must say, quality of the software depends upon the quality of the set, the test set. So, because the programmer for demonstration purposes makes use of a limited test set, the quality is not likely to be very good.