Software Testing Interview

Questions (Manual+ API+ SQL)

Q1. Tell me about yourself?

Ans- Good Morning, this is Harsha Bhadoria. I have 2.5 Yrs. of experience as QA Tester. I had
completed my Engineering from Rajasthan Technical University in the year 2019. I started my Career
with the Vorsitz IT Service in 2019 as a QA Tester. Then I worked with Teleperformance for 13
months. And I am currently serving Capgemini as a Sr. QA Engineer.

Q2. Tell me about your roles and responsibilities?

Ans- I am working as a Sr QA Engineer in current organization, here my responsibilities are I go

through the requirements, prepare Test cases, Execute Test Cases, attend Scrum Call and Stand-Up
Meetings, Perform Functional testing like Smoke, Sanity, Retest, Regression Test. If found any bug
then upload it on JIRA. Perform API testing as well.

Q3. Explain Smoke and Sanity testing?

Ans- Smoke is used to check whether the build is acceptable for further testing or not. It is Shallow
and Wide.

Sanity is used to check whether the build is good to go for further deployment or not. It is Narrow
and Wide.

Q4. Explain Retesting and regression testing?

Ans- We perform retesting while we raise any bug and the developer fix that, then we retest that
and check whether that bug is fixed or not.

In regression testing we check if developer has fixed any bug then any surrounding functionalities
will not get affected by that. Then we test the surrounding functionalities in regression testing.

Q5. Explain Verification and Validation method? / Explain Preventive and reactive approach?

Ans- Verification is the process-oriented approach. In verification we check that are we building the
product, right? Verification is done by the developer point of view. We can verify without executing
the code. Techniques we used is Informal review, Inspection, and Peer review.

Validation is the product-oriented approach. In validation we check that Are we building the right
product? It is done as the per the customer point of view. We validate by executing the software
code. Techniques we used are unit testing, integration testing, system testing, smoke and sanity etc.

Q6. Explain Static and dynamic testing?

Ans- We do static testing without executing the code. It involves checklist for testing process. It
prevents the defects. It includes walkthroughs, code review, inspection etc. E.g. Verification.

We do static testing by executing the code. It involves test cases for testing process. It finds the
defect. It involves functional and non-functional testing. E.g. Validation.
Q7. Explain Quality assurance and Quality Control?

Ans- Quality Assurance is aimed to avoid the defect whereas Quality control is aimed to identify and
fix the defects. Quality Assurance provides assurance that quality requested will be achieved
whereas Quality Control is a procedure that focuses on fulfilling the quality requested. Quality
Assurance is done in software development life cycle whereas Quality Control is done in software
testing life cycle. Quality Assurance is a proactive measure whereas Quality Control is a Reactive
measure. Quality Assurance requires the involvement of all team members whereas Quality Control
needs only testing team. Quality Assurance is performed before Quality Control.

Q8. Explain Cache and Cookies?

Ans- Cache is employed to store the web site content for the long run purpose. While cookie is
employed to store user choices. Cache’s website contents are stored in browser only. While cookie’s
contents are stored in both server and browser. It expires manually. While it expires automatically. It
consumes large space in terms of capacity. While it consumes less space in terms of capacity. Cache
does not send the response with requests. While cookie sends the response with requests.

Q9. Explain Build and Release?

Ans- A build is a version of a software. It is given to testing team by developers to test the
application locally.

Release is the distribution of the final version of an application to the customer by software
developer team.

Q10. Explain Bug leakage and Bug release?

Ans- A defect which exists during testing yet unfound by the tester which is eventually found by the
tester/end-user is also called bug leakage.

A bug release is when a particular version of s/w is released with a set of known bug(s)/defect(s).

Q11. Explain Top-down testing and Bottom-up testing?

Ans- Top Down Testing is a method in which integration testing takes place from top to bottom
following the control flow of software system. The higher-level modules are tested first and then
lower level modules are tested and integrated in order to check the software functionality. Stubs are
used for testing if some modules are not ready.

Bottom-up Testing is a strategy in which the lower level modules are tested first. These tested
modules are then further used to facilitate the testing of higher-level modules. The process
continues until all modules at top level are tested. Once the lower level modules are tested and
integrated, then the next level of modules is formed. Drivers are used for testing if some modules
are not ready.

