0% found this document useful (0 votes)
293 views95 pages

Manual Testing Interview Questions

The document provides answers to 27 common interview questions for manual software testing. It begins by defining software testing and explaining when the ideal time to stop testing is. It then discusses key testing concepts like verification vs validation, different types of testing (static, black-box, unit, integration), test plans, coverage, and more. The document also answers questions about achieving full coverage, test stubs vs drivers, benefits of early testing, and differences between validation and verification.

Uploaded by

mdamjadansari787
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
Download as docx, pdf, or txt
0% found this document useful (0 votes)
293 views95 pages

Manual Testing Interview Questions

The document provides answers to 27 common interview questions for manual software testing. It begins by defining software testing and explaining when the ideal time to stop testing is. It then discusses key testing concepts like verification vs validation, different types of testing (static, black-box, unit, integration), test plans, coverage, and more. The document also answers questions about achieving full coverage, test stubs vs drivers, benefits of early testing, and differences between validation and verification.

Uploaded by

mdamjadansari787
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1/ 95

Manual Testing Interview Questions

If you are a fresher in this field and this is supposedly going to be your first job, below-
mentioned are the questions you will be asked.

1. What do you know about Software Testing?

Ans : Software testing refers to the validation process that helps evaluate whether the
system is working according to the requirements of the business. This process helps
qualify software on varying aspects, like efficiency, completeness, accuracy, and
usability.

2. When is the ideal time to stop the process of testing?

Ans: The testing activity stops once the team has completed the following objections:

Successful completion of the full test cycle once the final bug has been fixed

The end date of the validation stage if no high-priority or critical defects have been left
behind

In case the team has achieved the expected level of Code Coverage (CC) ratio

3. In software testing, what is the meaning of verification and validation?

Ans: In software testing, verification is a process that helps confirm that the
development of a product is underway according to the specifications and the standard
procedures of development. In this process, inspection, reviews, walkthroughs, and
demos are a few stages.

On the other hand, validation is all about confirming that the developed product is
devoid of bugs and working as expected. In this process, functional testing and non-
functional testing are two stages.
4. Define static testing?

Ans: Static testing is the white-box testing technique that helps direct developers to
cross-check their code through a checklist to find errors.

5. When does static testing begin?

Ans: Developers can effortlessly begin static testing without really finalizing the
program or application.

6. What do you mean by black-box testing?

Ans: Black-box testing is a standard testing approach that needs testers to evaluate the
software’s functionality according to the business needs. The software gets tested as a
black box and gets the validation according to the end-user’s point of view.

7. What do you mean by a test plan?

Ans: A test plan is a plan that retains all of the potential testing activities to make sure
the product is qualitative. It accumulates data from use case documents, requirements,
and product descriptions.

8. What does the test plan include?

Ans: The test plan document comprises the following things:


Testing objectives

Risk factors

Test scope

Deliverables

Testing the frame

Criteria for entry and exit

Environment

Reasons for testing


9. Define test coverage?

Ans: Test coverage is referred to as the quality metric that displays the amount of testing
that has been completed (in percentage). Test coverage is relevant for both non-
functional and functional testing activities. Also, it is used to add those test cases that
have been missing.

10. Can you achieve 100% testing coverage?

Ans: It is not possible to perform 100% testing of any software or product. However, can
do the following steps to come closer:

Setting a hard limit on:

Percentage of test cases passed

Number of bugs discovered

Setting a red flag in case:

There is a depletion of test budged

There is a breach of deadlines

Setting a green flag in case:

The entire functionality is covered in test cases

All critical and major bugs must have a ‘CLOSED’ status

11. Define unit testing?


Ans: Unit testing is also known by different names, such as component testing or module
testing. A lot of times, developers test individual modules or units to see if they work
adequately.

12. Define Integration testing?

Ans: Integration testing helps validate how well two or more software units will be
interacting with one another. There are three different ways to validate the integration:
the big bang approach, bottom-up approach, and top-down approach.

13. Is it possible to do system testing at any possible stage?

Ans: No, it is not possible. System testing should begin only once all of the modules are in
place and are working correctly. However, it is better if performed before User
Acceptance Testing (UAT).

14. What is the difference between a test stub and a test driver?

Ans: The test stub is referred to as a dummy program that helps integrate with an
application to complete the functionality. It is relevant for such testing types that use a
top-down approach. And, the test driver is a code section that calls a software
component under the test. It is effective in testing that follows a bottom-up approach.

15. What are the different types of software testing?

Ans: Different types of software testing include:

Unit testing

Functional testing

Integration testing

Smoke testing
Regression testing

Shakeout testing

System testing

White-box and black-box testing

Alpha and beta testing

Performance testing

Load testing

Stress testing

Endurance testing

Software Testing Interview Questions

If you are planning to appear for a software testing interview, here are a few questions
you should vary of:

16. Define the PDCA cycle?

Ans: In a normal software development process, there are four varying steps, referred to
as PDCA. It stands for Plan, Do Check, Act.

The plan defines the objectives and a comprehensive strategy to achieve that objective.

Do depends upon the strategy finalized during the first stage.


Check is the testing part of the software development stage. It is used to make sure that
everything is happening as per the plan.

The act is a step that is used to solve any issue arising during the checking cycle.

While the developers take responsibility for planning and building the project, testers
handle the check part of it.

17. What are the benefits of designing tests early in the life cycle?

Ans: By designing tests early in the life cycle, we can effortlessly avert defects from being
available in the main code.

18. Define exploratory testing?

Ans: Exploratory testing is referred to when design and execution take place
simultaneously against an application. In this testing type, the tester uses domain
knowledge and the testing experience to forecast under what conditions and where the
system may behave in an unanticipated way.
19. How can you explain risk-based testing?

Ans: Risk-based testing is one such testing strategy that is based upon prioritizing tests
by keeping risks in mind. It is based on a comprehensive risk analysis approach that
further categorizes the risk by their priority. Those with the highest priority get
resolved first.

20. What do you know about accessibility testing?

Ans: Accessibility testing comes into the picture when there is a need to verify whether
the software is accessible to everybody, including those with disabilities, such as blind,
deaf, mentally disabled, and more.

21. Define agile testing?

Ans: Agile testing is one such practice that uses agile methodologies and follows the
paradigm of test-first design.

22. What is automated testing?

Ans: When done by software tools and executed without any manual intervention,
testing is referred to as automated testing. This type of testing can be used in API,
performance, GUI, and more.

23. Define baseline testing?

Ans: In baseline testing, a specific set of tests is run to gain information regarding the
performance. Baseline testing enhances the capabilities and performance of the
application with the help of collected information to make changes in the application.
The baseline helps compare the application’s present performance with the previous
performance.

24. What are the important testing types for web testing?
Ans: Two major types of testing are important for web testing, such as:

Performance Testing: It is a testing technique wherein the quality attributes are


evaluated, such as responsiveness, scalability, speed under varying load conditions, and
more. The performance testing defines the attributes that require improvement before
the launch.

Security Testing: This one is a testing technique that comprehends the resources and
data that must be saved from hackers or intruders.

25. State the difference between validation and verification?

Ans:

Validation Verification

It is a dynamic testing It is a static testing

Validation takes place after verification Verification takes place before validation

Verification assesses documents, plans,


Validation assesses products
specifications, and requirements

In verification testing, inputs are the issues list


Invalidation testing, a real product is tested
checklist, inspection, and walkthroughs

Here, plans, documents, requirements, and


Here, the actual product is the output
specifications are the output.
26. State the difference between reactive and preventative approaches to
testing?

Ans: The reactive tests are designed once the software is developed, while the
preventative tests are designed earlier than that.

27. What is the use of decision table testing?

Ans: A decision table comprises inputs and outputs in the same column, only that the
outputs come above and inputs are placed below them. Also, decision table testing is
used for the testing systems for which the specification takes the cause-effect
combination or rules.

28. What are positive and negative testing?

Ans: Positive testing is when you put valid input and anticipate to expect certain actions
that are completed as per the specifications. On the other hand, negative testing is when
you put an invalid input and get an error.

29. What is the meaning of boundary value analysis?

