Manual Testing Interview Questions Asked

8/10/2019 Manual Testing Interview Questions Asked

1/13

Manual Testing Interview Questions Asked @ MindTree Company Name: MindTree

Sent By: Pradhan (QA Engineer)

Interview Questions:

1. Tell me about yourself ?2. Explain about your Current Project and Roles & Responsibilities ? 3. Which Model Following in Your Current Company and Explain About V-Model ?

Answer :V- model means Verification and Validation model. Just like the waterfallmodel, the V-Shaped life cycle is a sequential path of execution of processes. Eachphase must be completed before the next phase begins. Testing of the product isplanned in parallel with a corresponding phase of development.

The various phases of the V-model are as follows:

Requirements like BRS and SRS begin the life cycle model just like the waterfall model. But,in this model before development is started, a system test plan is created. The test plan

focuses on meeting the functionality specified in the requirements gathering.

The high-level design (HLD) phase focuses on system architecture and design. It provideoverview of solution, platform, system, product and service/process. An integration test planis created in this phase as well in order to test the pieces of the software systems ability to
http://softwaretesterjob.blogspot.com/2013/03/manual-testing-interview-questions.htmlhttp://softwaretesterjob.blogspot.com/2013/03/manual-testing-interview-questions.htmlhttp://2.bp.blogspot.com/-4TOVGNVT9-Q/UHRWf6dkSbI/AAAAAAAAAGU/3NLatqxNrXY/s1600/V-Model+(1).jpghttp://softwaretesterjob.blogspot.com/2013/03/manual-testing-interview-questions.html


2/13

work together.

The low-level design (LLD) phase is where the actual software components are designed. Itdefines the actual logic for each and every component of the system. Class diagram with all

the methods and relation between classes comes under LLD. Component tests are created inthis phase as well.

The implementation and Coding phase is, again, where all coding takes place. Once codingis complete, the path of execution continues up the right side of the V where the test plans

developed earlier are now put to use Execution.

4.What is the Difference between Verification and Validation ?Read Answer:

Verification : Are we building the product right?Validation: Are we building the right product?

Verification is to check whether software conforms to the specifications and is done bydevelopment team at various development phases.During development phase the SRSdocument ,Design Document and the code are reviewed to ensure that product is beingdeveloped using the process oriented approach.It is an in-house activity ofthe development organization. It is an Quality assurance activity which prevents the defects ofthe product.

Validation is to check whether the software meets the customer's expectation.This is done bytesting the software for its functionality and other requirements as mentioned in RequirementsSpecification Documents.Validation is carried out with customer involvement.It is Qualitycontrol acitvity which detects the defect during testing of the product5. What Should be done After a Bug is Found?

Read Answer: When a bug is found, it needs to be communicated and assigned todevelopers to fix it. After the problem is resolved, fixes should be re-tested.

Additionally, determinations should be made regarding requirements, software, hardware,safety impact, etc., for regression testing to check the fixes didn't create other problemselsewhere.

For Datailed Bug Lifecycle :

Defect: A fault in a program, which causes the program to perform in an unintended orunanticipated manner.

Defect Life Cycle (Bug Life cycle) is the journey of a defect from its identification to itsclosure. The Life Cycle varies from organization to organization and is governed by thesoftware testing process the organization or project follows and/or the Defect tracking toolbeing used.


3/13

1) New: When QA files new bug.

2) Assigned: Assigned to field is set by lead or manager and assigns bug to developer.

3) Could not reproduce: If developer is not able to reproduce the bug by the steps given inbug report by QA then developer can mark the bug as CNR . QA needs action to check if bugis reproduced and can assign to developer with detailed reproducing steps.

4) Need more information: If developer is not clear about the bug reproduce steps providedby QA to reproduce the bug, then he/she can mark it as Need more information . In this caseQA needs to add detailed reproducing steps and assign bug back to dev for fix.

5) Deferred: If the bug is not related to current build or can not be fixed in this release orbug is not important to fix immediately then the project manager can set the bug status asdeferred.

6) Rejected/Invalid: Some times developer or team lead can mark the bug as Rejected orinvalid if the system is working according to specifications and bug is just due to some

misinterpretation.

7) Resolved/Fixed: When developer makes necessary code changes and verifies thechanges then he/she can make bug status as Fixed and the bug is passed to testing team.

