What is the responsibility of programmers vs QA?
Answer Posted / uttara
QA is responsible for "Process Quality" and Programmers are
responsible for "Product Quality".
Both work hand in hand where QA would be working to ensure
that the processes used for developing the product ensure
that the developed products are of high quality.
Programmers have to used these processes effectively so
that they end developing a high quality product.
Processes are the "ways" to produce a quality product.
Processes are owned by QA.
Programmers are supposed to "implement"
the "processes/ways" objectively so that they can produce a
high quality product.
Any issues/area of improvement found during execution
of "process" by the programmers should be communicated back
to the QA so that they can improve/fine tune the process
for future use
| Is This Answer Correct ? | 0 Yes | 1 No |
Post New Answer View All Answers
What are the differences between test strategy and test plan?
What are the different levels in software testing?
What is basic block?
What are the advantage and disadvantages of automated testing?
What are verification and validation and difference between these two?
You have 250 outstanding requests in a bug tracking application,you have no automated build environment, or representative production environment in test, nor the hardware required.You are responsible for establishing some kind of process and order to the QA department, what would you need in terms of budget and what would your processes be, as well as how would you address the environment issues mentioned above?
Is it possible to do load testing in POWERMHS? If yes how do you do that?
Describe use case testing?
Please, list many things You’ll do (effort) as a SQA Tester, in this Company software project from the idea making of the specification, till that software released!
Define bug leakage and bug release?
Mention the different types of software testing?
a proj ws atarted and cloded within the second day why?it has good amt of resources.srs ws prepers and accepted by the client too.
what documnets qa engineer need for starting qa?
What is specification-driven testing?
What are the dimensions of the risks?