I Hope it Will Help u

Q: How do you introduce a new software QA process? A: It depends on the size of the organization and the risks involved. For large organizations with high-risk projects, a serious management buy-in is required and a formalized QA process is necessary. For medium size organizations with lower risk projects, management and organizational buy-in and a slower, step-by-step process is required. Generally speaking, QA processes should be balanced with productivity, in order to keep any bureaucracy from getting out of hand. For smaller groups or projects, an ad-hoc process is more appropriate. A lot depends on team leads and managers, feedback to developers and good communication is essential among customers, managers, developers, test engineers and testers. Regardless the size of the company, the greatest value for effort is in managing requirement processes, where the goal is requirements that are clear, complete and testable.
  1. [2009/10/27] Manual Testing FAQ *2 by sonuraj (1674)
  2. [2011/03/07] Training Material for Manual Testing *5 by tella (5816)
  3. [2010/11/23] Manual Testing is Here to Stay. What do you think? Come and have your say during a brief webinar by vivekjog (985)
  4. [2011/11/16] The future of software testing Part one – Testing in production *1 by vivekjog (2742)
  5. [2010/09/16] What is a Manual testing? *4 by kprasanthkumarr (1997)