Ans: In boundary value analysis, we test precise boundaries. For instance, suppose there
is a bank application where you can withdraw a minimum of 100 and a maximum of
25000. Thus, we will test the above and below the maximum scenarios in boundary
value analysis.

For example, if there is a bank application, you can withdraw a maximum of 25000 and a
minimum of 100. So in boundary value testing, we only test above the max and below the
max. This covers all scenarios.

30. Define the types of performance testing?

Ans: Performance testing is a technique that helps determine the system’s performance,
such as stability, scalability, and speed. There are different types of software testing,
such as:
Load Testing: A technique wherein a system is tested with an increasing load until it
attains the threshold value

Stress Testing: This one is a technique that helps check the system when hardware
resources are not sufficient, such as disk space, memory, CPU, and more

Spike Testing: Spike Testing is a subset of load testing that checks the application’s
instability when the load is varying

Endurance Testing: This is the subset of load testing and checks the system’s behavior

Volume Testing: This is a technique wherein the system gets tested when the data
volume is increased

Scalability Testing: It is referred to as a technique that makes sure the system is working
well in proportion to the increasing demands of the users.

Functional Testing Interview Questions

Functional Testing has various phases that must be considered while testing. We'll look
at a variety of interview questions and answers in this section to help you prepare for
your interview.

31. What is the meaning of functional testing?

Ans: Functional testing is a black-box testing technique where the application’s


functionality is tested to come up with anticipated results by offering a specific input.
The role of functional testing is not just to validate the application’s behavior but also to
verify whether the application can be released or not.

32. Define the important steps covered in functional testing?

Ans: Some of the important steps covered in functional testing include:


Understanding the requirement documents and resolving doubts as well as queries in
the review comments

Writing the test cases in regards to the requirement specifications by keeping every
scenario in mind

Discovering the test inputs along with requesting the test data needed to execute the test
cases and check the application’s functionality

Comprehending the real outcomes according to the tested input values

Executing the test cases that understand whether the behavior of the application is as
per the expectation or if any defects are there

33. What is the difference between functional and non-functional testing?

Ans: The difference between functional and non-functional testing is as follows:


Functional Testing Non-Functional Testing

It is performed to comprehend the behavior of the It is the process that helps comprehend whethe
system according to the client's functional needs and performance of the system is according to the c
requirements requirements

Manual and automation testing tools are used to Effective tools are used to perform it after func
perform it testing

It is quite easy to perform It is difficult to perform

Functional testing covers:

Unit Testing Non-functional testing covers:

Regression Testing Performance Testing

Smoke Testing Compatibility Testing

User Acceptance Testing Load, Stress, Volume Testing

Sanity Testing Security Testing

Integration testing
34. What is the difference between build and release?

Ans: The build is one executable file that is regarding the application’s part handed over
to the tester to test the functionalities and fix bugs. The build can also reject the testing
team if it doesn’t have anything critical or major. The release is a software application
that doesn’t exist in the testing phase anymore. It has been handed over to the client.

35. What is the bug cycle?

Ans: A bug refers to an unwanted flaw, mistake, or error occurring in the application and
preventing it from generating the needed result. When any bug is discovered when
testing the application, it goes through a definite cycle, from logging to resolving, known
as the bug life cycle.

36. State some of the bug statuses?

Ans: Some of the bug statuses are:

New: It is when a bug is logged for the first time

Assigned: It is once a bug is logged, it will be reviewed by the team lead and assigned to
the developer team

Open: It is when the tester has logged the bug in the Open state, and it remains so until
the developed has worked on it

Fixed / Resolved: This status comes up when the developer has resolved the bug

Reopen: This status comes if the tester has detected the bug again

Invalid / Not a Bug: It can be marked invalid when the developer reports an issue
according to the functionality but logged because of the misinterpretation

37. What is data-driven testing?


Ans: Data-driven testing is a methodology where a series of test scripts, comprising test
cases, gets executed consistently with the help of data sources, such as SQL database, CSV
file, XML file, or Excel spreadsheet for input values. Here, the real result is compared to
the anticipated one during the verification process.

38. What essential points should be considered when writing test cases?

Ans: Writing a test case is meant to be an essential activity for the test execution process,
requiring writing skills and profound knowledge of the application to make reusable
and effective test cases. Some of the essential points to be kept in mind include:

There should be a precise understanding of the requirements before writing the test
cases. There should be no assumptions or doubts.

Every requirement should be in the form of test cases. Generally, a traceability matrix is
maintained to keep track of every requirement integrated and testing completed.

According to the requirements of document specifications, every non-functional and


functional requirement should be covered.

Test cases should be checked periodically for no redundancy or repetition.

39. Define automation testing?

Ans: Automation testing is one such method that uses an automation tool to execute test
cases suite to improve test coverage and speed to test execution. Automation testing
doesn’t need any human intervention as it executes pre-scripted tests and can compare
and report results with previous test runs.

40. What are stress testing and load testing?

Ans: Stress testing is a performance testing type where the application goes through
stress or exertion, meaning the application is executed above the break threshold to
comprehend the point where it will crash. Usually, this condition comes when there is
too much data or too many users.
Loading testing is a performance testing type where the application gets executed above
a variety of load levels to monitor the server’s peak performance, server throughput,
response time, and more.

41. What is volume testing?

Ans: Volume testing is a performance testing type that comprehends the response time
and server throughput level when concurrent users and large data loads from the
databases are put into the application or system under test.

42. What are different test techniques in functional testing?

Ans: There are two different types of test techniques, such as:

Requirement-Based Testing: This is a functional testing form that is performed by


prioritizing the needs on the basis of risk criteria. This also makes sure that all of the
critical test paths get included in the process.

Business Process-Based Testing: This functional testing form is performed from the
perspective of the business process. The scenarios included in this are business
processes' knowledge.

43. What is exploratory testing?

Ans: Exploratory testing means exploring or testing the application without following
any procedures or schedules. When performing this testing type, testers don’t track any
set patterns but use out-of-the-box thinking and varying ideas to see how the application
will perform.

44. What are the potential login features to be tested for any web
application?

Ans: The potential scenarios to perform so as to test the login feature of an application
fully include:
Checking the fields of inputs, such as username and password, for both invalid and valid
values

Entering a valid email ID with an incorrect password and an invalid email ID with a valid
password

Entering valid credentials to log into the application

Entering the application after logging in and navigating back to the login page to check if
the user is asked to log in again or not

Sign in from a browser and open the application from another browser to check if you
are still logged in

Changing the password after logging in and then trying to log in with the old password

45. What is the importance of accessibility testing?

Ans: In the present scenario, the web is dominating our lives through varying forms,
including online payments, online learning, shopping, and more. Hence, to grow better,
everybody should be a part of technology. With accessibility testing, disabled people can
use the internet with much ease through:

Speech recognition software

Special keyboard

Screen reader software

Screen magnification software

Manual Testing Interview Questions for 3/5/7/8 Years of Experience


If you are an experienced professional working in this domain for 3/5/7/8 years and are
planning to go higher-level in your job, jotted down below are some interview questions
that you should prepare.

46. What will be your strategy if you find a bug during testing?

Ans: When a bug is discovered, we can:

Run additional tests to ensure the problem has a precise description

Run tests to make sure a similar problem does not exist with other inputs

Once the certainty is established, can add more details and then report the bug.

47. How will you test if the requirements have to be frozen yet?

Ans: If the specifications haven’t been frozen for a product, can curate the test plan
based on assumptions regarding the product. However, these assumptions should be
well-documented in the plan.

48. How will you conquer the challenges that occurred because of the
unavailability of documents during the testing?

Ans: In case the standard documents, such as Feature Description Document or System
Requirement Specification are missing, then quality assurance will be based upon the
following references, such as:

Screenshots

Wireframes

A previous version of the application


Another method could be having discussions with developers and business analysts. It
will help resolve doubts and open a channel for bringing transparency to the
requirements.

49. Can you spot the difference between regression testing and retesting?

Ans: Possible differences that we can spot between regression testing and retesting are:

Regression testing ensures the fixed bug doesn’t break other application components,
while the retesting is performed to verify that the defect has been fixed.

With regression test cases, the functionality of all or some modules is verified.

