How to prepate for the Manual Testing Interview?
How to prepare for the Manual testing ? What all the concepts needed to be covered?
Is it necessary to learn QTP and automation concepts for the manual testing job?
Just clearly study the basic concepts of SDLC and study about the test cases, test strategy, scenarios and all.
QTP and Automation Concepts will be an added advantage.
I think this book, "A Practicioner's guide to testing" by Lee Copeland, is a good prep for manual testing career.
It goes over a wide rage of testing topics..
* Test Coverage
* Risk analysis
* techniques for coming up what should tested, and what could be omitted.
* alot of testing theory.
* a lot on testing process
* advantages and disadvantages of testing types and coverage techniques.
There is a course called E-mastering test design. In my previous Mgmt position I had my people take it. As part of the package, the book referenced above was included and it was cool because now and then I would see my folks going to the book for reference.
Every company is different. Most companies wouldn't require "Manual Testers" to know test automation or QTP, but you never know for sure.
Originally Posted by uskvl
These might help:
IME, many manual testing positions will require some programming knowledge, even if they are not working in automated tests.
These days, any Web Testing position will require a little above basic SQL (select, joins, and aggregate queries, but not so much in indexing, DB admin, and normalization techniques)
Software engineering concepts are important before testing interview.
Thanks for sharing
Originally Posted by dlai
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.
First basic thing – Testing Concepts: One needs to be very good at this especially the manual testing methodologies. But only knowing different testing concepts is half work done. The next – most important thing is to know which type/technique/concept of testing can be applied at what stage of SDLC.