Q12. Explain Black box and White box testing.

Ans- Black Box Testing is a software testing method in which the internal structure/ design/
implementation of the item being tested is not known to the tester.

White Box Testing is a software testing method in which the internal structure/ design/
implementation of the item being tested is known to the tester.

Q13. Explain bug, error, defect and failure.

Ans- Bug is the difference between actual outcome and expected outcome. It is accepted by the
developer and founded by tester during testing.

Defect is the difference between actual outcome and expected outcome. Mostly it is founded at
production environment. The mistake in coding like syntax, semantic is known as Error. Failure is the
system or component inability to carry out required task.

Q14. Explain Alpha and Beta testing.

Ans- Alpha Testing is a type of acceptance testing; performed to identify all possible issues and bugs
before releasing the final product to the end users. Alpha testing is carried out by the testers who
are internal employees of the organization.

Beta Testing is performed by “real users” of the software application in “real environment” and it
can be considered as a form of external User Acceptance Testing. It is the final test before shipping a
product to the customers. Direct feedback from customers is a major advantage of Beta Testing. This
testing helps to test products in customer’s environment.

Q15. Explain Negative and Positive testing?

Ans- Positive testing is a type of software testing that is performed by assuming everything will be as
expected. It is performed with the assumption that only valid and relevant things will occur. data set
and all other functionalities will be as expected.

Negative testing is a type of software testing that is performed to check the system for unexpected
conditions. Negative testing plays a much important role in high-performance software
development. It checks whether on such unexpected conditions what will be the behavior of the
software.

Q16. Explain Test Plan and Test case?

Ans- A Test Plan can be defined as a document that defines the scope, objective, and approach to
test the software application. Test Plan is a document that lists all the activities in a QA project,
schedules them, defines the scope of the project, roles & responsibilities, risks, entry & exit criteria,
test objective, and anything else that you can think of.

Test Case is a step by step procedure that is used to test an application Test case template includes
Test Suit ID, Test Data, Test procedure, Actual results, Expected results etc.

Q17. Explain waterfall and Agile model?

Ans- Agile Testing is a type of software testing that involves all members of the project team, special
experts and testers. In agile testing, testing is not a different phase and testing is performed along
with development phases that includes requirements, design, coding and generation of test cases.
Agile testing takes place alongside the Software Development Life Cycle (SDLC).

Waterfall Testing is a type of software testing in which testing is a different phase and there are
steps and steps classified and testing is performed only in that order. Only after the completion of
the one phase or one level next level testing is carried out.

Q18. Explain Epic and User story?

Ans- An epic is a large body of work that can be broken down into a number of smaller stories, or
sometimes called “Issues” in Jira.
User stories are lightweight requirements phrased in a way that focuses on the end-user and the
desired outcome.

Q19. Explain Exploratory testing and Ad-hoc (monkey) testing?

Ans- Exploratory testing is an approach to software testing that is concisely described as

simultaneous learning, test design and test execution. We can say that in this testing test planning,
analysis, design and test execution, are all done together and instantly.

Ad hoc Testing is an informal or unstructured software testing type that aims to break the testing
process in order to find possible defects or errors at an early possible stage. Ad hoc testing is done
randomly and it is usually an unplanned activity which does not follow any documentation and test
design techniques to create test cases.

Q20. Explain Critical bug and showstopper bug?

Ans- Critical bug usually block an entire system's or module's functionality, and testing cannot
proceed further without such a defect being fixed.

A showstopper bug is a hardware or software bug that causes an implementation to stop and
become essentially useless. A showstopper bug is a bug that stops from continuing test scripts and
doesn't let you proceed to the next level.

Q21. Explain Scrum Call or Stand-Up Call?

Ans- Daily Scrum meeting is also called can Scrum call or Standup meeting. This meeting own by the
Scrum team, happens mostly during beginning of every day. Should last for max 15 minutes. Where
the development team member discusses on the work they have done, and make the strategy to
work for the day.

Q22. Explain Severity and Priority?

Ans- Bug Severity or Defect Severity in testing is a degree of impact a bug or a Defect has on the
software application under test.

Priority is defined as the order in which a defect should be fixed. Higher the priority the sooner the
defect should be resolved.

Q23. Explain Project and Product?

