Interview Q&A

Question 0

What is a Test Plan?

Answer 0

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.

It includes:

• Heading
• Revision History
• Table of Contents
• Introduction
• Scope
• Approach
• Overview
• Types of testing
• Types of software and hardware
• Roles
• Issues
• Risks
• Assumptions
• Sign off section

Question 1

What document did you refer to write the Test Cases?

Answer 1

Requirement document. (NOTE: It can also be Use Cases, or Design Document)

Question 2

What would you do in a situation where you did not have any documents (no requirement document, no Use Cases, or no Design Document) and you had to write the Test Cases?

Answer 2

In that situation, I would discuss the application scenario and functionalities with the Business Analysts or developer. Prepare a document based on their feedback, review it with them then start writing the Test Cases.

Question 3

What is a Use Case and what does it include?

Answer 3

A Use Case is a document that describes the user’s action and the system’s response to that particular functionality.

It includes:

• Cover page
• Revision History
• Table of Contents
• Flow of Events (normal flow and alternative flow)
• Exceptions
• Special Requirements
• Pre-conditions
• Post-conditions

Question 4

What is Software Development Life Cycle?

Answer 4

The Software Development Life Cycle is a process that ensures good software is built. It is a conceptual model used in project management that describes the stages involved in an information system development project, from an initial feasibility study through maintenance of the completed application.

Each phase in the life cycle has its own process and deliverables that feed into the next phase. There are typically 5 phases starting with the analysis and requirements gathering and ending with the implementation.

It includes the following different stages:

1. Requirement phase
2. Design phase
3. Coding (programming)
4. Testing
5. Release (Production)
6. Maintenance (Support)

Question 5

What is Business Requirement Document (BRD)?

Answer 5

It is a document that describes in detail the functionalities that the user requires in the application. This document is written by the Business Analysts.

Question 6

What is Business Design Document?

Answer 6

It is the document which describes the application functionalities of the user in detail. 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.

Question 7

What is Software Testing Life Cycle (STLC)?

Answer 7

Software Testing Life Cycle (STLC) is a sequence of steps that are carried out in order to validate the software:

1. Requirement Analysis
2. Test Planning
3. Test Case Development
4. Review the Test Cases
5. Test Execution
6. Bug logging and tracking
7. Close or Reopen bugs

Question 8

What is Code Generation or Program?

Answer 8

It’s the process of translating the Business Design Document into it’s machine readable form via coding. Programming tools like Compilers, Interpreters and Debuggers are used to generate the code thru different high level language like JavaScript, C++, Pascal.

Question 9

What is a Module?

Answer 9

A ‘Module’ is a software component that has a specific task. It can be a ‘link’ which can go inside to its component detail.

Question 10

What is meant by Walk-thru meeting?

Answer 10

Before start working in a module and/or after accomplishing the testing of a module, the tester calls a meeting to disseminate his findings or to share his queries to other tester or leads of the company working on the same application that is called the Walk-thru meeting.

Question 11

What is Build?

Answer 11

A build is only a portion of the software that is collection of different modules in a single folder.

In other word, the developers put their code in the shared location (folder) and all those code (modules) are combined together so that it is a complete application that works.

This is put together by the Configuration Management Team (CMT)

Question 12

What is meant by the Build Deployment?

Answer 12

When the Build so prepared by the CMT is sent to different Test Environments, it is called the Build Deployment.

Question 13

What is Test Strategy?

Answer 13

A test strategy is an outline that describes the testing portion of the software development cycle. 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.

Question 14

What does the test strategy describes?

Answer 14

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. (source: Wikipedia)

Question 15

Who creates the test strategy?

Answer 15

It is written by the Test Manager or Lead. It is created based on development design document.

Question 16

The following are some of the components that the Test Strategy includes:

Answer 16

It includes introduction, scope, resource and schedule for test activities, acceptance criteria, test environment, test tools, test priorities, test planning, executing a test pass and types of test to be performed.

Question 17

Are Test Plan and Test Strategy same type of document?

Answer 17

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.

Question 18

Unit testing?

Answer 18

It is a test to check the code whether it is properly working or not as per the requirement. It is done by the developers (Not testers).

Question 19

Shakeout testing?

Answer 19

This test is basically carried out to check the networking facility, database connectivity and the integration of modules. (It is done by the Configuration Team, Not testers).

Question 20

Smoke testing?

Answer 20

It is an initial set of test to check whether the major functionalities are working or not and also to check the major breakdowns in the application. It is the preliminary test carried out by the SQA tester.

Question 21

Functional testing?