Retesting offers a higher priority in comparison to regression.

50. What would be the key challenges of manual testing?

Ans: As per my understanding, the following are some of the key challenges of manual
testing:

The lack of standard documentation to comprehend the application

Testing the application entirely with the help of optimized test cases

Unavailability of skilled testers

Deciding the test that should be executed first

Understanding the requirements clearly

The ability to know when to stop the testing

51. Define functional and non-functional test cases?


Ans: Functional testing is the testing of the functionality of a product or an application. It
helps test the software’s behavior. Based on the client's requirements, a document,
known as the software specification or requirement specification, gets used to test the
application. On the other hand, non-functional testing is when an application works
according to the user’s expectations, regardless of the condition.

52. What is the meaning of STLC?

Ans: STLC is referred to as Software Testing Life Cycle. It proposes the execution of tests
in a systematic and planner manner. In this model, a lot of activities take place intending
to enhance the product’s quality. This method covers requirement analysis, test
planning, test case development, environment setup, test execution, and test cycle
closure.

53. What is the meaning of a fault?

Ans: A fault is a condition that leads to the failure of software execution when
performing a regarded function.

54. State the difference between a bug, defect, and error?

Ans: An error occurs when there is a slip in coding. This can be discovered by a manual
tester when it becomes a defect. If the development team admits the defect, it becomes a
bug. In case a built code misses the requirements, it turns out to be a functional failure.

55. What is the relationship between severity and priority?

Ans: Severity signifies the depth or gravity of a bug. It helps describe the application’s
perspective. On the other hand, priority talks about the bug that must be fixed on a
priority basis. It also defines the point of view of users.

56. List down the severity types?

Ans: The criticality or the severity of a bug can be high, medium, or low, depending on its
context, such as:
User interface defects come under low severity

Boundary-related defects and error handling defects come under medium severity

Error handling defects, calculation defects, misinterpreted data, hardware failures,


compatibility issues, control flow defects, and load conditions come under high severity

57. Define defect removal efficiency?

Ans: Defect Removal Efficiency (DRE) is a testing metric that indicates the development
team’s efficiency in fixing errors and issues before releasing the software. It is measured
as the ratio of fixed defects to the total number of discovered issues. For instance, if
there were 80 discovered defects during the testing and 60 were fixed, the DRE will be
80/60 = 1.3%.

58. How will you perform automated testing in an environment?

Ans: Automation testing is one such process that helps execute the tests automatically. It
decreases the need for human intervention significantly. Various tools can be used for it,
such as WinRunner, Selenium, and QTP. With the help of testing tools, we can speed up
the testing tasks. Also, these tools help us create test scripts to verify the application and
generate test reports automatically.

59. What is the difference between software testing, quality control, and
quality assurance?

Ans: Software testing is one process that ensures that the product meets the
requirements of users. The objective of performing this test is to discover bugs and fix
them. Hence, it helps maintain the product’s quality so that it can be delivered to the
customer.

Quality Control (QC) is related to the product’s quality. It not just discovers the defects
but also suggests improvements as well. Hence, the testing team is liable for QC.
Quality Assurance (QA) is a systematic and planned way of monitoring the quality of the
entire process, meant to come up with a quality product. It helps track the test reports
and modify the process to fulfill expectations.

60. State the difference between bug release and bug leakage?

Ans: Bug release is when a specific software version is released with known bugs.
Generally, these bugs are of low priority or severity.

Bug leakage happens when a bug is identified by the end customer and missed by the
testing team when testing the software.

Conclusion

Now that you have a comprehensive, in-depth list of manual testing interview questions,
you can definitely prepare well. So, go through these questions repeatedly until you are
ready to give correct answers without pausing in between.

Basic Selenium Interview Questions

1. What is Selenese? And explain its types?

A test scripting language specially used by Selenium for creating test cases is called
Selenese. It's a cross-platform language used for representing Selenium commands. By
using Selenese, we can perform various actions like checking links, different UI
elements, dropdown lists, etc. Besides we can also perform actions like testing Ajax
functionality, scrolling through a page, and a lot more web application features.

[ Related Article: What is Selenium? ]

Mainly selenium commands are of three types:

Actions: Manipulates web application state.


Accessors: Checks the web application state and sorts the results in some variables.

Assertions: Verifies application state corresponding to an expected state specified by the


user.

2. What are the limitations of Selenium?

Doesn't supports desktop applications testing

Unavailability of reliable tech support, as Selenium requires a high level of expertise and
resources to manage.

Since Selenium is open-source software, we need to rely on community forums to get


technical issues resolved.

Doesn’t support automation tests on REST and SOAP platforms.

Limited support for image testing

No built-in reposting and test management feature

Need to rely on third-party tools for testing mobile and desktop applications.

[ Related Article: Selenium Career Opportunities ]

3. List the testing types supported by Selenium?

Types of testing supported by Selenium are as follows:

Acceptance testing: Determines the feature or system that meets customer expectations
and requirements.

Functional testing: Determines if a feature or system functions well without issues.


Performance testing: They are performed to measure how well an application is
performing

Regression testing: Generally, this test is done after a fix, change, or feature is added.

Test-driven development (TDD): It's an iterative development methodology in which


test drives the feature design.

Behavior-driven development (BDD): It's also an iterative development methodology, in


which the objective is to include all the parties in the development of an application.

4. What is the latest version of Selenium?

Selenium's latest version is Selenium 4.0.0 Alpha 5, which is released in March 2020.

Selenium 4.0 comes with new standardization and offers a seamless experience.

The key features of Selenium 4.0 Alpha 5 are:

Improved docker support using domain sockets and the DOCKER_HOST env variable

Replaces OpenTracing with OpenTelemetry.

Instead of creating a client per session, reuses the same HTTP client.
If you want to become a Selenium Certified Specialist, then visit Mindmajix - A Global online
training platform: “Selenium Training”. This course will help you to achieve excellence in this domain
5. What's new in Selenium 4.0?

W3C WebDriver Standardization

Selenium 4 IDE TNG

Refreshed Documentation

Improved Selenium Grid

Better Window and Tab management

Relative locators

6. How can you click on a hyperlink in Selenium?

The below command finds the element using link text and then clicks on that element,
then after the user will be redirected to a corresponding page.

driver.findElement(By.linkText("Today's deals")).click();

The below command finds the element based on the substring of the link in the
parenthesis and partial link text() finds the web element.

driver.findElement(By.partialLinkText("Service")).click();
7. How to add text in the text box without using sendkeys()?

Using JavaScriptExecutor, we can enter text in the text box.

JavascriptExecutor jse = (JavascriptExecutor) driver;