Ans- A project is a temporary endeavor, with a clear definition of what needs to be delivered and by
when. Project is developed upon customer requirements. A project has a beginning and end date.

A product is designed to continually create value for customers by solving their problems. Product is
based upon market requirements.

Q24. Explain Put and Patch method?

Ans- Put method is used for updating any existing resource.

Patch method is used for partially updating any existing resource.

Q25. Explain Functional and Non-Functional testing?

Ans- Functional testing is a type of software testing in which the system is tested against the
functional requirements and specifications. It is basically defined as a type of testing which verifies
that each function of the software application works in conformance with the requirement and
specification.

Non-functional testing is a type of software testing that is performed to verify the non-functional
requirements of the application. It verifies whether the behavior of the system is as per the
requirement or not. Non-functional testing is defined as a type of software testing to check non-
functional aspects of a software application.

Q26. What is Backlog?

Ans- Backlog is simply a list of all things that needs to be done within the project.

Q27. What is Scrum?

Ans- Scrum is an agile development methodology used in the development of Software based on an
iterative and incremental processes. The primary objective of Scrum is to satisfy the customer’s need
through an environment of transparency in communication, collective responsibility and continuous
progress.

Q28. What is Retrospective meeting?

Ans- In Retrospective meeting we discuss: - What worked well for us? What did not work well for us?
What actions can we take to improve our process going forward?

Q29. Which methodology you use in your current organization?

Ans- In my current organization we are using Agile methodology, in it we follow scrum framework,
here are BA’s who are always in contact with the client they collect the requirement from the clients
and they put down in JIRA as backlog. Then we have Sprint demo call where 3 to 4 teams are
engaged in that call, like BA’s, Back-end, developer and QA team. In which we decide that what 2 to
3 points we will take in this sprint and if in those points we have any doubt we take clarification from
the BA Team.

Then developer team and QA team provide estimations to BA that how much time will it take to
complete development and testing for those points. At the time when developer team is developing
the project, we parallelly start writing test cases. After completing test cases we send it to the BA’s
to review once they approve, they send them back. Then we start executing the test cases once the
developer provides us the build.

After executing the test cases at the end of the sprint we have retrospective call in that call we
discuss what good thing we did, where we lack and where we need more improvement for next
sprint.

On daily basis we have 15-20 min of scrum call, in which we discuss what we had done, what we are
going to do today and if we found any bug, we can discuss that on that call too.

Q30. What is Unit testing?

Ans- A unit test is a way of testing a unit - the smallest piece of code that can be logically isolated in
a system. It is a software development process in which the smallest testable parts of an application,
called units.

Q31. What is System testing?

Ans- System Testing is a level of testing that validates the complete and fully integrated software
product. The purpose of a system test is to evaluate the end-to-end system specifications.

Q32. What is Integration testing?

Ans- Integration testing is defined as a type of testing where software modules are integrated
logically and tested as a group. A typical software project consists of multiple software modules,
coded by different programmers. The purpose of this level of testing is to expose defects in the
interaction between these software modules when they are integrated

Q33. What is Exploratory testing?

Ans- Exploratory testing is an approach to software testing that is often described as simultaneous
learning, test design, and execution. It focuses on discovery and relies on the guidance of the
individual tester to uncover defects that are not easily covered in the scope of other tests.

Q34. What is Usability testing?

Ans- Usability testing is a method used to evaluate how easy a website is to use. The tests take place
with real users to measure how ‘usable’ or ‘intuitive’ a website is and how easy it is for users to
reach their goals.

Q35. What is Ad-hoc testing? / What is Monkey Testing?

Ans- Ad-hoc Testing is an informal or unstructured software testing type that aims to break the
testing process in order to find possible defects or errors at an early possible stage. Ad hoc testing is
done randomly and it is usually an unplanned activity which does not follow any documentation and
test design techniques to create test cases.

Q36. What is UAT testing?

Ans- User Acceptance Testing (UAT) is a type of testing performed by the end user or the client to
verify/accept the software system before moving the software application to the production
environment. UAT is done in the final phase of testing after functional, integration and system
testing are done.

Q37. What is Functional testing?

Ans- In functional testing we test, what the system does i.e. it verifies that each function of the
software operates in conformance with the requirement specification. It can be answered with
yes/no. E.g. Login Functionality.