Answer 21

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 80% of the tests are done. In this test, the Test Cases are ‘executed’.

Question 22

Integration testing?

Answer 22

It is a test to check whether all the modules are combined together or not and working successfully as specified in the requirement document.

Question 23

Regression testing?

Answer 23

When a functionality is added to an application, we need to make sure that the newly added functionality does not break the application. In order to make it sure, we perform a repeated testing which is called Regression Testing. We also do regression testing after the developers fix the bugs. See the video below for more understanding. (Courtesy of guru99.com).

Question 24

System testing?

Answer 24

Testing which is based on overall requirements specification and it covers all combined parts of a system. It is also a black box type of testing.

Question 25

Load testing?

Answer 25

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.

Question 26

Stress testing?

Answer 26

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. which checks for the stress/load the applications can withstand.

Question 27

Performance testing?

Answer 27

It is a test to check the user’s response time of number of users using multiple scenarios (multiple business process) of the same application at the same time.

Question 28

User acceptance testing?

Answer 28

In this type of testing, the software is handed over to the user in order to find out if the software meets the user expectations and works as it is expected to.

Question 29

Black box testing?

Answer 29

It is test where a tester performs testing without looking into the code. 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.

Question 30

White box testing?

Answer 30

It is a test where a tester looks into the code and performs the testing.

Question 31

Alpha testing?

Answer 31

In this type of testing, the users are invited at the development center where they use the application and the developers note every particular input or action carried out by the user. Any type of abnormal behavior of the system is noted and rectified by the developers.

Question 32

What is Negative Testing?

Answer 32

When we test an application by putting negative values (instead of actual values), then the system should not allow the other values rather than the actual value. The system should give an message that the value is not correct.

Question 33

Beta testing?

Answer 33

In this type of testing, the software is distributed as a beta version to the users and users test the application at their sites. As the users explore the software, in case if any exception/defect occurs that is reported to the developers.

Question 34

What is Change Control (OR Change Request)?

Answer 34

It is a document that describes the additional functionalities that are added after the Business Requirement Document is signed off. It can be updated in the old business requirement document or it can be a separate document.

Question 35

Backend Testing?

Answer 35

It is a test to check whether the data displayed in the GUI front end report format matches with the particular data in the original database.

Question 36

What do you do on your first day of the work?

Answer 36

On the first day, normally, we will be given a computer and support people will set up the User Name and Password for the computer. If that is done already, then the QA Lead or QA Manager will give me a brief walk through of the documents (which documents are where), introduce to different team members (normally to the ones you will be working with). Then your boss will ask you to step into work what needs to be done. However, the first thing normally is, they will ask you to read the documents available for that project.

Question 37

Are you better working in a team or working alone?

Answer 37

I am a team player. I get along with team members very well. As far as the working is concerned, I can be equally productive in team or working alone.

Question 38

Where do you see yourself in another 5 years?

Answer 38

I see myself a QA Lead in another 5 years.

Question 39

How do you determine what to test in an application?

Answer 39

First of all we have the test cases (or test scripts) that are written based on the requirement document. This pretty much covers what functionalities to test. Therefore, looking at the test cases tells us what to test in the application.

Question 40

What do you do once you find a defect?

Answer 40

Look in notebook.

Question 41

38. What are the basic elements you put in a defect?

Answer 41

Basic elements we put in a defect are: SEVERITY, PRIORITY, CREATED BY, VERSION NO, HEADER, DESCRIPTION OF THE DEFECT where we write how to recreate a defect, in what module the defect is found, Status, and so on.

Question 42

When should testing start in a project? Why?

Answer 42

We should start testing as soon as the following things are ready:
-Test Data are ready
-Build (all the developers have
  coded their code and merged
  them together)
-Test Environment (servers, network
  etc) is set up and ready
-When the manager asks us to go
  ahead and start testing.

Question 43

What are all the basic elements in a defect report?

Answer 43

The basic elements in a defect report are: Defect ID, Header, Description, Defect Reported by, Date, Status, Version, Assigned to, Approved by, Module where the defect was found and so on.

Question 44

What are the types of test cases that you write?

Answer 44

We write test cases for smoke testing, integration testing, functional testing, regression testing, load testing, stress testing, system testing and so on.

Question 45

How to write Regression test cases? What are the criteria?

Answer 45

Regression test cases are also based on the requirement documents. They are written more into detail and with every release (build), the testers need to do regression testing.

The criteria for regression testing are; there should be no major defects while we do our smoke test and functional testing.

Question 46

What is Test Harness?

Answer 46

