YouTube Link: https://youtu.be/Zkeqvl8cxGc ** Test Automation Masters Program: https://www.edureka.co/masters-program/automation-testing-engineer-training** This Edureka PPT on "Manual Testing Interview Questions and Answers" will help you to prepare yourself for Software Testing Interviews based on manual testing. It covers manual testing interview questions for beginners, intermediate and experienced professionals. Below topics are covered in this PPT: Top 50 manual testing interview questions 1. Beginners level questions 2. Intermediate level questions 3. Advance level questions Follow us to never miss an update in the future. YouTube: https://www.youtube.com/user/edurekaIN Instagram: https://www.instagram.com/edureka_learning/ Facebook: https://www.facebook.com/edurekaIN/ Twitter: https://twitter.com/edurekain LinkedIn: https://www.linkedin.com/company/edureka Castbox: https://castbox.fm/networks/505?country=in

1. Copyright © 2017, edureka and/or its affiliates. All rights reserved.

2. BEGINNER LEVEL MANUAL TESTING INTERVIEW QUESTIONS
ADVANCED LEVEL MANUAL TESTING INTERVIEW QUESTIONS
www.edureka.co
INTERMEDIATE LEVEL MANUAL TESTING INTERVIEW QUESTIONS

3. www.edureka.co

4. www.edureka.co
01 What is Software Testing? Explain in simple terms.
Software Testing is a process used to identify the correctness, completeness
and the quality of developed compute software. It includes a set of activities
conducted with intent of finding errors in software so that it could be
corrected before the product is released to end users.
www.edureka.co

5. www.edureka.co
02 Why is software testing required? How does testing benefit an organization?
Quality Assurance
No errors in code
Safety Assurance
Bug Free
Multiple OS Support
www.edureka.co

6. www.edureka.co
03 What are the two main categories of software testing?
Manual testing is essentially
self-explanatory — testing of a
web application is done
manually, by human action
Automated testing uses the
assistance of tools, scripts, and
software to perform test cases by
repeating pre-defined actions
www.edureka.co

7. www.edureka.co
04 What exactly is quality control? Is it similar to Quality Assurance?
Quality control is a product-oriented approach of
running a program to determine if it has any
defects, as well as making sure that the software
meets all of the requirements put forth by the
stakeholders.
www.edureka.co

8. www.edureka.co
05 What different types of manual testing are there?
Black-Box Testing
White-Box Testing
Integration Testing
Unit Testing
System Testing
Acceptance Testing
www.edureka.co

9. www.edureka.co
06 Explain the difference between alpha testing and beta testing.
Alpha Testing
Alpha Testing is a type of software testing
performed to identify bugs before releasing the
product to real users or to the public. Alpha
Testing is a type of user acceptance testing.
Beta Testing
Beta Testing is performed by real users of
the software application in a real
environment. Beta Testing is also a type of
user acceptance testing.
www.edureka.co

10. www.edureka.co
07 What are the different levels of manual testing?
Unit
Testing
Integration
Testing
System
Testing
Acceptance
Testing
Testing individual components Testing interface b/w groups
Testing the integrated system Testing the final system
www.edureka.co

11. www.edureka.co
08 What is the difference between quality control and quality assurance?
Quality Control Quality Assurance
Quality control is set of activities for ensuring
quality in the products.
Quality Assurance is a set of activities for
ensuring quality in the processes by which
products are developed.
Aims to identify defects in the finished product. Aims to prevent defects with a focus on process
used to make the product.
Quality control is a product-oriented approach Quality assurance is a process-oriented
www.edureka.co

12. www.edureka.co
09 What is a testbed in manual testing? Explain with help of an example.
Testbed is an environment used for testing an application, including the
hardware as well as any software needed to run the program to be
tested.
Web Server - IIS/Apache
Database - MS SQL
OS - Windows/ Linux
Browser - IE/FireFox
Java version : version 6
www.edureka.co

