Interview Questions for QA Tester. January 2. 5th, 2. Author: Prakash Nepal. Qaquestions. com is down for some time. This was their “Bible”. In some sections, I have started including the interview questions that were asked by companies to some of the candidates who visited this website and wanted to share. These questions and scenarios are based on practical experience. These were asked during my several interviews. Therefore, a person who is looking for a QA job (Quality Assurance job) can greatly benefit from this. If you are the first time job seeker as a QA person, then it can help you even better. As a consultant (or contractor), I moved to different companies in various locations in the United States. Consulting job or contracting job is such a job where an individual takes (or has to take) a job anywhere in the United States and normally, it is for a short period of time, for example, 3 months to several years. Some companies allow a contractor to work only for 1. It is their policy) and the consultant has to leave (for six months) the company no matter what.
Why Performance Testing is performed? Performance Testing is performed to evaluate application performance under some load and stress condition. It is generally measured in terms of response time for the user activity. See SWIFT Interview questions on http:// For testing training in jaipur:-Visit http:// Selenium Interview questions:-http:// Reply Delete. The most popular frequently asked Software Testing interview questions with Answers. 100+ important QA interview questions with fully solved sample answers for reference. H2Kinfosys offering best Online Training Classes for QA Testing, Big Data.Net, Selenium, Java, BA, UFT and all top IT Courses by real time professionals. Some companies allow the contractors as long as they want. Therefore, it really depends on the company policy how long you will be working. Finally, if you are attending an interview, you have to know these questions and answers by heart, must be very fluent in answering these questions. Practice in front of the mirror, loud and clear (talk to yourself). Most of the time, when we read the questions, we feel good and feel comfortable, but the reality is, at the time of the interview, even though we feel we have the knowledge, can’t express it well. This is the bitter reality. When we come out the door, we regret. If you cannot remember these by heart, trust me, it may not work. Therefore, let’s not regret. HERE ARE THE QUESTIONS: 1. Can you tell me about yourself? Answer: In my QA career, I have been working on various system platforms and operating systems like Windows 9. Windows 2. 00. 0, Windows XP and UNIX. I have tested applications developed in Java, C++, Visual Basic and so on. I have tested Web- based applications as well as client server applications. As a QA person, I have written Test Plans, Test Cases, attended walkthrough meetings with the Business Analysts, Project Managers, Business Managers and QA Leads. Attended requirement review meetings and provided feedback to the Business Analysts. I have worked in different databases like Oracle and DB2, wrote SQL queries to retrieve data from the database. As far as different types of testing is concerned, I have performed Smoke Testing, Functional Testing, Backend Testing, Black. Box Testing, Integration Testing, Regression Testing and UAT (User Acceptance Testing) Testing. I have participated in Load Testing and Stress Testing. I have written defects as they are found using Clear. Quest and Test. Director. Once the defects were fixed, retested them and if the passed, closed them. If the defects were not fixed, then reopened them. I have also attended the defect assessment meetings as necessary. In the meantime, a continuous interaction with developers was necessary. This is pretty much what I have been doing as a QA person. What did you do in your last project? In my last project, the application was a web- based application developed in Java platform. As a QA Person, I wrote Test Plans from the requirement documents and Use Cases. I performed Smoke Testing, Functional Testing, Backend Testing, Black. Box Testing, Integration Testing, Regression Testing and UAT (User Acceptance Testing). I have participated in Load Testing and Stress Testing. I attended several walkthrough meetings for requirement reviews and provided feedback to the Business Analysts. Mostly, I was in the backend testing, which required writing SQL queries directly to the database. Besides these, I wrote defects using Clear. Quest. Once the defects were fixed, retested them and if the passed, closed them. If the defects were not fixed, then reopened them. Have you written Test Plan? What does it include? Yes. What is a Test Plan? A Test Plan is a document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks and who will do each task (roles and responsibilities) and any risks and its solutions. What does it include? A Test Plan includes Heading, Revision History, Table of Contents, Introduction, Scope, Approach, Overview, different types of testing that will be carried out, what software and hardware will be required, issues, risks, assumptions and sign off section. Click here to see how a complete Test. What does it include? A Test Case is a document that describes step by step process how to test the application. A Test Case includes Test Case ID, Steps Description, Expected Output, Actual Output, Pass/Fail, Remarks. Click here to see how a complete Test Case looks like. The number 1. 10. In some companies, they use Use Cases. In some companies, they use Requirement Documents and in some companies, they use Design Document. However, in practical scenario, most of the companies have requirement document at least). This is the sample Requirement Document for Mercury Tours. How did you write the Test Cases? Yes. I have been to that kind of scenarios several times. There were companies where they had no documents at all. In that case, I had to discuss the application scenario and functionalities with the Business Analysts or developer. I kind of prepared a document in consultation with Business Analysts and Developers and then started writing Test Cases. I have written Test Cases using Use Cases. Can you tell me what a Use Case is? A use case is a document that describes the user action and system response for a particular functionality. This application is being developed by Digital Systems, Inc. The project name is Auto Parts One. However, the business owner (user) is a company called American Auto Parts of the North (imaginary name). Or. What is a Use Case and what does it include? A Use Case is a document that describes the user action and system response for a particular functionality. It includes cover page, Revision History, Table of Contents, Floe of Events (normal flow and alternative flow), Exceptions, Special Requirements, Pre- conditions and Post- conditions. Please see the Use Case: Click this link: 2. Remember, one Use Case can have many Test Cases. For example, look below: For a complete Test Case for www. This document is written by the Business Analysts. What is Software Testing Life Cycle (STLC)? The testing of software has its own life cycle. This document is the further details of the Business Requirement Document. This is a very crucial step in the SDLC. Sometimes the Business Requirement Document and Business Design Document can be lumped together to make only one Business Requirement Document. What is Code Generation or Program? Coding is the process of translating the Business Design Document into the machine readable form. If the design is done in detailed manner, the Code Generation can be done without much application. Programming tools like Compilers, Interpreters and Debuggers are used to generate the code thru different high level language like C, C++, Pascal, Java. It is created to inform project managers, testers, and developers about some key issues of the testing process. This includes the testing objective, methods of testing new functions, total time and resources required for the project, and the testing environment. The test strategy describes how the product risks of the stakeholders are mitigated at the test- level, which types of test are to be performed, and which entry and exit criteria apply. It is written by the Test Manager or Lead. The following are some of the components that the Test Strategy includes: 1 Test Levels. Risks and Mitigation. Regression Test Approach. Test Status Collections and Reporting. Test Records Maintenance. Requirements traceability matrix. Test Summary. Click here to see how the Test Strategy looks like. Are Test Plan and Test Strategy same type of document? No. They are different documents. Test Plan is a document that collects and organizes test cases by functional areas and/or types of testing in a form that can be presented to the other teams and/or customer where as the Test Strategy is the documented approach to testing. Test Plan is prepared by the tester whereas the Test Strategy is prepared by the QA Manager or QA lead. Both are important pieces of Quality Assurance processes since they help communicate the test approach scope and ensure test coverage while improving the efficiency of the testing effort. It is the preliminary test carried out by the SQA tester. Functional testing: al It is a test to check whether each and every functionality of that application is working as per the requirement. It is major test where 8. In this test, the Test Cases are . Regression testing: When a functionality is added to an application, we need to make sure that the newly added functionality does not break the application. It is also a black box type of testing. Load testing: It is a test to check the user’s response time of number of users using any one scenario (single business process) of the same application at the same time. Stress testing: In this type of testing the application is tested against heavy load such as complex numerical values, large number of inputs, large number of queries etc. OR A testing method where the application under test is viewed as a black box and the internal behavior of the program is completely ignored. Testing occurs based upon the external specifications. Also known as behavioral testing, since only the external behavior of the program is evaluated and analyzed. White box testing: It is a test where a tester looks into the code and performs the testing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2016
Categories |