Tester interview questions and answers are completely based on the interview I and my friends attended during last years of working experience as Quality Assurance Testers. These SQA questions and scenarios are based only on real experience and were asked during actual QA interviews. Therefore, QA Tester who is looking for a Quality Assurance job will greatly benefit from this. If you are the first time job seeker as a QA Tester, then it can help you even better. Finally, if you are plant to attend an interview, you have to know these questions and answers by heart and must be very smooth in answering these questions. Practice in front of the friends or just a mirror, speak loud and clear. Most of the time, when you study the questions, you feel fine and feel relaxed, but the reality is, at the time of the actual interview, even though you feel you have the knowledge, cannot express it well. It may sound a little rough, but this is everyone’s hard experience. When you come out the interview door, you are deeply regretted. If you cannot remember these by heart, believe me, it may not work. Readers are welcome to post own questions and answers to the following SQA interview questions.

QA Manager interview questions: do we need a software QA Team?

How would you convince upper management that company needs a formal QA testing team? It is one of the common interview questions for QA Engineer with 5 years of experience or QA Manager. How would you explain that software quality would not improve if the company get rid of QA team? It sounds like a wonderful idea, instead of making the testers responsible for quality, assign the responsibility squarely on the backs of the software developers producing the software.

Developing amazing applications isn't the same as testing them, but as an experienced QA Tester, I would rather have a developers testing application than the testers who can just plainly submit bug reports. QA team needs to build quality into software development life cycle. The bug in software design is fifteen times cheaper to fix than a bug in code. QA productivity is really hard to measure. If QA team is doing testing right, everything just happens smoothly, but if the testers mess up even a little, everyone knows about it.

To be successful, QA teams must create test plans, create test harnesses, create test cases and use testing tools. QA should ensure whether the application code is effectively delivering on the business requirements provided. The developers should unit test their own code and deliver "perfectly good code", while QA testers should deliver "code that actually addresses business needs". For a company that makes software applications, a rock-solid QA department is absolutely irreplaceable.
0 comments
Labels:

How Google Tests Software - Book Review

How Google Tests Software book presents diverse insight into Google approaches and methodologies for software testing Google. Engineering Director James Whittaker and two Google testing experts have teamed up to outline best practices for testing and delivering software at scale based on personal trails and errors in Google.

The authors describe the life of Software Engineers in Test and Test Engineers at Google and how the company blends development and testing together. The book will explain the benefits of breaking down types of testing into three broad categories that include both manual and automated testing and how the selection of manual or automated testing depends on what is being tested. The reader would get a solid foundation for making decision about proper testing infrastructure, timely code reviews, organizing staging environments, deploying software with continuous builds and configuring production monitoring.

How Google Tests Software book provides perspectives on the application of Google proven approaches with a nice balance of stories, process, and test techniques. The book will help QA Testers become more effective and more efficient in testing endeavors.

How Google Tests Software book provides perspectives on the application of Google proven approaches with a nice balance of stories, process, and test techniques. The book will help QA Testers become more effective and more efficient in testing endeavors. In case you dream to work as QA Tester for Google, I would recommend to get this book together with The Google Resume: How to Prepare for a Career and Land a Job at Apple, Microsoft, Google, or any Top Tech Company book. In this case one book will help you to improve your QA skills, while another would help to polish your resume and prepare for Google interview.

Book Details:

Title: How Google Tests Software
Authors: James A. Whittaker, Jason Arbon, Jeff Carollo
Publisher: Addison-Wesley Professional
Pages: 272
ISBN 10: 032180302717401
Print ISBN 13: 978-0321803023

Related books reviews and recommendations

0 comments
Labels: ,

Selenium Interview Questions

IT interviews usually start with behavioral interview questions like “tell me about yourself” and end with a questions from a candidate. The interviews for Selenium QA Egineer position are not different, except that in the middle the prospective tester should be prepared to answer on the technical Selenium interview questions. Unfortunately the job seeker has no control over what interview questions will be asked by hiring QA Manager or QA Tester. The good news that IT interview is not a contest to check who answers most questions right the shortest amount of time. The interview is about convincing the prospective employer that only you are good fit for the company and only you can get the job done. Having said that, there are definitely some common Selenium interview questions that you can be reasonably assured to get and the answers can make the deal or sent you back home. In the preparation for an interview I would recommend to read Selenium Testing Tools Interview Questions book. The book has 175 interview questions with answers covering Selenium IDE, Selenium RC, Selenium Grid and Selenium WebDriver.



The best idea would be to practice answering the questions from the book on your own. In addition to polishing verbal questions, be ready to actually show how to use Selenium on machine or write the code. It could be enough for beginner tester to show how to record script with Selenium-IDE and resolve issues exposed when play-back doesn’t exactly do what the recodrding identified, but QA Tester with 2 years of experience should be ready to write the code in Selenese, Java, Python, PHP on the whiteboard. The ideal candidate should be able launch a Selenium-RC or WebDriver project, develop a test script, commit the code to the version control system, and successfully add the script to preexisting continuous integration server.

Last thing to remember, don’t limit your interview preparation to Selenium only. All Selenium interviews for tester position will include common software quality assurance interview questions, and the interviewer will ask the QA tester about programming languages, technologies, frameworks listed in the testers resume.
0 comments
Labels:
Subscribe to: Posts (Atom)

Common QA Tester interview questions