13. www.edureka.co
10 Explain the procedure for manual testing?
Understand The
Requirements
Write The Test Cases
Conduct The
Tests
Log Good Bug Reports
Report The
Results
www.edureka.co

14. www.edureka.co
11 What is the test case? Explain with help of an example.
A Test Case is a document which consists of a set of conditions or actions which are performed
on the software application in order to verify the expected functionality of the feature
Good Test Coverage
Better Compliance
Low Deployment Risks
Customer Satisfaction
www.edureka.co

15. www.edureka.co
12 What is API testing?
PRESENTATION
LAYER
(User Interface)
BUSINESS LAYER
(Application User
Interface)
DATABASE LAYER
(Database)
GUI Testing on
Presentation Layer
API Testing on
Business Layer
API testing involves testing the application programming interfaces (APIs)
directly and as part of integration testing to determine if they meet expectations
for functionality, reliability, performance, and security.
www.edureka.co

16. www.edureka.co
13 What’s the difference between verification and validation in testing?
Verification
It’s a static analysis
techniques. Here, testing is
done without executing the
code.
Examples:
• Reviews
• Inspection
• Walkthrough
Validation
It’s a dynamic analysis
technique where testing is
done by executing the code.
Examples:
• Functional Testing
• Non-Functional
Testing
www.edureka.co

17. www.edureka.co
14 What’s the difference between a bug and a defect?
Defect can be simply
defined as a variance
between expected
and actual.
A bug is the result of a coding
error. An Error found in the
development environment before
the product is shipped to the
customer.
www.edureka.co

18. www.edureka.co
15 What are the advantages of manual testing?
Live Testing Less Programming
Low Cost Investment
UI & UX Issues
UX
Adaptability to Change
www.edureka.co

19. www.edureka.co
16 What are the disadvantages of manual testing?
Time Consuming
Possibility of Errors
Testing Limitations
www.edureka.co

20. www.edureka.co
17 Is documentation really necessary in Manual Testing?
www.edureka.co

21. www.edureka.co

22. www.edureka.co
18 What is the difference between manual testing and automation testing?
www.edureka.co

23. www.edureka.co
19 When should you opt for manual testing over automation testing?
Short time projects
You can use manual testing when,
When performing ad-hoc testing
When performing exploratory testing
When performing usability testing
www.edureka.co

24. www.edureka.co
20 What are the phases involved in Software Testing Life Cycle?
Requirement
Analysis1
Test Planning2
Test Case
Development3
Test Environment
Setup
4
Test Execution5
Test Cycle
Closure5
www.edureka.co

25. www.edureka.co
21 What is the difference between a bug, a defect and an error?
Defect can be simply defined as a variance between
expected and actual.
A bug is the result of a coding error. An Error found in the
development environment before the product is shipped to
the customer.
An error is a mistake, misunderstanding, or
misconception, on the part of a software developer.
www.edureka.co

26. www.edureka.co
22 What makes a good test engineer?
Communication Skills
‘Test to break’ attitude
Strong desire for quality
Tact and diplomacy
Ability to judge the situations
www.edureka.co

27. www.edureka.co
23 What is regression testing? When to apply it?
Tested
Software
Developed
Software
Feature
Update Regression
Test Plan
Testing of a previously tested program following modification, to ensure that
defects have not been introduced or uncovered in unchanged areas of the
software, as a result of the changes made
www.edureka.co

28. www.edureka.co
24 What is the difference between system testing and integration testing?
System Testing Integration Testing
Tests the software as a whole to check if the
system is compliant with user requirements
Tests the interface between modules of the
software application
Involves both functional and non-functional
testing
Only functional testing is performed
High-level testing performed after integration
testing
Low-level testing performed after unit testing
www.edureka.co