8) Reopen: If QA is not satisfy with the fix and if bug is stil l reproducible even after fix thenQA can mark it as Reopen so that developer can take appropriate action.

9) Closed: If bug is verified by the QA team and if the fix is ok and problem is solved then QA
http://www.buzzle.com/images/diagrams/software-testing/dfc-defect-life-cycle.jpg


4/13

can mark bug as Closed . 6. What if the Software is so buggy and it can't be Tested at all?Read Answer : In this situation the best bet is to have test engineers go through the processof reporting whatever bugs or problems initially show up, with the focus being on critical bugs.Since this type of problem can severely affect schedules and indicates deeper problems in thesoftware development process, such as insufficient unit testing, insufficient integration testing,

poor design, improper build or release procedures, managers should be notified and providedwith some documentation as evidence of the problem.

7. What if there isn't enough time for thorough Testing?Read Answer:

Use risk analysis to determine where testing should be focused. This requires judgment skills,common sense and experience. The checklist should include answers to the followingquestions:

o Which functionality is most important to the project's intended purpose?o Which functionality is most visible to the user?o Which functionality has the largest safety impact?o Which functionality has the largest financial impact on users?o Which aspects of the application are most important to the customer?o Which aspects of the application can be tested early in the development cycle?o Which parts of the code are most complex and thus most subject to errors?o Which parts of the application were developed in rush or panic mode?o Which aspects of similar/related previous projects caused problems?o Which aspects of similar/related previous projects had large maintenance expenses?o Which parts of the requirements and design are unclear or poorly thought out?o What do the developers think are the highest-risk aspects of the application?o What kinds of problems would cause the worst publicity?o What kinds of problems would cause the most customer service complaints?o What kinds of tests could easily cover multiple functionalities?o

Which tests will have the best high-risk-coverage to time-required ratio?

8. Who will be the Good Tester? Read Answer :

o Good tester takes the customer s point of view. he should be tactful and diplomatic. o He should have a test to break attitude, a strong desire for quality, an attention to

detail, and good communication skills, both oral and written.o Previous s/w development experience is also helpful, as it provides a deeper

understanding of the s/w development process.

9. Explain About Software Testing Life Cycle ?Read Answer :

Software Testing Life Cycle (STLC) defines the steps/stages/phases in testing of sof tware.

The different stages in Software Testing Life Cycle:


5/13

o Requirement Analysiso Test Planningo Test Case Design / Developmento Environment setupo Test Execution / Reporting / Defect Trackingo Test Cycle Closure / Retrospective study

1) Requirement Analysis During this phase, test team studies the requirements from a testing point of view to identifythe testable requirements. The QA team may interact with various stakeholders (Client,Business Analyst, Technical Leads, System Architects etc) to understand the requirements indetail. Requirements could be either Functional (defining what the software must do) or NonFunctional (defining system performance /security availability ) .Automation feasibility for thegiven testing project is also done in this stage.

Activities

o Identify types of tests to be performed.o Gather details about testing priorities and focus.o Prepare Requirement Traceability Matrix (RTM).o Identify test environment details where testing is supposed to be carried out.o Automation feasibility analysis (if required).

Deliverables

o RTMo Automation feasibility report. (if applicable)

2) Test Planning

This phase is also called Test Strategy phase. Typically , in this stage, a Senior QA managerwill determine effort and cost estimates for the project and would prepare and finalize the TestPlan.

Activities

o Preparation of test plan/strategy document for various types of testingo Test tool selectiono Test effort estimationo Resource planning and determining roles and responsibilities.o Training requirement

Deliverables

o Test plan /strategy document.o Effort estimation document.

3) Test Case Design / Development

This phase involves creation, verification and rework of test cases & test scripts. Test data , isidentified/created and is reviewed and then reworked as well.


6/13

Activities

o Create test cases, automation scripts (if applicable)o Review and baseline test cases and scriptso Create test data (If Test Environment is available)

Deliverables

o Test cases/scriptso Test data

4) Test Environment Setup

Test environment decides the software and hardware conditions under which a work product istested. Test environment set-up is one of the critical aspects of testing process and can bedone in parallel with Test Case Development Stage. Test team may not be involved in thisactivity if the customer/development team provides the test environment in which case thetest team is required to do a readiness check (smoke testing) of the given environment.

Activities

o Understand the required architecture, environment set-up and prepare hardware andsoftware requirement list for the Test Environment.