Q38. What is Non-functional testing?

Ans- In non-functional testing we test how well the system performs. To check the non-functional
aspects like performance, usability and reliability of a software application. It can be answered with
a range of numbers. E.g. Performance of an application where 100 users log in simultaneously.

Q39. What is Regression testing?

Ans- Regression testing is testing existing software applications to make sure that a change or
addition hasn't broken any existing functionality.

Q40. What is Retesting?

Ans- Retesting is a process to check specific test cases that are found with bug/s in the final
execution. Generally, testers find these bugs while testing the software application and assign it to
the developers to fix it. Then the developers fix the bug/s and assign it back to the testers for
verification. This continuous process is called Retesting.

Q41. What is Bug Life Cycle?

Ans- New -> Assigned -> Open -> Fixed -> Retest -> Close

Q42. What is Deferred bug?

Ans- The bug, changed to deferred state means the bug is expected to be fixed in next releases. The
reasons for changing the bug to this state have many factors. Some of them are priority of the bug
may be low, lack of time for the release or the bug may not have major effect on the software.

Q43. How do we perform integration testing between google and twitter?

Q44. What is Entry and Exit criteria for testing?

Ans- Entry Criteria: Entry Criteria gives the prerequisite items that must be completed before testing
can begin.

Exit Criteria: Exit Criteria defines the items that must be completed before testing can be concluded

Q45. When do you think the product is enough tested?

Ans- When we had executed the 95% to 98% of the test cases for 2 to 3 rounds then we can
conclude that testing is enough.

Q46. What is inconsistent bug? If any Bug is inconsistent, how do you proceed?

Ans- A bug which is not reproducible when retesting the same in the same version of the application
i.e. the defect is valid but it’s not reproducible always. This case, better to attach screenshots and
clear steps to reproduce with test data while logging the defect

Q47. Explain User Story and Epic?

Ans- Stories, also called “user stories,” are short requirements or requests written from the
perspective of an end user. Epics are large bodies of work that can be broken down into a number of
smaller tasks (called stories).

Q48. Explain Critical bug and Blocker?

Ans- Blocker is a type of a bug that blocks further testing because the app or software crashes in a
specific environment due to the bug. Critical error is connected with security and leads to the
program shutdown, data loss or other serious damage. Such bugs disable the app's main
functionality and are primarily fixed.

Q49. Microphone of the headset is changed, which testing you will perform?

Ans- For testing the microphone only we perform retesting and for checking the surrounding
functionalities we perform regression testing.

Q50. What is Software testing life Cycle?

Q51. What is Software Development Life Cycle?

Q52. What is duration of Sprint in your current organization?

Ans- In my current organization sprint is of 10-15 days.

Q53. What is Test Plan?

Ans- A test plan is a document detailing the objectives, resources, and processes for a specific test
for a software or hardware product.

Q54. What is Test Artifacts/ Test Deliverables?

Ans- Test Artifacts/ Deliverables are simply integral part of software testing. These are generally set
of documents, which software project tester gets during STLC (Software Testing Life Cycle). Test
artifacts are by-products that are generated or created while performing software testing.

Q55. What is Agile?

Ans- Agile is an iterative approach to project management and software development that helps
teams deliver value to their customers faster Requirements, plans, and results are evaluated
continuously so teams have a natural mechanism for responding to change quickly.

Q56. Explain Test Suite?

Ans- Test suite, is a collection of test cases that are intended to be used to test a software program
to show that it has some specified set of behaviors.

Q57. Explain RTM / Requirement Traceability Matrix?

Ans- The main purpose of Requirement Traceability Matrix is to validate that all requirements are
checked via test cases such that no functionality is unchecked during Software testing.

Q58 If you are getting Client error while testing, how will you fix it?

Ans- Client error is from 400 – 499 is we are getting any error code in between this then we can try
to fix by Relaunching the browser, Try to access the same URL in different browser, By clearing cache
and cookie data, reinstalling the browser, restarting the system, check the network connection.

Q59. If you are getting Server Error while testing, how will you fix it?

Ans- Server error can be fixed by the developer only.

Q60. What is Web service?

Ans- Web Service is a method of communication between two system over the network.

Q61. What is REST API?