29. www.edureka.co
25 Explain the defect life cycle. What are the phases involved?
A defect life cycle is a
process in which a defect
goes through various
phases during its entire
lifetime. It starts when a
defect is found and ends
when a defect is closed,
after ensuring it’s not
reproduced.
www.edureka.co

30. www.edureka.co
26 What is test harness? Explain.
A test harness is the gathering of software and test information arranged to test a
program unit by running it under changing conditions like stress, load, data-driven, and
monitoring its behaviour and outputs. Test Harness contains two main parts:
✓ A Test Execution Engine
✓ Test script repository
www.edureka.co

31. www.edureka.co
27 What is test closure? Explain.
Test Closure is a document which gives a summary of all the tests
conducted during the software development life cycle and also gives a
detailed analysis of the bugs removed and errors found.
www.edureka.co

32. www.edureka.co
28 What is the difference between Positive and Negative Testing?
www.edureka.co

33. www.edureka.co
29 Define what is a critical bug.
A critical bug is a bug that has got the tendency to affect a
majority of the functionality of the given application.
www.edureka.co

34. www.edureka.co
30 What is pesticide paradox? How to overcome it?
According to pesticide paradox, if the same tests are repeated over and over again,
eventually the same test cases will no longer find new bugs. Solution:
Write a whole new set of test cases
Prepare new test cases and add them to the
existing test cases
www.edureka.co

35. www.edureka.co
31 What is Defect Cascading in Software Testing?
Defect Cascading is the process of triggering other defects in the
application.
Defect
Cascading
• When a defect goes unnoticed while testing, it
invokes other defects.
• multiple defects crop up in the later stages of
development.
www.edureka.co

36. www.edureka.co
32 What is a quality software? Define it in your terms.
In general, quality software is reasonably bug-free, delivered on time
and within budget, meets requirements and/or expectations, and is
maintainable.
But again ‘quality’ is a subjective term
www.edureka.co

37. www.edureka.co
33 What is black box testing, and what are the various techniques?
Black-Box Testing, also known as specification-based testing, analyses the functionality of a
software/application without knowing much about the internal structure/design of the item.
Black-Box Testing Techniques:
➢ Equivalence Partitioning
➢ Boundary Value Analysis
➢ Decision Table Based Technique
➢ Cause-effect Graphing
➢ Use Case Testing
www.edureka.co

38. www.edureka.co
34 What is white box testing, and what are the various techniques?
White-Box Testing also known as structure-based testing, requires a profound
knowledge of the code as it includes testing of some structural part of the
application.
White-Box Testing Techniques:
➢ Statement Coverage
➢ Decision Coverage
➢ Condition Coverage
➢ Multiple Condition Coverage
www.edureka.co

39. www.edureka.co
35 What are the Experience-based testing techniques?
Experienced-based testing is all about discovery, investigation, and learning. The tester constantly
studies and analyzes the product and accordingly applies his skills, traits, and experience to develop test
strategy and test cases to perform necessary testing
Experience Based Testing Techniques:
➢ Exploratory Testing
➢ Error Guessing
www.edureka.co

40. www.edureka.co
36 What is the difference between top-down and bottom-up approach?
Top-Down Approach: Testing happens
from top to bottom. That is, high-
level modules are tested first and after
that low-level modules.
Bottom-Up Approach: Testing happens
from base levels to high-up levels. The
lowest level modules are tested first and
afterward high-level state modules
www.edureka.co

41. www.edureka.co
37 What is the difference between smoke testing and sanity testing?
System Testing Integration Testing
Tests the software as a whole to check if the
system is compliant with user requirements
Tests the interface between modules of the
software application
Involves both functional and non-functional
testing
Only functional testing is performed
High-level testing performed after integration
testing
Low-level testing performed after unit testing
www.edureka.co

42. www.edureka.co
38 What is the difference between static testing and dynamic testing?
www.edureka.co

43. www.edureka.co

