I guess you missed the FAQs you were supposed to read when signing up.
One of the key things is to perform a search to see if your questions have already been addressed in other threads, which in this case they have. On the same page of posts as well. With pretty much the same name......here
Although it sounds like you are completely new to testing and QA. You might want to consider taking some time and reading the various information and points of view that are given through this site. It will help you develop your own opinions and knowledge base of what QA/ QC/ Testing, etc is and can be. Not doing the legwork on your end is a bad sign of someone in the industry as expecting the answers to be handed to you is a sorry state to start working in the field. Dig into it, search for answers through books and on the Internet. Go for it - it won't hurt.
Insanity: doing the same thing over and over again and expecting different results
In my view following are QA processes
1. "Spec (Use Case/Form Spec) should be baselined before ur testing start" will come under QA.
2. Testing should start from Initial phase of SDLC
3. We should do regression testing with new feature testing in a new iteration
4.A Test Case should be added against Defect logged if there is not already any scenario in the Test Case so that it can be blocked further iterations.
[Test Case should not be written untill the use cases are baselined... although there r the cases when test cases are written even the docs are not baselined...i know it may sound..i am asking or telling. actually the problem is it i know the processes but the problem is that which one will come under QA/QC?]
Why does it matter which it comes under, as long as all the tasks are accomplished? What is driving the issue to make you differentiate between QA/QC?
Originally posted by om.vikas: actually the problem is it i know the processes but the problem is that which one will come under QA/QC?]
<font size="2" face="Verdana, Arial, Helvetica">What is the rest of the story here? Why is it a problem for you not to know which label the process falls under? Will it affect execution of the process?
Using classic definitions...
QA consists of, QA planning to include how the below will be handled:
Deployment and Production Control
(just to name a few areas)
Notice that testing is under the overall umbrella, listed as Verification/Validation. Under that, one can usually find all the types, levels, and categories of testing.
Finally, to quote Darrel:
"Why does it matter which it comes under, as long as all the tasks are accomplished? What is driving the issue to make you differentiate between QA/QC?"
Without detailed context from you, it is difficult to propose to you something that might best fit your world and situation.