Ans- REST API is an architectural style for API that uses HTTP request to access and use data. We can
use any method in REST API. It supports all types of data formats. It requires less bandwidth for
access and server response.

Q62. What is SOAP API?

Ans- SOAP is a protocol i.e. it has predefined set of rules. Its used to create, retrieve, update and
delete records like account, password etc. It is used for transmitting data over HTTP and HTTPS
protocol. It strictly follows XML data format only.

Q63. Explain REST/ SOAP API?

Ans-

Q64. What is Candidate Key?

Ans- It is a set of one or more fields/ column that can identify a record uniquely in a table. There can
be multiple candidate keys in one table. Each candidate key can work as primary key.

Q65. What is Primary Key?

Ans- It is a set of one or more column of a table that uniquely identify a record in a database table. It
cannot accept null and duplicate values. Only one candidate key can be primary key.

Q66. What is Unique Key?

Ans- - It is a set of one or more column of a table that uniquely identify a record in a database table.
It is like primary key but it can accept only one null value and it cannot have duplicate value.

Q67. What is Foreign Key?

Ans- It is a field defined in database table that is primary key in another table. It cannot accept
multiple null and duplicate values.

Q68. Explain DCL, DDL, and DML?

Ans- DML (Data Manipulation Language) – It is used to retrieve, store, modify, delete, insert and
update data in database. E.g. Insert, update, delete

DDL (Data Definition Language) -It is used to create and modify the structure of database objects in
database. E.g. Create, alter, drop, truncate

DCL (Data Control Language) – It is used to create roles, permission and referential integrity as well it
is used to control access to database by securing it. E.g. Grant, Revoke

Q69. What is Endpoint?

Ans- Endpoint = Domain + URI

Q70. What is protocol?

Ans- Protocol is a system of rules that allows two or more entities of a communications system to
transmit information.

Q71. What is Path Parameter?

Ans- URI parameter (Path Param) is basically used to identify a specific resource or resources.

Q72. What is Path Variable?

Ans- The PATH environment variable is an important security control. It specifies the directories to
be searched to find a command.

Q73. What is Query String/ Query Parameter?

Ans- A query string is a part of a uniform resource locator that assigns values to specified
parameters. A query string commonly includes fields added to a base URL by a Web browser or
other client application,

Q74. What is URI?

Ans- URIs enable the protocols over the internet to conduct the interactions between and among
resources.

Q75. Why you use GET, PUT, POST, PATCH and DELETE?

GET- It is used to read a resource.

PUT- It is used to update an existing resource.

POST- It is used to create a new resource.

PATCH- It is used to partial update any existing resource.

DELETE- It is used to delete a resource.

Q76. Which SQL Server you are using in your current organization?

Ans- SQL Server Management Studio 2016

Q77. Explain HTTPS and HTTPS?

Ans- HTTP- Transfers data from a web server to a browser, this sends data such in non-encrypted
form.

HTTPS- Transfers data by using SSL i.e. Secure Socket Layer which creates encrypted connection
between server and browser.

Q78. What is API?

Ans- API is a method of communication between two layers. It is a client- Server application. We
send request from the client and get response from the server.

Q79. Which methods are used in SOAP API?

Ans- GET and POST methods are used in SOAP API.

Q80. Which API is most preferred and why?

Ans- REST API is most preferred because it accepts different data formats due to which it requires
less bandwidth for access and server response. It uses multiple methods for communication.

Q81. What you do when you miss any UAT bug?

Ans- If we missed any UAT bug then we will try to replicate it at our SIT (System in Testing) end, we
will follow the same steps for replicating the bug if they provide any video and screenshot then we
will consider that too. We will check BRD and User Story that is it listed over there or not, then we
will check that have we created ay test cases or test scenario for that or not. If it is mentioned in the
requirement then we accept that it is our miss and we assign that to developer by including scrum
team and try to fix that on priority basis, followed by retest and regression test, then we will go with
deployment.

And if that is not mentioned in the requirements we will provide our strong comments that this is
not the part of the BRD or SRs document or we are not able to replicate it at our SIT end means that
are some environment issues so we don’t accept as a bug but we could take as a enhancement or
change request for next sprint.

Q82. Which Boards are used in JIRA?

Ans- For short term project we use KANBAN board and for long term project we use SCRUM board.

Q83. Which teams are engaged in standup call?

