Question { HCL, 11932 }

what is mean by testing process ?

Answer

Testing is often confused with the processes of quality
control and quality assurance. Testing is the process of
creating, implementing and evaluating tests. If you are
shopping for a new television, you can call that process
"testing for the best TV for you"... it's kind of
pretentious, but that is what you're doing as you compare
prices and features to find what will work best for you.
Testing usually has a limited scope and duration – you're
just looking at TVs and only in your town, you're not going
to spend a year shopping, are you?
Testing is predicated on the use of a standard of quality:
you have a specification of what's allowable (no broken
links? ALT tags have values? Maximum page weight is 10K?)
and you compare the site to the standard, noting deviations
and shortcomings. This seems simple, but your testing is
only valuable if your standard of quality is comprehensive,
well thought-out, and reasonable. If your standard has
holes, then your testing process has blind spots.
Quality control is a refinement of testing, involving the
formal and systematic use of testing and a precise
definition of what quality means for the purposes of the
test. You aren't just testing; you are testing and then
doing something with the results. Quality control is used
for testing a product or output of a process, with the test
measuring the subject's ability to meet a certain benchmark
or threshold of quality. The tests usually take the form of
"does this product meet requirement X?", and are often
pass-fail.

Question { 4812 }

Is the build or version number change during retesting

Answer

Yes, the build needs to fix for all the patches with a new
version release in order to track record of previous bugs.