jse.executeScript("document.getElementById('email').value="123.ab@xyz.com
");

8. What is StaleElementReferenceException, and how do you handle it?

Stale means old and no longer new. A stale element means an old element. Any element
present on the webpage is considered as a web element in Web Driver. If the document
object model (DOM) changes, then the web element goes stale. If we try to connect with
any element that is staled, then StaleElementReferenceException is thrown.

The reasons for StaleElementReferenceException thrown are, one is a web element


deleted entirely and the next id element no longer attached to DOM.

To handle StaleElementReferenceException, follow the below-mentioned ways:

Solution 1: Refresh the page and try again for the same element

Sample code to overcome the issue:

driver.navigate().refresh();

driver.findElement(By.xpath("xpath here")).click();

Solution 2: Use try-catch block within for loop, if the element is not found in DOM.

// Using for loop, it tries for 4 times.


// If the element is located for the first time then it breaks from the for loop nad
comeout of the loop

for(int i=0; i<=3;i++){

try{

driver.findElement(By.xpath("xpath here")).click();

break;

catch(Exception e){

Sysout(e.getMessage());

Solution 3: Wait for element till it gets available

wait.until(ExpectedConditions.presenceOfElementLocated(By.id("table")));

Use ExpectedConditions.refreshed to avoid StaleElementReferenceException and


retrieve the element again. This element updates the element by redrawing it accessing
the referenced element.

wait.until(ExpectedConditions.refreshed(ExpectedConditions.stalenessOf("table")));

Solution 4: Handle StaleElementElement Exception by POM.

9. What is the same-origin policy? And how can you avoid it?
The same-origin policy is a critical security mechanism that defines how the script or
document loaded from one origin can associate with a resource from another origin. It
helps to isolate potential malicious documents and rescues from attack vectors.

For example, for a URL http:// http://www.google.com/resources/, the origin is a


combination of a google.com, http, 80 correspondingly. Selenium Core (JavaScript
program) cannot obtain the elements from an origin that is different from where it is
launched.

If we have launched a JavaScript program from "http://www.google.com", then it would


be easy to access pages. To handle the same-origin policy, Selenium RC was introduced.
In this, the server acts as a client-configured HTTP proxy and tricks the browser into
believing Selenium Core and Web application tested are from the same origin.

10. What are locators in Selenium?

Locator in Selenium is a command that tells Selenium IDE about which GUI elements
need to operate. There are various types of locators available in Selenium WebDriver,
and its choice depends largely on the application under test.

Locating by ID: It takes a string parameter which is an ID attribute value and returns the
object to the findElement() method.

driver.findElement(By.id("user"));

Locating by TagName: It locates all elements with a matching tag name.

driver.findElement(By.tagName("button").click());

Locating by Link: The target link can be located using a by.link text locator.

driver.findElement(By.linkText("Today's deals")).click();

Locating by Name: The first element with the name attribute value will return the
location matched.
driver.findElement(By.name("books").click());

Locating by XPath: It takes a string parameter which is XPathExpression and returns it


to an object to findElement() method.

driver.findElement(By.xpath("//span[contains(text(),'an account')]")).getText();

Locating by ClassName: It finds elements based on class attribute value.

driver.findElement(By.className("inputtext"));

Locating by CSS selector: It locates elements based on the drivers underlying the CSS
selector engine.

driver.findElement(By.cssSelector("input#email")).sendKeys("myemail@email.com");

Advanced Selenium Interview Questions

11. How many types of waits are there in Selenium?

Waits are commands in Selenium that are important for executing test scripts.

There are three types of waits in Selenium, such as:

Implicit Wait Type: Implicit wait commands direct Selenium WebDriver to wait for a
certain measure of time before throwing a "no such element" exception.

Syntax:

driver.manage().timeouts().implicitlyWait(10, TimeUnit.SECONDS);

Explicit Wait Type: Explicit wait command directs WebDriver to wait until a certain
condition occurs before proceeding with executing the code.
Syntax:

WebDriverWait wait = new WebDriverWait(WebDriver Reference,TimeOut);

Fluent Wait Type: Fluent wait command defines Selenium WebDriver to wait for a
specific condition to appear. And, also determines the frequency with which Selenium
Webdriver checks the state that appeared before by throwing
"ElementNotVisibleException".

Syntax:

Wait wait = new FluentWait(WebDriver reference)

.withTimeout(timeout, SECONDS)

.pollingEvery(timeout, SECONDS)

.ignoring(Exception.class);

12. What are the most commonly used Browser navigation commands for
Selenium WebDriver?

Navigate To Command: This method loads a new web page in the current browser
window and returns a string as a parameter.

driver.navigate().to(appUrl);

Forward Command: This method does the same operation as the forward button of any
browser. It neither returns nor accepts anything

driver.navigate().forward();

Back Command: This method does the same operation like the back button of any
browser. Neither returns nor accepts anything.
driver.navigate().back();

Refresh Command: This method is used for refreshing the current page.

driver.navigate().refresh();

13. How is the Page Object Model(POM) different from Page Factory?

Page Object Model is a class that represents a web page and its functionality and
members. Page Factory is a way of initializing web elements you want to interact with
the page object while creating an instance of it.

14. How to handle pop-ups in Selenium?

The robot class in Selenium is used to handle mouse and keyboard functions. It closes
the pop windows. Using the WindowHandle() function, we can handle the pop-up
window. By using third-party tools also we can handle pop-ups and other window-based
features.

15. What is the use of switchTo() command in Selenium?

switchTo() Command is used to switch the focus to a new window browser, by supplying
the Window Handle or Window Name as an argument to the Command.

driver.SwitchTo().Window(WindowHandle);

driver.SwitchTo().Window(WindowName);

To get the current Window Handle, use the following command:

String currentWindowHandle = driver.CurrentWindowHandle;

16. How is findElement() different from findElements()?


findElement() is used for accessing a single web element on a page. It returns the order
of the first matching element of the specified order. It throws a NoSuchElementException
when it fails to send the element.

Syntax:

driver.findElement(By.xpath("Value of Xpath"));

findElements() returns the list of all the matching elements. findElements method
returns an empty list when an +element is not available or doesn't exist on the page.

Syntax:

List link = driver.findElements(By.xpath("Value of Xpath"));

17. What is the major difference between "/" and "//" in Xpath?

Single Slash “/”: It is used to create Xpath with an absolute path that is Xpath would be
created to start selection from document node/start node.

/html/body/div[2]/div[1]/div[1]/a

Double Slash "//": It is used to create Xpath with a relative path that is Xpath would be
created to create start selection from anywhere within the document

//div[class="qa-logo"]/a

18. How can you launch a browser using Selenium WebDriver?

The following syntax is used to launch a browser using Selenium WebDriver:

WebDriver driver = new InternetExplorerDriver();

WebDriver driver = new ChromeDriver();


WebDriver driver = new FirefoxDriver();

19. How to verify whether an element is displayed or not on screen in


Selenium?

To verify the visibility of web elements like checkbox, edit box, radio button, etc., use the
following methods:

isdisplayed(): Checks if a web element is present on the screen.

Syntax:

Boolean result = driver.findElement(By.xpath("//span[text()='Coding


Ground']")).isDispayed();

isSelected(): Checks the status of the check box, radio button, and options in the static
dropdown.

Syntax:

Boolean btnresult = driver.findElement(By.xpath("//xpath[contains(@class,'gsc-search-


button')]")).isSelected();

isEnabled(): Checks if an element is enabled or not.

Syntax:

Boolean btnresult = driver.findElement(By.xpath("//xpath[contains(@class,'gsc-search-


button')]")).isEnabled();

20. How to select a value from DropDown using Selenium Webdriver?

The value in the dropdown can be selected using WebDriver's Select class.
Syntax:

select By VisibleText:

Select selectByVisibleText = new Select (driver.findElement(By.id("SelectID_Two")));

selectByVisibleText.selectByVisibleText("Lime");

select By Value:

Select selectByValue = new Select(driver.findElement(By.id("SelectID_One")));

selectByValue.selectByValue("greenvalue");

select By Index:

Select selectByIndex = new Select(driver.findElement(By.id("SelectID_Three")));

selectByIndex.selectByIndex(2);

21. How to handle frames using WebDriver?

The iFrame is an inline frame or web page used for inserting another document within
the current HTML document. It is often used to add content from other sources like an
advertisement on a web page. It is defined with the "iframe" tag.

Select iframe by id

driver.switchTo().frame("ID of the frame");

Locating iframe using tagName

driver.switchTo().frame(driver.findElements(By.tagName("iframe").get(0));
Locating iframe using index

frame(index)

driver.switchTo().frame(0);

Switch to Frame by WebElement

frame(WebElement element)

22. What is the difference between driver.quit() command and


driver.close()?

driver. quit() is used for exiting the browser, tabs, pop-ups, session, etc., whereas the
driver.close() is used to close the web browser window that the user is currently
working on.

23. How to perform mouse hover functions on a web element using


WebDriver?

WebDriver offers a wide range of utilities that users can exploit to automate mouse and
keyboard events. Action interface is one such utility that simulates single user
interactions.

Here are the methods Actions class has provided for Mouse Hover action:

moveToElement(WebElement target)

moveToElement(WebElement target, int xOffset, int yOffset)

24. What are Junit annotations?


Junit annotations in Selenium are used for identifying method types defined in test code.
To execute Selenium WebDriver testing with JUnit, it's necessary to add Junit annotation
in the script.

Commonly used JUnit Annotations in Selenium are listed below:

@BeforeClass

@Before

@Test

@After

@AfterClass

@Ignore

25. Can Captcha be automated?

No, captcha and barcode readers cannot be automated. Captcha functionality is to


ensure that automated programs and bots don't get access to sensitive information -
which is why Selenium cannot automate it.

150 Manual Testing Interview Questions &


Answers for 2022
ByThomas HamiltonUpdatedNovember 12, 2022
We have compiled the most frequently asked manual testing questions and
answers that acquaint you with the type of software tester interview
questions that an interviewer might ask you during your interview. In this
list of interview questions for software testing with answers, we have
covered all commonly asked basic and advanced testing interview
questions for 10 years experience with detailed answers to help you clear
the manual testing job interview easily.

We have covered almost 150+ important software testing viva questions


for freshers candidates as well as manual testing experienced interview
questions for QA Engineers to help prepare for the upcoming interview.
This detailed guide of software testing interview questions for experienced
candidates will help you to crack your Job interview for Software Testing.

List of the Top Manual Testing Interview Questions:

Manual Testing Interview Questions and Answers


for Experienced

1. What is Exploratory Testing?


Exploratory testing is a hands-on approach in which testers are involved in
minimum planning and maximum test execution. The planning involves the
creation of a test charter, a short declaration of the scope of a short (1 to 2
hour) time-boxed test effort, the objectives and possible approaches to be
used. The test design and test execution activities are performed in parallel
typically without formally documenting the test conditions, test cases or
test scripts. This does not mean that other, more formal testing techniques
will not be used. For example, the tester may decide to use boundary value
analysis but will think through and test the most important boundary
values without necessarily writing them down. Some notes will be written
during the exploratory-testing session so that a report can be produced
afterward.

2. What is “use case testing”?

In order to identify and execute the functional requirement of an


application from start to finish “use case” is used and the techniques used
to do this is known as “Use Case Testing.”

3. What is the difference between the STLC (Software Testing Life Cycle)
and SDLC (Software Development Life Cycle)?

SDLC deals with development/coding of the software while STLC deals with
validation and verification of the software

4. What is traceability matrix?


The relationship between test cases and requirements is shown with the
help of a document. This document is known as a traceability matrix.

5. What is Equivalence partitioning testing?

Equivalence partitioning testing is a software testing technique which


divides the application input test data into each partition at least once of
equivalent data from which test cases can be derived. By this testing
method, it reduces the time required for software testing.

6. What is white box testing and list the types of white box testing?

White box testing technique involves selection of test cases based on an


analysis of the internal structure (Code coverage, branches coverage, paths
coverage, condition coverage, etc.) of a component or system. It is also
known as Code-Based testing or Structural testing. Different types of white
box testing are

Statement Coverage

Decision Coverage

7. In white box testing, what do you verify?

In white box testing following steps are verified.


Verify the security holes in the code

Verify the incomplete or broken paths in the code

Verify the flow of structure according to the document specification

Verify the expected outputs

Verify all conditional loops in the code to check the complete functionality
of the application

Verify the line by line coding and cover 100% testing

8. What is black box testing? What are the different black box testing
techniques?

Black box testing is the software testing method which is used to test the
software without knowing the internal structure of code or program. This
testing is usually done to check the functionality of an application. The
different black box testing techniques are

Equivalence Partitioning

Boundary value analysis

Cause-effect graphing
9. What is the difference between static and dynamic testing?

Static testing: During Static testing method, the code is not executed, and it
is performed using the software documentation.

Dynamic testing: To perform this testing the code is required to be in an


executable form.

10. What are verification and validation?

Verification is a process of evaluating software at the development phase. It


helps you to decide whether the product of a given application satisfies the
specified requirements. Validation is the process of evaluating software at
the after the development process and to check whether it meets the
customer requirements.

11. What are the different test levels?

There are four test levels

Unit/component/program/module testing

Integration testing

System testing

Acceptance testing
12. What is Integration testing?

Integration testing is a level of software testing process, where individual


units of an application are combined and tested. It is usually performed
after unit and functional testing.

13. What Test Plans consists of?

Test design, scope, test strategies, approach are various details that Test
plan document consists of.

Test case identifier

Scope

Features to be tested

Features not to be tested

Test strategy & Test approach

Test deliverables

Responsibilities

Staffing and training


Risk and Contingencies

14. What is the difference between UAT (User Acceptance Testing) and
System testing?

System Testing: System testing is finding defects when the system


undergoes testing as a whole; it is also known as end-to-end testing. In such
type of testing, the application suffers from beginning till the end.

UAT: User Acceptance Testing (UAT) involves running a product through a


series of specific tests which determines whether the product will meet the
needs of its users.

15. Mention the difference between Data Driven Testing and Retesting?

Retesting: It is a process of checking bugs that are actioned by the


development team to verify that they are fixed.

Data Driven Testing (DDT): In data driven testing process, the application
is tested with multiple test data. The application is tested with a different
set of values.

Advanced Manual Software Testing Interview


Questions for 3/5/10 Years Experience
16. What are the valuable steps to resolve issues while testing?

Record: Log and handle any problems which have happened

Report: Report the issues to higher level manager

Control: Define the issue management process

17. What is the difference between test scenarios, test cases, and test
script?

Difference between test scenarios and test cases is that

Test Scenarios: A Test Scenario is any functionality that can be tested. It is


also called Test Condition or Test Possibility.

Test Cases: It is a document that contains the steps that have to be


executed; it has been planned earlier.

Test Script: It is written in a programming language and it’s a short


program used to test part of the functionality of the software system. In
other words a written set of steps that should be performed manually.

18. What is Latent defect?

Latent defect: This defect is an existing defect in the system which does not
cause any failure as the exact set of conditions has never been met
19. What are the two parameters which can be useful to know the quality
of test execution?

To know the quality of test execution, we can use two parameters

Defect reject ratio

Defect leakage ratio

Parameters for quality of test execution

20. What is the function of the software testing tool “phantom”?


Phantom is a freeware and is used for windows GUI automation scripting
language. It allows us to take control of windows and functions
automatically. It can simulate any combination of keystrokes and mouse
clicks as well as menus, lists and more.

21. Explain what Test Deliverables is?

Test Deliverables are a set of documents, tools and other components that
have to be developed and maintained in support of testing.

There are different test deliverables at every phase of the software


development lifecycle

Before Testing

During Testing

After the Testing

22. What is mutation testing?

Mutation testing is a technique to identify if a set of test data or test case is


useful by intentionally introducing various code changes (bugs) and
retesting with original test data/ cases to determine if the bugs are
detected.
23. What all things you should consider before selecting automation
tools for the AUT?

Technical Feasibility

Complexity level

Application stability

Test data

Application size

Re-usability of automated scripts

Execution across environment

24. How will you conduct Risk Analysis?

For the risk analysis following steps need to be implemented

Finding the score of the risk

Making a profile for the risk

Changing the risk properties

Deploy the resources of that test risk


Making a database of risk

25. What are the categories of debugging?

Categories for debugging

Brute force debugging

Backtracking

Cause elimination

Program Slicing

Fault tree analysis

26. What is fault masking explain with example?

When the presence of one defect hides the presence of another defect in the
system, it is known as fault masking.

Example: If the “Negative Value” cause a firing of unhandled system


exception, the developer will prevent the negative values input. This will
resolve the issue and hide the defect of unhandled exception firing.
27. Explain what Test Plan is? What is the information that should be
covered in Test Plan?

A test plan can be defined as a document describing the scope, approach,


resources, and schedule of testing activities and a test plan should cover
the following details.

Test Strategy

Test Objective

Exit/Suspension Criteria

Resource Planning

Test Deliverables

28. How can you eliminate the product risk in your project?

It helps you to eliminate product risk in your project, and there is a simple
yet crucial step that can reduce the product risk in your project.

Investigate the specification documents

Have discussions about the project with all stakeholders including the
developer

As a real user walk around the website


29. What is the common risk that leads to project failure?

The common risk that leads to a project failure are

Not having enough human resource

Testing Environment may not be set up properly

Limited Budget

Time Limitations

30. On what basis you can arrive at an estimation for your project?

To estimate your project, you have to consider the following points

Divide the whole project into the smallest tasks

Allocate each task to team members

Estimate the effort required to complete each task

Validate the estimation


31. Explain how you would allocate a task to team members?

Task Member

Analyze software requirement specification All the members

Create the test specification Tester/Test Analyst

Build up the test environment Test administrator

Execute the test cases Tester, a Test administra

Report defects Tester


32. Explain what is testing type and what are the commonly used testing
type?

To get an expected test outcome, a standard procedure is followed which is


referred to as Testing Type.

Commonly used testing types are

Unit Testing: Test the smallest code of an application

API Testing: Testing API created for the application

Integration Testing: Individual software modules are combined and tested

System Testing: Complete testing of the system

Install/UnInstall Testing: Testing done from the point of client/customer


view

Agile Testing: Testing through Agile technique

33. While monitoring your project what all things you have to consider?

The things that have to be taken in considerations are

Is your project on schedule


Are you over budget

Are you working towards the same career goal

Have you got enough resources

Are there any warning signs of impending problems

Is there any pressure from management to complete the project sooner

34. What are the common mistakes which create issues?

Matching resources to wrong projects

Test manager lack of skills

Not listening to others

Poor Scheduling

Underestimating

Ignoring the small problems

Not following the process


35. What does a typical test report contain? What are the benefits of test
reports?

A test report contains the following things:

Project Information

Test Objective

Test Summary

Defect

The benefits of test reports are:

Current status of project and quality of product are informed

If required, stakeholder and customer can take corrective action

A final document helps to decide whether the product is ready for release

36. What is test management review and why it is important?

Management review is also referred to as Software Quality Assurance or


SQA. SQA focusses more on the software process rather than the software
work products. It is a set of activities designed to make sure that the project
manager follows the standard process. SQA helps test manager to
benchmark the project against the set standards.
37. What are the best practices for software quality assurance?

The best practices for an effective SQA implementation is

Continuous Improvement

Documentation

Tool Usage

Metrics

Responsibility by team members

Experienced SQA auditors

38. When is RTM (Requirement Traceability Matrix) prepared?

RTM is prepared before test case designing. Requirements should be


traceable from review activities.

39. What is the difference between Test matrix and Traceability matrix?

Test Matrix: Test matrix is used to capture actual quality, effort, the plan,
resources and time required to capture all phases of software testing
Traceability Matrix: Mapping between test cases and customer
requirements is known as Traceability Matrix

40. In manual testing what are stubs and drivers?

Both stubs and drivers are part of incremental testing. In incremental


testing, there are two approaches namely bottom-up and top-down
approach. Drivers are used in bottom-up testing and stub is used for a top-
down approach. In order to test the main module, the stub is used, which is
a dummy code or program.

41. What is the step you would follow once you find the defect?

Once a defect is found you would follow the step

a) Recreate the defect

b) Attach the screenshot

c) Log the defect

42. Explain what is “Test Plan Driven” or “Key Word Driven” method of
testing?
This technique uses the actual test case document developed by testers
using a spreadsheet containing special “key Words”. The key words control
the processing.

43. What is the DFD (Data Flow Diagram)?

When a “flow of data” through an information system is graphically


represented, then it is known as Data Flow Diagram. It is also used for the
visualization of data processing.

44. Explain what LCSAJ is?

LCSAJ stands for ‘linear code sequence and jump.’ It consists of the
following three items

a) Start of the linear sequence of executable statements

b) End of the linear sequence

c) The target line to which control flow is transferred at the end of the
linear sequence

45. Explain what N+1 testing is?


The variation of regression testing is represented as N+1. In this technique,
the testing is performed in multiple cycles in which errors found in test
cycle ‘N’ are resolved and re-tested in test cycle N+1. The cycle is repeated
unless there are no errors found.

46. What is Fuzz testing and when it is used?

Fuzz testing is used to detect security loopholes and coding errors in


software. In this technique, random data is added to the system in an
attempt to crash the system. If vulnerability persists, a tool called fuzz
tester is used to determine potential causes. This technique is more useful
for bigger projects but only detects a major fault.

47. Mention what the main advantages of statement coverage metric of


software testing are?

The benefit of statement coverage metric is that

a) It does not require processing source code and can be applied directly to
object code

b) Bugs are distributed evenly through the code, due to which percentage
of executable statements covered reflects the percentage of faults
discovered

48. How to generate test cases for “replace a string” method?


a) If characters in new string > characters in the previous string. None of
the characters should get truncated

b) If characters in new string< characters in the previous string. Junk


characters should not be added

c) Spaces after and before the string should not be deleted