o Setup test Environment and test datao Perform smoke test on the build

Deliverables

o Environment ready with test data set upo Smoke Test Results.

5) Test Execution / Reporting / Defect Tracking

During this phase test team will carry out the testing based on the test plans and the testcases prepared. Bugs will be reported back to the development team for correction andretesting will be performed.

Activities

o Execute tests as per plano Document test results, and log defects for failed caseso Map defects to test cases in RTMo Retest the defect fixeso Track the defects to closure

Deliverables

o Completed RTM with execution statuso Test cases updated with resultso Defect reports


7/13

6) Test Cycle Closure / Retrospective study

Testing team will meet , discuss and analyze testing artifacts to identify strategies that have tobe implemented in future, taking lessons from the current test cycle. The idea is to removethe process bottlenecks for future test cycles and share best practices for any similar projectsin future.

Activities

o Evaluate cycle completion criteria based on Time,Test coverage,Cost,Software,CriticalBusiness Objectives , Quality

o Prepare test metrics based on the above parameters.o Document the learning out of the projecto Prepare Test closure reporto Qualitative and quantitative reporting of quality of the work product to the customer.o Test result analysis to find out the defect distribution by type and severity.

Deliverables

o Test Closure reporto Test metrics


8/13

Q1. What is Requirement Traceability Matrix?

The Requirements Traceability Matrix (RTM) is a tool to make sure that project requirement remain same throughoutthe whole development process. RTM is used in the development process because of following reasons:

To determine whether the developed project is meet the requirements of the user.

To de termine all the requirements given by the user To make sure the application requirement can be fulfilled in the verification process.

Q2. What is difference between Pilot and Beta testing?

The differences between these two are listed below:

A beta tes t when the product is about to release to the end user whereas pilot testing take place in the earlier phaseof the development cycle. In beta testing application is given to a few user to make sure that application meet the user requirement and doesnot contain any showstopper whereas in case of pilot testing team member give their feedback to improve the qualityof the application.

Q3. Describe how to perform Risk analysis during software testing?

Risk analysis is the process of identifying risk in the application and prioritizing them to test. Following are some ofthe risks:

1. New Hardware.2. New Technology.3. New Automation Tool.4. Sequence of code delivery.5. Availability of application test resources.

We prioritize them into three categories these are:

High magnitude: Impact of the bug on the other functionality of the application. Medium: it can be tolerable in the application but not desirable. Low: it can be tolerable. This type of risk has no impact on the company business.

Q4. What is Silk Test?

Silk Test is a tool developed for performing the regression and functionality testing of the application. Silk Test a toolis used when we are testing the applications which are based on Window, Java, web or traditional client/server. SilkTest help in preparing the test plan and management of those test plans, to provide the direct accessing of thedatabase and validation of the field.

Q5. What is difference between Master Test Plan and Test Plan.

The differences between Master Plan and Test Plan are given below:

Master Test Plan contains all the testing and risk involved area of the application where as Test case documentcontains test cases. Master Test plan contain all the details of each and every individual tests to be run during the overall developmentof application whereas test plan describe the scope, approach, resources and schedule of performing test. Master Test plan contain the description of every tests that is going to be performed on the application where as test


9/13

plan only contain the description of few test cases. during the testing cycle like Unit test, System test, beta test etc Master Test Plan is created for all large projects but when it is created for the small project then we called it as testplan.

Q6. How to deal with not reproducible bug?

Ans. A bug cannot be reproduced for following reasons:

1. Low memory.2. Addressing to non-available memory location.3. Things happening in a particular sequence.

Tester can do following things to deal with not reproducible bug:

Includes steps that are close to the error statement. Evaluate the test environment. Examine and evaluate test execution results. Resources & Time Constraints must be kept in point.

Q7.What is the difference between coupling and cohesion?

The difference between coupling and cohesion is discussed below:

Cohesion is the degree which is measure dependency of the software component that combines relatedfunctionality into a single unit whereas coupling means that binding the related functionality into different unit. Cohesion deals with the functionality that related different process within the single module whereas coupling dealswith how much one module is dependent on the other modules within the application. It is good to increase the cohesion between the software whereas increasing coupling is avoided.

Q8. What is the role of QA in a project development?

The role of Quality Assurance is discussed below:

QA team is responsible for monitoring the process to be carried out for developm ent. Responsibilities of QA team are planning testing execution process. QA Lead creates the time tables and agrees on a Quality Assurance plan for the product. QA team communicated QA process to the team members. QA team ensures traceability of te st cases to requirements.

Q9. When do you choose automated testing over manual testing?

This choice between automated testing over manual testing can be based upon following factors:

1. Frequency of use of test case2. Time Comparison (automated script run much faster than manual execution.)3. Reusability of Automation Script4. Adaptability of test case for automation.5. Exploitation of automation tool

Q10. What are the key challenges of software testing?

Following are some challenges of software testing:


10/13

1. Application should be stable enough to be tested.2. Testing always under time constraint3. Understanding the requirements.4. Domain knowledge and business user perspective understanding.5. Which tests to execute first?6. Testing the Complete Application.7. Regression testing.8. Lack of skilled testers.9. Changing requirements.10. Lack of resources, tools and training

Q11. What is difference between QA, QC and Software Testing?

Quality Assurance (QA): QA refers to the planned and systematic way of monitoring the quality of process which isfollowed to produce a quality product. QA tracks the outcomes and adjusts the process to meet the expectation.

Quality Control (QC): Concern with the quality of the product. QC finds the defects and suggests improvements. Theprocess set by QA is implemented by QC. The QC is the responsibility of the tester.

Software Testing: is the process of ensuring that product which is developed by the developer meets the userrequirement. The motive to perform testing is to find the bugs and make sure that they get fixed.

Q12. What is concurrent user hits in load testing?

When the multiple users, without any time difference, hits on a same event of the application under the load test iscalled a concurrent user hit. The concurrency point is added so that multiple Virtual User can work on a single eventof the application. By adding concurrency point, the virtual users will wait for the other Virtual users which are runningthe scripts, if they reach early. When all the users reached to the concurrency point, only then they start hitting therequests.

Q13. What is difference between Front End Testing and Back End testing?

The differences between front and back end testing are:

Front End Testing is performed on the Graph ical User Interface (GUI).whereas Back End Testing involvesdatabases testing. Front end consist of web site look where user can interact whereas in case of back end it is the database which isrequired to store the data. When ender user enters data in GUI of the front end application, then this entered data is stored in the database. Tosave this data into the database we write SQL queries.

Q14. What is Automated Testing?

The process of performing testing automatically which reduces the human intervention this is automation testing. Theautomation testing is carried out with the help of the some automation tool like QTP, Selenium, WinRunner etc. Inautomation testing we use a tool that runs the test script to test the application; this test script can be generatedmanually or automatically. When testing is completed then tools automatically generate the test report and report.


11/13

Q15. What is Testware?

The testware is:

The subset of software which helps in performing the testing of application. Testware are required to plan, design, and execute tests. It contains documents, scripts, inputs, expected results,

set-up and additional software or utilities used in testing. Testware is term given to combination of all utilities and application softw are that required for testing a softwarepackage.

Testware is special because it has:

1. Different purpose2. Different metrics for quality and3. Different users

Q16.What is Exhaustive Testing?

Exhaustive Testing, as the name suggests is very exhaustive. Exhaustive testing means to test every component inthe application with every possible number of inputs. According to Principles of testing Exhaustive Testing isImpossible because exhaustive testing requires more time and effort to test the application for all possible number ofinputs. This may lead to high cost and delay in the release of the application.

Q17. What is Gray Box Testing?

Grey box testing is the hybrid of black box and white box testing. In gray box testing, test engineer has the knowledgeof coding section of the component and designs test cases or test data based on system knowledge. In this testerhas knowledge of code, but this is less than the knowledge of white box testing. Based on this knowledge the testcases are designed and the software application under test treats as a black box & tester test the application fromoutside.

Q18. What is Integration Testing?

Integration testing is black box testing. Integration testing focuses on the interfaces between units, to ensure thatunits work together to complete a specify task. The purpose of integration testing is to confirm that differentcomponents of the application interact with each other. Test cases are developed with the purpose of exercising theinterfaces between the components. Integration testing is considered complete, when actual results and expectedresults are same. Integration testing is done after unit testing. There are mainly three approaches to do integrationtesting:

Top -down Approach tests the components by integrating from top to bottom. Bottom -up approach It takes place from the bottom of the control flow to the higher level components Big bang approach In this are different module are joined together to form a complete system and then testing isperformed on it.

Q19. What is Scalability Testing?