44. www.edureka.cowww.edureka.co
How will you
determine when to
stop testing?
39
Deciding when to stop testing can be quite difficult. Òne common
factors in deciding when to stop testing are:
➢ Testcases completed with certain pass %
➢ When bug rate falls below a certain level
➢ When the budget is exhausted
➢ Coverage of code has reached specific point
➢ Considering the deadlines
➢ When beta or alpha testing period ends
www.edureka.co

45. www.edureka.cowww.edureka.co
What if the software is so
buggy it can’t really be
tested at all?40
In such situations, the best bet is for testers to go through
the process of reporting whatever bugs or blocking-type
problems initially show up, with the focus being on critical
bugs
www.edureka.co

46. www.edureka.cowww.edureka.co
How you test a product if the
requirements are yet to
freeze?
41
If the functionality isn’t necessary to the
purpose of the application, it should be
removed. Else, create a test plan based on
the assumptions made about the product.
www.edureka.co

47. www.edureka.cowww.edureka.co
What if an organization is
growing so fast that fixed
testing processes are not
possible? What to do in such
situations?
42
It’s a very common problem faced by
organizations
Hire good and skilled people
Management should ‘ruthlessly prioritize’ quality
issues and maintain focus on the customer
Everyone in the organization should be clear on
what ‘quality’ means to the end-user
www.edureka.co

48. www.edureka.cowww.edureka.co
How do you know the code
has met specifications?43
Code is considered good if it is bug-free, and is readable
and maintainable.
• There are lot of tools like traceability matrix to which
ensures the requirements are mapped to the test
cases.
• And when the execution of all test cases finishes with
a success, it indicates that the code has met the
requirement.
www.edureka.co

49. www.edureka.cowww.edureka.co
What are the cases when
you’ll consider to choose
automated testing over
manual testing?
44
When reports are required for every
execution
When there are repetitive steps
Execution to be done in standard
environment
Lot of code that is to be tested
multiple times
When there is less time to complete
testing
www.edureka.co

50. www.edureka.cowww.edureka.co
What is ‘configuration
management’?45
Software configuration management
(SCM) is a set of processes, policies, and
tools that organize, control, coordinate,
and track:
• code
• documentation
• problems
• change requests
• designs and tools
• compilers and libraries
www.edureka.co

51. www.edureka.cowww.edureka.co
Is it true that we can do
system testing at any stage?46
No. The system testing must start only if all units are in
place and are working properly. System testing usually
happens before the UAT (User Acceptance Testing).
www.edureka.co

52. www.edureka.cowww.edureka.co
What are some best
practices that you should
follow when writing test
cases?
47
✓ Prioritize the test cases based on the project
timelines & risk.
✓ Remember the 80/20 rule.
✓ Don’t try to test cases in one attempt
✓ Classify test cases
✓ Make sure test cases are modular
✓ Keep them simple
✓ Always keep end-users’ requirements in
mind
✓ Actively use a test management tool
✓ Monitor your test cases regularly
www.edureka.co

53. www.edureka.cowww.edureka.co
Why is it that the boundary
value analysis provides good
test cases?
48
Have a talk to respective team member
Try to convince him otherwise regarding
meetings
Explain how they contribute to team’s
progress & performance
If issue is still nor resolved, set up a
meeting with reporting manager
www.edureka.co

54. www.edureka.cowww.edureka.co
Why is it impossible to test a
program thoroughly or in
other terms 100% bug-free?
49
It is impossible to build a software product which is 100%
bug-free. You can just minimize the error, flaw, failure or
fault in a computer program or system that causes it to
produce an incorrect or unexpected result.
www.edureka.co

55. www.edureka.cowww.edureka.co
Can automation testing
replace manual testing?50
Automation testing isn’t a replacement for manual
testing. It’s just a continuation of the manual
testing.
www.edureka.co

56. Copyright © 2017, edureka and/or its affiliates. All rights reserved.
www.edureka.co

57. www.edureka.co