“In software testing, a test harness or automated test framework is a collection of software and test data configured to test a program unit by running it under varying conditions and monitor its behavior and outputs. It has two main parts: the test execution engine and the test script repository.” (Definition from www.wikipedia.org)

Question 47

How to write User Acceptance Test plan?

Answer 47

The way of writing Test Plan and Test Cases is the same in all the test phases. However, specifically for User Acceptance Testing, the testers use data nearly real data (meaning that the data is very much similar to the production data or real data). (qaquestions.com)

Question 48

What is the Waterfall methodology?

Answer 48

It is sequential design process. Where Development flows sequentially from start point to end point, with several different stages: Conception, Initiation, Analysis, Design, Construction, Testing, Implementation, and Maintenance.

Question 49

What is a Test Case

Answer 49

In it’s simplest definition a test case as a set of step-by-step instructions to verify something behaves as it is required to behave.

It often contains:

• Title
• Description
• Test steps
• Expected result
• Actual result (Once tested)

Atest case is a set of conditions or variables under which a tester determines whether the software satisfies requirements and functions properly.

A test case is a single executable test which a tester carries out. It guides them through the steps of the test.

Question 50

What is the Agile methodology?

Answer 50

It is based on an incremental and iterative approach to software design. Allowing developers freedom to respond to changes in requirements as they arise. It is made up of scrum teams ; it’s carried out in sprints.

Question 51

What’s the difference between a Test Case and a Test Scenario?

Answer 51

Test Scenario
The purpose of scenario testing is to test the end-to-end functionality of a software application and ensure the business processes and flows are functioning as needed. In scenario testing, the tester puts themselves in the users shoes and determines real world scenarios (use-cases) that can be performed. Once these test scenarios are determined, test cases can be written for each scenario. Test scenarios are the high level concept of what to test.

Test Case
A test case is a set of steps to be executed by the tester in order to validate the scenario. Whereas test scenarios are derived from use-cases, test cases are derived and written from the test scenarios. A test scenario usually has multiple test cases associated with it, as test cases layout out the low-level details on how to test the scenario.

Example
Test Scenario: Validate the login page
Test Case 1: Enter a valid username and password
Test Case 2: Reset your password
Test Case 3: Enter invalid credentials

Question 52

User Story

Answer 52

User storiesare short descriptions of functionality told from the user’s perspective. Thefocus is on why and how the user interacts with the software. A user story is essentially a high-level definition of what the software should be capable of doing. Typically, any feedback or request that comes from the business or end-user can be written as a user story.

A good userstoryis written in simple language and speaks to the reason and anticipated benefits of a specific areaof the software. They usually follow a template like this:
As a , I want so that .
Here’s an example of a user story for a basic e-commerce site:
As a customer, I want to be able to view the items in my cart so that I know for sure what I’m purchasing.

Acceptance criteria often accompanies the user story. Thesecriteria are the boundaries of the user story (feature) and they essentially determine when the user story is competed. Acceptance criteria is also what the tester will write/conduct their tests against. You can think of acceptance criteria as the functional requirements that support a user story.

Question 53

What Is A Requirement?

Answer 53

Traditional requirements describehow the software should act. The intent of the system is the main focus.Requirements documents go into great detail on how an area of software should work. They typically serve the purpose of guiding how the software team will build something.
While user stories are plain and simple, requirements documents go into a lot of detail and take a good amount of time to write. Requirements documents often contain things like executive summaries, scope, risks, and more. Theyset the level of quality forfunctionality, performance, and user experience.
Here’s an example of a few requirements for a basic e-commerce site:
Display the name of each item in the shopping cart.
Display the quantity of each item in the shopping cart.
Allow the user to remove any items in the shopping cart.

Question 54

Difference between User Story & Requirement

Answer 54

In general, user stories are morecommonly used within agile methodology,whilerequirements documents aremore commonly associated with the traditional waterfallmethodology.
Due to the light nature of user stories, they promote more discussionand collaboration than requirements documents. As you can see in the above examples, requirements lay out specific detail while the user story example leaves room for discussion. These discussions may take place prior to or within the planning session. As we discussed in a previous post,the entire team (including QA) should be involved in this discussion.
With requirements docs, the greater details are already fleshed out. It’s pretty rare for a developer to append or modifyrequirements documents.
By the timesoftwareis implemented per a formal requirements document, the actual requirements may have changed. With user stories, anyone should be able to contribute to the user story backlog at any time. This couldbe a developer raising issues on technical debt, the client requestinga new feature, or a tester who has noticed a UX issue. The backlog isa collaborative effort and therefore ensures the work being done aligns with the customers needs.