Ans- QA Team, Backend, frontend, Business Analyst and Scrum teams are engaged in standup call.

Q84. Why Agile method is preferred?

Ans- Agile helps teams respond to unpredictability through incremental, iterative work, which also
allows the team to gather feedback and react quickly. Customer satisfaction through early and
continuous software delivery. Accommodate changing requirements throughout the development
process.

Q85. What is status code for Client/ Server error?

Ans- 400 – 499 are client error and 500 – 599 are server error.

Q86. What is 300 Status code denote?

Ans- 300 denotes the redirect status response code indicates that the request has more than one
possible response.

Q87. What is 200/ 201 Status Code denote?

Ans- 200 is for OK (Everything Fine) means API is successfully executed.

201 is for created means a new resource has been created.

Q88. Which code is used for Bad Request? / Why we are getting 400 error?

Ans- 400 Bad Request response status code indicates that the server cannot or will not process the
request due to something that is perceived to be a client error.

Q89. Which Code is used for Not Found? / Why we are getting 404 error?

Ans- 404 is for Page not found indicates the server was unable to find what was requested.

Q90. Which Code is used for Forbidden? / Why we are getting 403 error?

Ans- 403 is for forbidden indicates that the server understands the request but refuses to authorize
it.

Q91. Which Code is used for Unauthorized? / Why we are getting 401 error?

Ans- The 401 Unauthorized Error is an HTTP status code error that represented the request sent by
the client to the server that lacks valid authentication credentials.

Q92. Which Code is used for Request Time Out? / Why we are getting 408 error?

Ans- A 408 Request Timeout is an HTTP response status code that indicates the server didn't receive
a complete request message within the server's allotted timeout period.

Q93. Which Code is used for OK response? / Why we are getting 200 error?

Ans- The HTTP 200 OK success status response code indicates that the request has succeeded.

Q94. Which Code is used for Created? / Why we are getting 201 error?

Ans- The request has been fulfilled and resulted in a new resource being created.
Q95. Which Code is used for No Content? / Why we are getting 204 error?

Ans - The HTTP 204 No Content success status response code indicates that a request has
succeeded, but that the client doesn't need to navigate away from its current page.

Q96. What is Client-Server Architecture?

Ans- The client-server architecture describes how a server provides resources and services to one or
more clients. We send request from the client and get response from server.

Q97. What is Sign Off?

Ans- QA prepares the Sign Off document to acknowledge that they have reviewed and tested the
application and now the application is ready for release.

Q98. What does a test plan consist of?

Ans- Test Plan consists of test environment, features to be tested, features not to be tested,
approvals, test deliverables, estimations, test cases, test items, bugs, assumptions and dependencies
etc.

Q99. What is Conditional Sign Off?

Ans- When the Software does not meet the exit criteria, the QA can do the Conditional Sign Off. For
example, when the software development activities cross the deadline and the tester has not
completed the testing, they can do the Conditional Sign Off after communicating with their Test
Manager.

Q100. What are the deliverables for Sign Off? / How will you provide Sign Off?

Ans- Test deliverables are Test strategy, Test plan and estimation, Test scenario, Test cases and test
data, RTM, Test summary report, Test closure report and Incident report

Q101. Which domain Projects you are working on?

Ans- Ecommerce domain

Q102. What is Performance Testing?

Ans- Performance testing is the practice of evaluating how a system performs in terms of
responsiveness and stability under a particular workload. Performance tests are typically executed to
examine speed, robustness, reliability, and application size.

Q103. What is UI testing? / What is GUI Testing?

Ans- User interface or UI testing, also known as GUI testing, is the process of testing the visual
elements of an application to validate whether they accurately meet the expected performance and
functionality. By testing the GUI, testers can validate that UI functions are free from defects.

Q104. What is SRS/ BRD?

Ans- The Business Requirement Specification (BRS) is a formal document that specifics the
customer's requirement, written or verbal. Simultaneously, the Software Requirement Specification
(SRS) document defines the functional and non-functional needs of the software to be established.

Q105. Explain Error Guessing Technique?

Ans- Error Guessing is a Software Testing technique on guessing the error which can prevail in the
code. It is an experience-based testing technique where the Test Analyst uses his/her experience to
guess the problematic areas of the application.

Q106. Explain Equivalence Portioning?