d) String should be replaced only for the first occurrence of the string

49. How will you handle a conflict amongst your team members?

I will talk individually to each person and note their concerns

I will find a solution to the common problems raised by team members

I will hold a team meeting, reveal the solution and ask people to co-operate

50. Mention what are the categories of defects?

Mainly there are three defect categories

Wrong: When a requirement is implemented incorrectly

Missing: It is a variance from the specification, an indication that a


specification was not implemented or a requirement of the customer is not
met
Extra: A requirement incorporated into the product that was not given by
the end customer. It is considered as a defect because it is a variance from
the existing requirements

51. Explain how does a test coverage tool work?

The code coverage testing tool runs parallel while performing testing on
the actual product. The code coverage tool monitors the executed
statements of the source code. When the final testing is done, we get a
complete report of the pending statements and also get the coverage
percentage.

52. Mention what the difference between a “defect” and a “failure” in


software testing is?

In simple terms when a defect reaches the end customer, it is called a


failure while the defect is identified internally and resolved; then it is
referred to as a defect.

53. Explain how to test documents in a project that span across the
software development lifecycle?

The project span across the software development lifecycle in the following
manner
Central/Project test plan: It is the main test plan that outlines the complete
test strategy of the project. This plan is used till the end of the software
development lifecycle

Acceptance test plan: This document begins during the requirement