Scalability testing is testing performed in order to enhanced and improve the functional and performance capabilitiesof the application. So that, application can meets requirements of the end users. The scalability measurements isdone by doing the evaluating the application performance in load and stress conditions. Now depending upon thisevaluation we improve and enhanced the capabilities of the application.


12/13

Q20. What is Software Requirements Specification?

A soft ware requirements specification is a document which acts as a contract between the customer and thesupplier. This SRS contain all the requirement of the end user regarding that application. SRS can be used as acommunication medium between the customer and the supplier.

The developer and tester prepare and examine the application based on the requirements written in the SRSdocument. The SRS documented is prepared by the Business Analyst by taking all the requirements for the customer.

Q21. What is Storage Testing?

In Storage Testing we test those functionalities of the application which is responsible for storing the data intodatabase. The data entered by the end user in GUI or front end, is the same data which is stored in the database.The storage testing determines that the data taken from the front end of the application is stored in correct place andin correct manner in the database.

Q22. What is Stress Testing?

Stress testing tests the software with a motive to check that the application do not crashes if we increase the stresson the application by increasing the large number of user working on the application. We can also apply the stress onthe application firing the lots of process which cannot be handled by the application. We perform the stress testing onthe application evaluate the application capabilities at or beyond the limits of its specified requirements to determine.Generally, this is a type of performance testing performed in a very high level of load and stress condition.

Q23. What is Test Harness?

A test harness is a collection of software and test data required to test the application by running it in different testingcondition like stress, load, data- driven, and monitoring its behavior and outputs. Test Harness contains two mainparts:

Test execution engine Test script repository

Automation testing is the use of a tool to control the execution of tests and compare the actual results with theexpected results. It also involves the setting up of test pre-conditions.

Q24. Can you define test driver and test stub?

The Stub is called from the software component to be tested. It is used in top down approach. The driver calls a component to be tested. It is used in bottom up approach. Both test stub and test driver are d ummy software components.

We need test stub and test driver because of following reason:

Suppose we want to test the interface between modules A and B and we have developed only module A. So wecannot test module A but if a dummy module is prepare, using that we can test module A. Now module B cannot send or receive data from module A directly so, in these cases we have to transfer data fromone module to another module by some external features. This external feature used is called Driver.

Q25.What is good design?


13/13

Design refers to functional design or internal design. Good internal design is indicated by software code whoseoverall structure is clear, understandable, easily modifiable, and maintainable; is robust with sufficient error-handlingand status logging capability, and works correctly when implemented. Good functional design is indicated by anapplication whose functionality can be traced back to customer and end -user requirements.

Q26. What makes a good QA or Test manager?

A good QA or Test manager should have following characteristics:

Knowledge about Software development process Improve the teamwork to increase productivity Improve cooperation between software, test, and QA engineers To improvements the QA processes. Communica tion skills. able to conduct meetings and keep them focused

Q27. What is Manual scripted Testing and Manual Support testing?

Manual Scripted Testing: Testing method in which the test cases are designed and reviewed by the team beforeexecuting it. It is done by manual testing teams.Manual-Support Testing: Testing technique that involves testing of all the functions performed by the people whilepreparing the data and using these data from automated system. it is conducted by testing teams

Q28. What is Fuzz testing, backward compatibility testing and assertion testing?

Fuzz Testing: testing application by entering invalid, unexpected, or random data to the application this testing isperformed to ensure that application is not crashing when entering incorrect and unformatted data.

Backward Compatibility Testing: Testing method which examines performance of latest software with older versionsof the test environment.

Assertion Testing: Type of testing consisting in verifying if the conditions confirm the product requirements.

Q29. How does a client or server environment affect testing?

There are lots of environmental factors that affect the testing like speed of data transfer data transfer, hardware, andserver etc while working with client or server technologies, testing will be extensive. When we have time limit, we dothe integration testing. In most of the cases we prefer the load, stress and performance testing for examine thecapabilities of the application for the client or server environment.

Q30. What are the categories of defects?

There are three main categories of defects:

Wrong: The requirements are implemented incorrectly in the application. Missing: When requirement given by the customer and application is unable to meet those application. Extra: A requirement incorporated into the product that was not given by the end customer. This is always avariance from the specification, but may be an attribute desired by the user of the product.

Manual Testing Interview Questions Asked

Documents

Transcript of Manual Testing Interview Questions Asked