Ans- Equivalence partitioning or equivalence class partitioning (ECP) is a software testing technique
that divides the input data of a software unit into partitions of equivalent data from which test cases
can be derived.

Q107. Explain Decision Table Technique?

Ans- Decision Table Testing is a software testing methodology used to test system behavior for
various input combinations. In this systematic approach, the several input combinations and their
corresponding system behavior are represented in tabular form.

Q108. Explain Boundary Value Analysis?

Ans- Boundary Value Analysis (BVA) is a Black-Box testing technique used to check the errors at the
boundaries of an input domain. The name comes from the Boundary, which means the limits of an
area. So, BVA mainly focuses on testing both valid and invalid input parameters for a given range of a
software component.

Q109. What is the Black Box-Testing Technique?

Ans- Black box testing checks scenarios where the system can break such as equivalence value
analysis, decision design technique and equivalence portioning.

Q110. How to do API Testing?

Ans- The developer provides us the API along with the method name and the parameter that we
need to pass with API, we select the method name from the dropdown and paste the API in column
and click on send. Then it will give us the response then we have to analyze like what the header is
coming, suppose if we are sending the request in Json format then we should receive the response
in Json only, and check what’s the response code, response time, file size.

Q111. What are Testing principles? / Explain any 4 testing principles?

Ans- There are 7 testing principles in testing i.e. Exhaustive testing is impossible, cluster defect,
pesticide paradox, early testing, presence of defects, testing is context dependent, absence of error
is fallacy.

Q112. What is Pesticide Paradox?

Ans - Pesticide Paradox principle says that if the same set of test cases are executed again and again
over the period of time then these set of tests are not capable enough to identify new defects in the
system. In order to overcome this “Pesticide Paradox”, the set of test cases needs to be regularly
reviewed and revised.

Q113. What is Defect Clustering?

Ans- Bugs are not often distributed evenly throughout an application. Defect clustering simply
means that a small number of features have caused the majority of quality issues in an application.

Q114. Why Exhaustive testing in impossible?

Ans- Exhaustive testing, which is also known as complete testing, occurs when all the testers in your
team are exhausted and when all the planned tests have been executed. It is a quality assurance
testing technique in which all scenarios or data is tested for testing.

Q115. What is CRUD?

Ans- CRUD is a process which we use in SOAP API it used for creating, retrieving, updating and
deleting a resource.

Q116. Explain V model?

Ans-

Q117. What are the drawbacks of Waterfall model?

Ans- The major disadvantage of the V Model is its rigidity and most limited flexibility. If any changes
occur midway, then developers must update the test documents and also requirement documents.

Q118. What are the types of Severity?

Ans- Severity is of 5 types: Critical, Major, Moderate, Minor, and Cosmetic.

Q119. What are the types of priority?

Ans- Priority is of 3 types high, low, medium.

Q120. What do you understand by Testing Environment?

Ans- A testing environment is a setup of software and hardware for the testing teams to execute test
cases. In other words, it supports test execution with hardware, software and network configured.

Q121. Give example of High Priority and Low Severity?

Ans- If the company name is misspelled in the home page of the website, then the priority is
high and severity is low to fix it.
Q122. How you Log Bug In JIRA?

Ans- Click on create button, select issue type, write description attach screenshot if needed, select
project, select assignee click on create.

Q123. What are the activities which you can perform in JIRA as a Test Engineer?

Ans- Jira software can be used for several purposes such as Requirements and Test case
management in Agile Methodology, Project Management, Task Management, Bug Tracking

Q124. What is Compatibility Testing?

Ans- Compatibility testing is software testing which comes under the non-functional testing
category, and it is performed on an application to check its compatibility (running capability) on
different platform/environments. This testing is done only when the application becomes stable.

Q125. If the developer is not accepting any Bug which you have raised on JIRA he is marking as
deferred, how will you handle such situation?

Ans- Any bug which we have reported and the developer is saying that is doesn’t have high priority
and high severity we can take bug for the next sprint then in such scenarios he marks that bug as
deferred.
Then I always ask the developer to provide your strong comments so that I can satisfy with that until
and unless I will not satisfy with your comments, I will not accept this bug as deferred. Then I will
discuss the same thing which developer had told me with the scrum master and BA that we are
going to release this product with this bug as deferred.