phase and is completed at the final delivery

System test plan: This plan starts during the design plan and proceeds until
the end of the project

Integration and Unit test plan: Both these test plans start during the
execution phase and last until the final delivery

54. Explain which test cases are written first black boxes or white boxes?

Black box test cases are written first as to write black box test cases; it
requires project plan and requirement document all these documents are
easily available at the beginning of the project. While writing white box test
cases requires more architectural understanding and is not available at the
start of the project.

55. Explain what the difference between latent and masked defects is?

Latent defect: A latent defect is an existing defect that has not caused a
failure because the sets of conditions were never met

Masked defect: It is an existing defect that has not caused a failure because
another defect has prevented that part of the code from being executed
56. Mention what bottom-up testing is?

Bottom-up testing is an approach to integration testing, where the lowest


level components are tested first, then used to facilitate the testing of
higher level components. The process is repeated until the component at
the top of the hierarchy is tested.

57. Mention what the different types of test coverage techniques are?

Different types of test coverage techniques include

Statement Coverage: It verifies that each line of source code has been
executed and tested

Decision Coverage: It ensures that every decision in the source code is


executed and tested

Path Coverage: It ensures that every possible route through a given part of
the code is executed and tested

58. Mention what the meaning of breath testing is?

Breath testing is a test suite that exercises the full functionality of a product
but does not test features in detail
59. Explain what the meaning of Code Walk Through is?

Code Walk Through is the informal analysis of the program source code to
find defects and verify coding techniques

60. Mention what the basic components of defect report format are?

The essential components of defect report format include

Project Name

Module Name

Defect detected on

Defect detected by

Defect ID and Name

Snapshot of the defect

Priority and Severity status

Defect resolved by

Defect resolved on
61. Mention what the purpose behind doing end-to-end testing is?

End-to-end testing is done after functional testing. The purpose behind


doing end-to-end testing is that

To validate the software requirements and integration with external


interfaces

Testing application in real-world environment scenario

Testing of interaction between application and database

62. Explain what it means by test harness?

A test harness is configuring a set of tools and test data to test an


application in various conditions, and it involves monitoring the output
with expected output for correctness.

63. Explain in a testing project what testing activities would you


automate?

In testing project testing activities, you would automate are

Tests that need to be run for every build of the application


Tests that use multiple data for the same set of actions

Identical tests that need to be executed using different browsers

Mission critical pages

A transaction with pages that do not change in a short time

64. What is the MAIN benefit of designing tests early in the life cycle?

It helps prevent defects from being introduced into the code.

65. What is risk-based testing?

Risk-based Testing is the term used for an approach to creating a Test


Strategy that is based on prioritizing tests by risk. The basis of the
approach is a detailed risk analysis and prioritizing of risks by risk level.
Tests to address each risk are then specified, starting with the highest risk
first.

66. What is the KEY difference between preventative and reactive


approaches to testing?

Preventative tests are designed early; reactive tests are designed after the
software has been produced.
67. What is the purpose of exit criteria?

The purpose of exit criteria is to define when a test level is completed.

68. What determines the level of risk?

The likelihood of an adverse event and the impact of the event determine
the level of risk.

69. When is used Decision table testing?

Decision table testing is used for testing systems for which the specification
takes the form of rules or cause-effect combinations. In a decision table, the
inputs are listed in a column, with the outputs in the same column but
below the inputs. The remainder of the table explores combinations of
inputs to define the outputs produced.

70. Why we use decision tables?


The techniques of equivalence partitioning and boundary value analysis
are often applied to specific situations or inputs. However, if different
combinations of inputs result in different actions being taken, this can be
more difficult to show using equivalence partitioning and boundary value
analysis, which tend to be more focused on the user interface. The other
two specification-based techniques, decision tables, and state transition
testing are more focused on business logic or business rules. A decision
table is a good way to deal with combinations of things (e.g., inputs). This
technique is sometimes also referred to as a ’cause-effect’ table. The reason
for this is that there is an associated logic diagramming technique called
’cause-effect graphing’ which was sometimes used to help derive the
decision table

71. What is the MAIN objective when reviewing a software deliverable?

To identify defects in any software work product.

72. Which of the following defines the expected results of a test? Test
case specification or test design specification.

Test case specification defines the expected results of a test.

73. What is the benefit of test independence?

It avoids author bias in defining effective tests.


74. As part of which test process do you determine the exit criteria?

The exit criteria are determined on the bases of ‘Test Planning’.

75. What is Alpha testing?

Pre-release testing by end user representatives at the developer’s site.

76. What is beta testing?

Testing performed by potential customers at their own locations.

77. Mention what the difference between Pilot and Beta testing is?

The difference between a pilot and beta testing is that pilot testing is
actually done using the product by the group of users before the final
deployment, and in beta testing, we do not input real data, but it is installed
at the end customer to validate if the product can be used in production.

78. Given the following fragment of code, how many tests are required
for 100% decision coverage?
if width > length

thenbiggest_dimension = width

if height > width

thenbiggest_dimension = height

end_if

elsebiggest_dimension = length

if height > length

thenbiggest_dimension = height

end_if

end_if

79. You have designed test cases to provide 100% statement and 100%
decision coverage for the following fragment of code. if width > length
then biggest_dimension = width else biggest_dimension = length end_if
The following has been added to the bottom of the code fragment above.
print “Biggest dimension is ” &biggest_dimensionprint “Width: ” & width
print “Length: ” & length How many more test cases are required?
None, existing test cases can be used.

80. What is the difference between Testing Techniques and Testing


Tools?

Testing technique: – Is a process for ensuring that some aspects of the


application system or unit functions properly there may be few techniques
but many tools.

Testing Tools: – Is a vehicle for performing a test process. The tool is a


resource to the tester, but itself is insufficient to conduct testing

Learn More About Testing Tools here

81. We use the output of the requirement analysis, the requirement


specification as the input for writing …

User Acceptance Test Cases

82. Repeated Testing of an already tested program, after modification, to


discover any defects introduced or uncovered as a result of the changes
in the software being tested or in another related or unrelated software
component:

Regression Testing
83. A wholesaler sells printer cartridges. The minimum order quantity is
5. There is a 20% discount for orders of 100 or more printer cartridges.
You have been asked to prepare test cases using various values for the
number of printer cartridges ordered. Which of the following groups
contain three test inputs that would be generated using Boundary Value
Analysis?

4, 5, 99

84. What is component testing?

Component testing, also known as unit, module, and program testing,


searches for defects in and verifies the functioning of software (e.g.,
modules, programs, objects, classes, etc.) that are separately testable.
Component testing may be done in isolation from the rest of the system
depending on the context of the development life cycle and the system.
Most often stubs and drivers are used to replace the missing software and
simulate the interface between the software components simply. A stub is
called from the software component to be tested; a driver calls a
component to be tested.

85. What is functional system testing?

Testing the end to end functionality of the system as a whole is defined as a


functional system testing.
86. What are the benefits of Independent Testing?

Independent testers are unbiased and identify different defects at the same
time.

87. In a REACTIVE approach to testing when would you expect the bulk
of the test design work to be begun?

The bulk of the test design work begun after the software or system has
been produced.

88. What are the different Methodologies in Agile Development Model?

There are currently seven different agile methodologies that I am aware of:

Extreme Programming (XP)

Scrum

Lean Software Development

Feature-Driven Development

Agile Unified Process


Crystal

Dynamic Systems Development Model (DSDM)

89. Which activity in the fundamental test process includes evaluation of


the testability of the requirements and system?

A ‘Test Analysis’ and ‘Design’ includes evaluation of the testability of the


requirements and system.

90. What is typically the MOST important reason to use risk to drive
testing efforts?

Because testing everything is not feasible.

91. What is random/monkey testing? When is it used?

Random testing is often known as monkey testing. In such type of testing


data is generated randomly often using a tool or automated mechanism.
With this randomly generated input, the system is tested, and results are
analyzed accordingly. These testing are less reliable; hence it is normally
used by the beginners and to see whether the system will hold up under
adverse effects.
92. Which of the following are valid objectives for incident reports?

Provide developers and other parties with feedback about the problem to
enable identification, isolation, and correction as necessary.

Provide ideas for test process improvement.

Provide a vehicle for assessing tester competence.

Provide testers with a means of tracking the quality of the system under
test.

93. Consider the following techniques. Which are static and which are
dynamic techniques?

Equivalence Partitioning.

Use Case Testing.

Data Flow Analysis.

Exploratory Testing.

Decision Testing.

Inspections.

Data Flow Analysis and Inspections are static; Equivalence Partitioning, Use
Case Testing, Exploratory Testing and Decision Testing are dynamic.
94. Why are static testing and dynamic testing described as
complementary?

Because they share the aim of identifying defects but differ in the types of
defect they find.

95. What are the phases of a formal review?

In contrast to informal reviews, formal reviews follow a formal process. A


typical formal review process consists of six main steps:

Planning

Kick-off

Preparation

Review meeting

Rework

Follow-up.

96. What is the role of moderator in the review process?


The moderator (or review leader) leads the review process. He or she
determines, in co-operation with the author, the type of review, approach
and the composition of the review team. The moderator performs the entry
check and the follow-up on the rework, in order to control the quality of the
input and output of the review process. The moderator also schedules the
meeting, disseminates documents before the meeting, coaches other team
members, paces the meeting, leads possible discussions and stores the data
that is collected.

Learn More about Review process in Video Tutorial here

97. What is an equivalence partition (also known as an equivalence


class)?

An input or output ranges of values such that only one value in the range
becomes a test case.

98. When should configuration management procedures be


implemented?

During test planning.

99. A Type of Functional Testing, which investigates the functions


relating to the detection of threats, such as virus from malicious
outsiders?
Security Testing

100. Testing wherein we subject the target of the test, to varying


workloads to measure and evaluate the performance behaviors and the
ability of the target and the test to continue to function properly under
these different workloads?

Load Testing

101. Testing activity which is performed to expose defects in the


interfaces and in the interaction between integrated components is?

Integration Level Testing

102. What are the Structure-based (white-box) testing techniques?

Structure-based testing techniques (which are also dynamic rather than


static) use the internal structure of the software to derive test cases. They
are commonly called ‘white-box’ or ‘glass-box’ techniques (implying you
can see into the system) since they require knowledge of how the software
is implemented, that is, how it works. For example, a structural technique
may be concerned with exercising loops in the software. Different test
cases may be derived to exercise the loop once, twice, and many times. This
may be done regardless of the functionality of the software.
103. When should “Regression Testing” be performed?