Q126. What is manual testing?

Ans- In manual testing, a tester manually verifies the functionality of the software. The tester has a
comprehensive list of all the test cases they should test, along with the test data. They go through
each case, one by one. They launch the software as an end-user would, enter the input, and
manually verify the output.

Q127. Which methodology you are using in current organization?

Ans- In my current organization we are using Agile methodology, in which we are using scrum
framework. There are BA’s who are always in contact with the client for requirements and they put
down those requirements in JIRA as backlog.

Then we have sprint call where 3 to 4 teams are engaged in that call like BA, developer, backend and
QA team. In which we decide what 2-3 points we will carry forward for the sprint and if we have any
doubts in the requirement, we clarify those with BA over that call only. Then developer team and QA
team provide the estimations to BA that how much time will it take to developments and testing for
those points. At the time when developer team is developing the project, we parallelly start writing
test cases. After completing test case we send it to the

Q128. What parameters you record in API Testing?

Ans- In API testing we check status code, file size, response time, header and body type.

Q129. What is Test Closure?

Ans- Test Closure is a document that gives a summary of all the tests conducted during the software
development life cycle, it also gives a detailed analysis of the bugs removed and errors found. In
other words, Test Closure is a memo that is prepared prior to formally completing the testing
process.

Q130. What is Bug Triage?

Ans- Severity and priority of the bugs are decided in which order the bugs will be fixed.

Q131. How you manage Unexpected Leaves?

Ans- In my organization my manager has implemented one good ting in our team, i.e. on every
Friday we have KT sessions in which we have to share the knowledge of or project to one of my
colleague, who is always ready to work on the project for which I am working. So, we always have
one supportive guy, as if in case someone need emergency leave so he can take leave and we can
support him for that time.

Q132. What is Deferred Bug?

Ans- The bug, changed to deferred state means the bug is expected to be fixed in next releases. The
reasons for changing the bug to this state have many factors. Some of them are priority of the bug
may be low, lack of time for the release or the bug may not have major effect on the software.

Q133. Write Test cases for Amazon Search Field?

Ans-

Q134. Tell traffic Light Test Cases?

Ans-

Q135. What is Test Environment?

Ans- A test environment consists of a server/computer on which a tester runs their tests. It is
different from a development machine and tries to represent the actual hardware on which the
software will run; once it’s in production.

Q136. In SQL how to find length of the Employee Name?

Ans- We have to use the LEN() function.

Q137. In SQL how to find odd number of rows?

Ans- Select * from table where id % 2! = 0

Q138. In SQL how to find name with two alphabets?

Ans- By using keyword %Like, we can get the name.

Q139. Explain Webservice and API?

Ans- API is a method of communication between 2 layers.

Webservice is a method of communication between two layers over the network.

Q140. What is end to end testing?

Ans- End to End testing is the process of testing a software system from start to finish. The tester
tests the software just like an end-user would.

Q141. How to test step 120 directly in Candy Crush Game? (Stub/ driver)

Ans- With the help of Top-down integration testing, by use of stub we can test step 120 directly.

Q142. What is a Bug report?

Ans- A bug report is a specific report that outlines information about what is wrong and needs fixing
with software or on a website. The report lists reasons, or seen errors, to point out exactly what is
viewed as wrong, and also includes a request and/or details for how to address each issue.

Q143. What is Cross-Browser Testing?

Ans- Cross Browser testing is a type of non-functional testing that lets you check whether your
website works as intended when accessed through: Different Browser-OS combinations i.e., on
popular browsers like Firefox, Chrome, Edge, Safari—on any of the popular operating systems like
Windows, macOS, iOS and Android.

Q144. What is Latent Defect?

Ans- A hidden or concealed defect; one which could not be discovered by reasonable and customary
observation or inspection.

Q145. What is Test Stub and Test Driver?

Ans- Stub and driver are the dummy codes which are used in Top-down and Bottom Up Integration
testing.

Q146. What are the different methods for testing?

Ans- There are several methods of testing such as functional and non-functional, functional includes
smoke, sanity, retest, regression test etc. while non-functional includes performance, security etc.

Q147. What are the different Levels for Testing?

Ans- Different levels of testing are unit testing, system testing, integration testing and User
Acceptance testing.