After the software has changed or when the environment has


changed Regression testing should be performed.

104. What is negative and positive testing?

A negative test is when you put in an invalid input and receives errors.
While positive testing is when you put in a valid input and expect some
action to be completed in accordance with the specification.

105. What is the purpose of a test completion criterion?

The purpose of test completion criterion is to determine when to stop


testing

106. What can static analysis NOT find?

For example memory leaks.

107. What is the difference between re-testing and regression testing?


Re-testing ensures the original fault has been removed; regression testing
looks for unexpected side effects.

108. What are the Experience-based testing techniques?

In experience-based techniques, people’s knowledge, skills, and


background are a prime contributor to the test conditions and test cases.
The experience of both technical and business people is important, as they
bring different perspectives to the test analysis and design process. Due to
previous experience with similar systems, they may have insights into what
could go wrong, which is very useful for testing.

109. What type of review requires formal entry and exit criteria,
including metrics?

Inspection

110. Could reviews or inspections be considered part of testing?

Yes, because both help detects faults and improves quality.

111. An input field takes the year of birth between 1900 and 2004 what
the boundary values for testing this field are?
1899,1900,2004,2005

112. Which of the following tools would be involved in the automation of


regression test? a. Data tester b. Boundary tester c. Capture/Playback d.
Output comparator.

d. Output comparator

113. To test a function, what has to write a programmer, which calls the
function to be tested and pass test data.

Driver

114. What is the one Key reason why developers have difficulty testing
their own work?

Lack of Objectivity

115. “How much testing is enough?”

The answer depends on the risk for your industry, contract and special
requirements.
116. When should testing be stopped?

It depends on the risks for the system being tested. There are some criteria
based on which you can stop testing.

Deadlines (Testing, Release)

Test budget has been depleted

Bug rate fall below a certain level

Test cases completed with certain percentage passed

Alpha or beta periods for testing ends

Coverage of code, functionality or requirements are met to a specified point

117. Which of the following is the primary purpose of the integration


strategy for integration testing in the small?

The primary purpose of the integration strategy is to specify which


modules to combine when and how many at once.

118. What are semi-random test cases?


Semi-random test cases are nothing, but when we perform random test
cases and do equivalence partitioning to those test cases, it removes
redundant test cases, thus giving us semi-random test cases.

119. Given the following code, which statement is true about the
minimum number of test cases required for full statement and branch
coverage?

Read p

Read q

IF p+q> 100

THEN Print “Large”

ENDIF

IF p > 50

THEN Print “p Large”

ENDIF

1 test for statement coverage, 2 for branch coverage


120. Which review is normally used to evaluate a product to determine
its suitability for the intended use and to identify discrepancies?

Technical Review.

121. Faults found should be originally documented by whom?

By testers.

122. Which is the current formal world-wide recognized documentation


standard?

There isn’t one.

123. Which of the following is the review participant who has created the
item to be reviewed?

Author

124. A number of critical bugs are fixed in software. All the bugs are in
one module, related to reports. The test manager decides to do
regression testing only on the reports module.
Regression testing should be done on other modules as well because fixing
one module may affect other modules.

125. Why does the boundary value analysis provide good test cases?

Because errors are frequently made during programming of the different


cases near the ‘edges’ of the range of values.

126. What makes an inspection different from other review types?

It is led by a trained leader, uses formal entry and exit criteria and
checklists.

127. Why can be tester dependent on configuration management?

Because configuration management assures that we know the exact version


of the testware and the test object.

128. What is V-Model?

A software development model that illustrates how testing activities


integrate with software development phases
129. What is maintenance testing?

Triggered by modifications, migration or retirement of existing software

130. What is test coverage?

Test coverage measures in some specific way the amount of testing


performed by a set of tests (derived in some other way, e.g., using
specification-based techniques). Wherever we can count things and can tell
whether or not each of those things has been tested by some test, then we
can measure coverage.

131. Why is incremental integration preferred over “big bang”


integration?

Because incremental integration has better early defects screening and


isolation ability

132. What is called the process starting with the terminal modules?

Bottom-up integration
133. During which test activity could fault be found most cost-
effectively?

During test planning

134. The purpose of the requirement phase is

To freeze requirements, to understand user needs, to define the scope of


testing

135. Why we split testing into distinct stages?

We split testing into distinct stages because of the following reasons,

Each test stage has a different purpose

It is easier to manage to test in stages

We can run different test into different environments

Performance and quality of the testing is improved using phased testing

136. What is DRE?


In order to measure test effectiveness, a powerful metric is used to
measure test effectiveness known as DRE (Defect Removal Efficiency) From
this metric we would know how many bugs we have found from the set of
test cases. The formula for calculating DRE is

DRE=Number of bugs while a testing/number of bugs while testing +


number of bugs found by a user

137. Which of the following is likely to benefit most from the use of test
tools providing test capture and replay facilities? a) Regression testing
b) Integration testing c) System testing d) User acceptance testing

Regression testing

138. How would you estimate the amount of re-testing likely to be


required?

Metrics from previous similar projects and discussions with the


development team

139. What studies data flow analysis?

The use of data on paths through the code.


140. What is failure?

Failure is a departure from specified behavior.

141. What are Test comparators?

Is it really a test if you put some inputs into some software, but never look
to see whether the software produces the correct result? The essence of
testing is to check whether the software produces the correct result and to
do that, and we must compare what the software produces to what it
should produce. A test comparator helps to automate aspects of that
comparison.

142. Who is responsible for document all the issues, problems and open
point that were identified during the review meeting

Scribe

143. What is the main purpose of Informal review

An inexpensive way to get some benefit

144. What is the purpose of test design technique?


Identifying test conditions and Identifying test cases

145. When testing a grade calculation system, a tester determines that


all scores from 90 to 100 will yield a grade of A, but scores below 90 will
not. This analysis is known as:

Equivalence partitioning

146. A test manager wants to use the resources available for the
automated testing of a web application. The best choice is

Tester, test automater, web specialist, DBA

147. During the testing of a module tester, ‘X’ found a bug and assigned it
to a developer. But developer rejects the same, saying that it’s not a bug.
What ‘X’ should do?

Send the detailed information of the bug encountered and check the
reproducibility

148. A type of integration testing in which software elements, hardware


elements, or both are combined all at once into a component or an
overall system, rather than in stages.
Big-Bang Testing

149. In practice, which Life Cycle model may have more, fewer or
different levels of development and testing, depending on the project
and the software product. For example, there may be component
integration testing after component testing, and system integration
testing after system testing.

V-Model

150. Which technique can be used to achieve input and output coverage?
It can be applied to human input, input via interfaces to a system, or
interface parameters in integration testing.

Equivalence partitioning

151. “This life cycle model is driven by schedule and budget risks” This
statement is best suited for.

V-Model

152. In which order should tests be run?


The most important one must be tested first

153. The later in the development life cycle a fault is discovered, the
more expensive it is to fix. Why?

The fault has been built into more documentation, code, tests, etc

154. What is Coverage measurement?

It is a partial measure of test thoroughness.

155. What is Boundary value testing?

Test boundary conditions on, below and above the edges of input and
output equivalence classes. For instance, let say a bank application where
you can withdraw maximum Rs.20,000 and a minimum of Rs.100, so in
boundary value testing we test only the exact boundaries, rather than
hitting in the middle. That means we test above the maximum limit and
below the minimum limit.

156. What does COTS represent?

Commercial Off The Shelf.


157. The purpose of which is to allow specific tests to be carried out on a
system or network that resembles as closely as possible the
environment where the item under test will be used upon release?

Test Environment

158. What can be thought of as being based on the project plan, but with
greater amounts of detail?

Phase Test Plan

159. What is Rapid Application Development?

Rapid Application Development (RAD) is formally a parallel development


of functions and subsequent integration. Components/functions are
developed in parallel as if they were mini projects, the developments are
time-boxed, delivered, and then assembled into a working prototype. This
can very quickly give the customer something to see and use and to provide
feedback regarding the delivery and their requirements. Rapid change and
development of the product are possible using this methodology. However
the product specification will need to be developed for the product at some
point, and the project will need to be placed under more formal controls
before going into production.

You might also like