Manual Testing real time questions .pdf

Manual Testing Real Time
Interview Questions
With answers
By : Jaikishan Mohanty
Part - 1

1.Tell Me About You?
● If you are fresher:
I am Jaikishan, I have completed my Computer Engineering in 2021. I have completed
my Testing Course from XYZ institute. I am aware of Testing Methodology, STLC &
SDLC.
My Short Term Goal is to become a Sr. Tester down the line 2 years and long term goal
is to become a Test Manager.
My Strength is – I am a good listener, workaholic & easily gel with others.
Talking about my weakness – Sometimes, I get so excited and caught up in my work that
I forget that my family life should be my number one priority.”

1.Tell Me About You?
● If you are having 1 to 3 Years of exp.:
I am Jaikishan, completed B.Tech in 2019, having around 2+ years of experience in
Software Testing and Automation. Currently working as a Software Test Engineer in XYZ
Company. My Responsibilities includes Test Case Creation and Execution by
understanding Requirements and Functionality, Logging and fixing a Defect, Sending
Build Wise Status Report to my Lead, participation in the client call, and involvement in
writing down Test Plan etc.
My Strength is – I can work under Pressure, Result Oriented, workaholic & easily gel with
others.
Talking about my weakness includes – I lose my efficiency if I work at a stretch for more
than 24 hours.

2. Tell me your Role and Responsibilities?
I am currently working here as a Software Test Engineer. My Responsibilities includes Test Case Creation and
Execution by understanding Requirements and Functionality, Logging and fixing a Defect, Sending Build Wise
Status Report to my Lead, participation in the client call, and involvement in writing down Test Plan etc.
• Prepare Test Cases and Test Data as per the Test Basics
• Peer reviews the Test cases and Test data
• Execute the test cases and record the execution status in the Test Management tool,
• Log all detected defects in the identified defect tracking tool,
• Provides status to the Assignment Manager/ Test Analyst, as and when required.
• Attending the Team Meetings
• Involved in Test Planning
• Ensuring that Deliveries of the application are in time and above expectations

3. Why you think that you are fit for testing? / Why have
you chosen this Testing Field? Why testing, tell me in only
in one sentence? Or what should be the qualities of a
tester?
❖ I know well how to break the thing than to make it &
❖ My attitude towards testing is thoroughly destructive but
my work is constructive
❖ I am having lot of patience
❖ I am always thinking from the end user perspective.
Because of all these reason I think that I am fit for testing

4. What is Software Testing?
→ It is a process of analyzing s/w item to detect the
differences between existing and required conditions
and to evaluate the features of the s/w item.
→ It is a verification and validation process.
→Process of demonstrating that errors are not
present.

5. What should be the mindset of a tester?
★ He should think from the end customer point of view.
★ His attitude towards testing should be thoroughly
destructive but his work should be constructive and
then he will able to find out more and more bugs in
the application.
★ He should be a go-getter and having the ability to
prove his opinion in spite of all odds.
★ Having Lot of patience.

6. At what stage of the SDLC does testing begin in your
opinion? When should testing start in your project? Why?
In SDLC testing begin from the Requirement Gathering stage. But
here in this stage we are testing the ideas not a code. We are
testing following things during Requirement gathering stage
➢ Is this the right requirement?
➢ Are they complete?
➢ Are they compatible?
➢ Are they achievable?
➢ Are they testable? Etc.

7. What is Quality?
Quality is nothing but degree of excellence with
reference to customer satisfactions.

9. DIFFERENCE BETWEEN VERIFICATION AND
VALIDATION?
Verification→
o It is a process of confirming whether the s/w meets it’s requirement or not.
o Process of examining/reviewing of work product.
o Are we building the product right?
o It is a QA activity.
o It is performed by a QA team or by developer.
o Cost and time effective.
o Activities involve in this is testing the application.

9. DIFFERENCE BETWEEN VERIFICATION AND
VALIDATION?
Validation→
o It is a process of confirming whether the s/w meets user’s requirement or not.
o Process of executing a product & examining how it behaves.
o Are we building the right product?
o It is a QC activity.
o It is performed by a QC team or by tester.
o Cost and time taking.
o Activities involve in this are inspections, reviews, walk-through.

10. Explain SDLC?
Software Development Life Cycle refers to all the
activities that are performed during software
development, including - requirement analysis,
designing, implementation, testing, deployment
and maintenance phases.

Part 2 will be coming soon.
Stay tuned with our channel.
Subscribe for notification. [Mohanty Academy]
Join Telegram for PDF file
https://t.me/Mohanty_Academy
THANK YOU

Interview Questions
With answers
Part - 2

11.Tell me different SDLC models?
Different SDLC models are :
➔ Water Fall Model
➔ Spiral Model
➔ Code & Fix Model
➔ Big Bang Model
➔ Scrum Model
➔ Prototype Model
➔ V Model

12. Which SDLC Models you are using? Explain in details.
Or Which development module is used in your organization?
We are using Agile Methodology for developing software and the Models we used are
SCRUM.
In Scrum, projects are divided into small group of requirements, called as sprints,
which are typically one week, two weeks, or three weeks in duration.
In Scrum we have a SCRUM Master who acts a Bridge between Product owner and
Development Team. Based on the size of sprints DEV & Test Team will provide the
estimations to our SCRUM Master in terms of hours. Then SCRUM Master will
publish the release Schedule by Date.
We have a daily SCRUM Meeting where we discussed about the Progress of Sprint
from Dev, Test and Analysis point of view on daily basis. If anything is blocking to us
we are discussing that also in the SCRUM meeting

13. What is the Advantage of Scrum Model /Agile
methodology?
❖ Very Productive
❖ Business gets something new after every 2 or 3
weeks.
❖ New Ideas go into TO DO List.
❖ Due to small sprints Tester & Developer can focus
well on the given functionality.

14. What is Regression Testing?
Regression Testing is nothing but to test the known set of
test cases to ensure that nothing has been affected
either due to bug fix or any new enhancement.
➔ Basically Regression Testing is used to find out the
side effect of existing functionality on other
functionality.

15. Tell me the difference between Regression testing and
retesting?
Regression Testing is nothing but to test the known set of test cases to ensure
that nothing has been affected either due to bug fix or addition of any new
enhancement. Basically Regression Testing is used to find out the side effect of
existing functionality on other functionality.
&
Retesting is nothing but testing the same thing with different set of data.
For example: Testing the Login Functionality with different set of user i.e. user
with administrative role, user with DB admin role, user with Account Manager
Role etc. So here we are testing the login functionality again and again with
different set of data

16. How to identify the regression test cases? Why
need of regression testing?
❏ If Functionality B(Forget P/w) is depending on Functionality A(Registration)
and with the change in Functionality A if the Functionality B is getting
affected then all the test cases related to functionality B will be our
regression test cases.
❏ And If Functionality A & B are interdependent then all the test cases
related functionality A & B will be our regression test cases.
➢ By using regression testing we will ensure that nothing has been
affected either due to bug fix or addition of any new enhancement.

17. Regression: what is it? How will u run all
regression suite if u have less time?
Definition same as previous.
Even though we have less time available we need to
execute all the Regression Suite by sitting late nights
or coming over weekend to ensure that all the
functionalities are working fine. We cannot take a
risk of excluding some test cases from execution.

18. WHAT IS DYNAMIC TESTING?
It involves in the execution of code. It validates
the output with the expected outcome.

19. WHAT IS STATIC TESTING?
It involves in reviewing the documents to identify
the defects in the early stages of SDLC.

20. EXPLAIN STLC - Software Testing life cycle.
Software testing life cycle refers to all the activities performed
during testing of a software product. The phases include-
• Requirement analyses and validation - In this phase the
requirements documents are analysed and validated and
scope of testing is defined.
• Test planning - In this phase test plan strategy is defined,
estimation of test effort is defined along with automation
strategy and tool selection is done.

20. EXPLAIN STLC - Software Testing life cycle.
• Test Design and analysis - In this phase test cases are designed,
test data is prepared and automation scripts are implemented.
• Test environment setup - A test environment closely simulating
the real world environment is prepared.
• Test execution - The test cases are prepared, bugs are reported
and retested once resolved.
• Test closure and reporting - A test closure report is prepared
having the final test results summary, learning and test metrics.

THANK YOU

Interview Questions
With answers
Part - 3

21.Tell me the difference between Scenario and Use Case
and Test Case? Or difference between Scenario and Test
Case?
➔ Scenario is nothing but how the End User will use the given
functionality in real time environment.
➔ While UseCase is nothing but the interaction of the end user with
that application.
➔ For Example: ATM Machine, here the functionality of the ATM
machine is to give the money to the end user.

➔ a.) Consider a Scenario where user wants to give Rs.70 to the Taxi
Owner during mid night and he don’t have money in his wallet. He
goes to ATM Machine and trying to withdraw the money from ATM but
ATM can dispense only Rs. 500 and Rs.1000 notes. In that case
even if the functionality wise ATM machine is working fine but it will
not satisfy the end user requirement as it will not solve his purpose
due to unavailability of smaller note.
➔ b.) Consider another scenario where user wants to carry Rs. 1 Lac
from one station to another. He goes to ATM center to withdraw the
amount and here he gets all the 100 Rs notes. In this case even
though functionality wise ATM Machine is working fine but it will not
satisfy the end user requirement as he is looking for a Rs. 500 or Rs.
1000 notes so that he can easily carry small number of notes.

➢ UseCase here in the give example is User will insert his Debt/Credit
Card in the ATM Machine, then he will enter the PIN number , then he
will select the type of Account & then he will enter the amount and
select yes/no Transactions Slips and finally press enter to perform the
complete operation.
➢ Test Cases in the above example is to verify the behavior of ATM
Machine --
○ For valid or Invalid Debit/Credit Card?
○ For the Expiry Date > or < or = today’s date for the given
Debit/Credit Card?
○ For Correct/Incorrect PIN, Minimum and Maximum PIN etc.
○ For the Amount > Available balance in his Account
○ For the Amount < or = Available balance in his account
○ For the amount <= 0 etc

22. Which 3 important scenario you will test as manager on
calculator before it is going to production?
Scenario is nothing but how the End User will use the given
functionality in real time environment. So when end user will take this
Calculator for UAT he will test following scenario:
● Whether all the Letters are visible and after pressing specific
letter whether the value is getting displayed on the display
window. E.g. after pressing “2” button, 2 should display on
calculator window.
● Performing Addition/Multiplication/Subtraction & Division on 2
Maximum numbers.
● Whether all the invalid operation is properly handled or not. E.g.
divide by zero.

23. Write scenario on Login window? Or How will you test
the login functionality of the application or tell me your
approach of testing the login functionality of the application?
Scenario on Login Window would be
❖ User tries to perform login by entering Valid Username & Invalid Password.
❖ User tries to perform login by entering Invalid Username and Valid Password.
❖ User tries to perform login by entering Invalid Username and invalid Password.
❖ User tries to perform login by without entering any Username and Password.
❖ User tries to perform login by entering Special Characters for Username and
password.
❖ User tries to perform login by entering maximum characters that specified for
the username and password fields

24. Tell me the different Scenarios on Chair/Mobile/Mixer
etc
So On Chair (Assume that it’s a Normal Plastic Chair) the scenario would be
● Effect of Environmental condition on this chair as this chair may be used in any
environmental condition.
● Reaction of Raw Material of chair on the human body.
● User can also use it for sitting purpose outside home so here we need consider
the rough & toughness of this chair.
● User can use it for standing purpose in order to remove the things from the loft
so here we need to consider the impact of pressure at a given area on this
chair.
● Small kids may play with this chair so here we need to consider the scenario
that its corner may harm the kids.

Mixer Scenario :
So on Mixer the scenario would be:
● User may use this Mixer where the available voltage is given specified minimum voltage.
So here we need to test the scenario that where this mixture will work fine or not for the
given desired low voltage. The same thing is applicable for High Voltage.
● User may use this mixture for a longer period of time on the given voltage range. So effect
of induced heat on the material of the mixture.
● User may use this mixture for crushing the very hard material which is not mentioned in the
specification. So here we need to test the scenario that what should be the effect of this on
the mixture and end user.
● User may use this mixture with wet hand, so here we need to test the scenario that
whether it is properly shock proof or not.
● What is user is going to crush the material in the given pot without holding the pot by hand,
so here we need to test the scenario whether proper locking system are provided or not.
Etc

Mobile Scenario :
● After inserting the SIM whether it is capturing the signal or
not.
● What if user is on a call while charging the mobile?
● After dialing the number it should call the same person.
● Based on the selected profile it is behaving or not?
● After plugging the charger pin where it is properly getting
charged or not.
● While continuous talking on mobile where it is getting
heated or not? Etc.

25. if C= a+b /a-b? What is scenario for this equation?
Scenario for the given equation would be:
➢ Similar Negative value for both a and b, to test the scenario of divide by
zero.
➢ Similar Negative and Positive Value for a & b, to test the scenario of
infinity.
➢ Any value for a and 0 value for b, to test the scenario of getting result 1.
➢ 0 value for a and any value for b,to test the scenario of getting result -1.
➢ Any two different value for a & b where the value of a>b to test the
positive output.
➢ Any two different value for a & b where the value of b>a to the negative
output.

THANK YOU

Interview Questions
With answers
Part - 4

26.WHAT IS WHITE BOX TESTING?
o This also called as glass-box testing, clear-box and structural testing.
o It is based on applications internal code structure.
o In this, an internal perspective of the system, as well as programming
skills are used to design test cases.
o In white box testing, the tester analyses the internal architecture of the
system as well as the quality of source code on different parameters like
code optimization, code coverage, code reusability etc.
o This testing usually was done at the unit level.

27. WHAT IS BLACK BOX TESTING?
o It is a process of testing a system component
considering input, output and general function.
o The tester interact with the system through the interface
providing input and validating the received output.
o It doesn’t require the knowledge of internal program
structure.
o In this we test UI & backend (coding/database).
o External actions are performed.

28. WHAT IS POSITIVE AND NEGATIVE TESTING?
Positive:
❖ It is determine what system supposed to do.
❖ It helps to check whether the application is
justifying the requirements or not.
Negative:
❖ It is determine what system not supposed to do.
❖ It helps to find the defects from the s/w.

29. WHAT IS GRAY BOX TESTING?
It is a combination of both black box and white box
testing. The tester who works on this type of testing
needs to have access to design documents, this
helps to create better test cases.

30. WHAT IS TEST STRATEGY?
➢ It is a high-level document and usually developed
by project manager. It’s a document which
captures the approach on how we go about
testing the product and achieve the goals

31. WHAT IS TEST PLAN?
It is a document which contains the plan for all the
testing activities

32. WHAT IS TEST SCENARIO?
It gives the idea of what we have to test. Or testable
part of an application is called TS.

33. WHAT IS TEST CASE?
It is a set of conditions under which tester
determines whether an application/ software is
working correctly or not

34. WHAT IS TEST BED?
An environment configured for testing is called test
bed. It consist of hardware, s/w, network
configuration.

35. WHAT IS TEST SUITE?
Collection of test cases

36. WHAT IS TEST DATA?
It is a document that is basically used to test the s/w
program. It is divided into 2 categories:-
a) +ve test data which is generally gives to system
to generate the expected result.
b) –ve test data which is used to test the unhandled
condition, unexpected , exceptional input condition

37. How will you ensure that your test cases are
complete? Which tool you use to write test cases or use
simple excel file?
We are writing down our test cases in excel sheet.
And with the help of Requirement Traceability
matrix we will ensure that whether all the
Requirements have properly covered or not.
And we will perform Peer Test Case Review and
Formal Test Case Review to find out the missed
test cases which we will add after this review.

38. How many test cases have you developed or
executed?
On an average for the functionality assigned to me
for the given project I have written more than 1000 +
test cases. On an average I am executing around 25
to 30 test cases per day.

39. When do you start writing Test Cases?
We start writing down the test cases when we get a
FSD i.e. Functional Specification Document.

40. How many Test Cases per day you are going write
down in your company?
On an average I am going to write down around 50
to 55 test cases per day.

THANK YOU

Interview Questions
With answers
Part - 5

41.WHAT IS DEFECT LIFE
CYCLE?
Defect Life Cycle or Bug Life Cycle is the
specific set of states that a Bug goes
through from discovery to defect fixation.
Bug Life Cycle phases/status:- The number
of states that a defect goes through varies
from project to project. Below lifecycle
diagram, covers all possible states:

o New: When a new defect is logged and posted for the first time. It is
assigned a status as NEW.
o Assigned: Once the bug is posted by the tester, the lead of the tester
approves the bug and assigns the bug to the developer team.
o Open: The developer starts analyzing and works on the defect fix.
o Fixed: When a developer makes a necessary code change and verifies the
change, he or she can make bug status as "Fixed."
o Pending retest: after fixing the defect the developer gives a particular code
for retesting the code to the tester. Here the testing is pending on the testers
end, the status assigned is "pending request."
o Retest: Tester does the retesting of the code at, to check whether the defect
is fixed by the developer or not and changes the status to "Re-test."

• Verified: The tester re-tests the bug after it got fixed by the developer. If there is no
bug detected in the software, then the bug is fixed and the status assigned is
"verified."
• Reopen: If the bug persists even after the developer has fixed the bug, the tester
changes the status to "reopened". Once again the bug goes through the life cycle.
• Closed: If the bug is no longer exists then tester assigns the status "Closed."
• Duplicate: If the defect is repeated twice or the defect corresponds to the same
concept of the bug, the status is changed to "duplicate."
• Rejected: If the developer feels the defect is not a genuine defect then it changes
the defect to "rejected."
• Deferred: If the present bug is not of a prime priority and if it is expected to get fixed
in the next release, then status "Deferred" is assigned to such bugs
• Not a bug: If it does not affect the functionality of the application then the status
assign to a bug is "Not a bug".

42. How to design test cases? Or tell me different Test Case
Design Technique?
We are designing the Test Cases using black box
type Test Case Design Technique like
➢ State Transition Testing
➢ Boundary Value Analysis
➢ Equivalence Class Partitioning
➢ By using Scenario’s
➢ By using Use Case’s
➢ Pair Wise Testing

43. Tell me about State Transition Testing?
Testing the change in state e.g. from on to
off, open to close etc. of the application is
called as State Transition Testing

44. Tell me about BVA (Boundary Value Analysis)?
BVA is a Test Case Design Technique where test cases are selected at the edges of
the equivalence class.
For example if one InputBox accept a number from 1 to 1000 then in that case our
test cases would be
1) Test cases with test data exactly as the input boundaries of input domain i.e.
values 1 and 1000 in our case.
2) Test data with values just below the extreme edges of input domains i.e. values 0
and 999.
3) Test data with values just above the extreme edges of input domain i.e. values 2
and 1001.
4) Test data with values !@#$#$# and sdf24234 .

45. Tell me about Equivalence Class Partitioning?
Equivalence Class partitioning is a Black Box Test Case Design
Technique where input data is divided into different equivalence data
classes. This method is typically used to reduce the total number test cases
to a finite set of testable test cases, still covering maximum requirements.
For example if one InputBox accept a number from 1 to 1000 then
Equivalence Class Partitioning in this case is
1. Class For Accepting Valid input : number from 1 to 1000
2. Class For Accepting Invalid Input : number <1 or >1000
3. Class For Accepting Invalid input : entering special characters,
alphanumeric value i.e. @#@#@#, blank value etc.

46. Difference between functional specification and
requirement specification. Do we need both in orders to
write the test cases?
Requirement Specification or Business Requirement
Document (SRS or BRD) contains all the requirement from the
business while FSD is a document which contains list of
functionality for the given Requirement. BRD is commonly
used by Business People while FSD is used by engineering
team.
● We are using FSD in order to write down the test cases.

47. IF a>=10 && B<=5 Then some line of code Write down
the test case for this?
Here we can use Test Case Design Technique to write down the test cases
1. Test the given line of code when the value of a=10 and B=5 i.e. at the
boundary
2. Test the given line of code when the value of a>10 and b<5 i.e within the
boundary
3. Test the given line of code when the value of a=9 and b=6 i.e. just
outside the boundary
4. Test the given line of code when the value of a=^&% and b=@$@# i.e.
checking for invalid invalid input

48. WHAT IS EXIT AND ENTRY CRITERIA?
ENTRY→
It describes when to start testing i.e. what we have to test it should be stable enough to test.
Ex:- if we want to test home page, the SRS/BRD/FRD document & the test cases must be ready
and it should be stable enough to test.
EXIT→
It describes when to stop testing i.e. once everything mentioned below is fulfilled then s/w
release is known as exit criteria:-
a. Followed before actually releasing the s/w to client. Checking computer testing is done or not.
b. Documents checking:- test matrix (RTM)/summary reports.
SUSPENSION CRITERIA→ when to stop testing temporarily.

49. WHAT IS BLOCKER?
A blocker is a bug of high priority and high severity. It
prevents or blocks testing of some other major
portion of the application as well.

50. MONKEY/AD-HOC TESTING?
It is an informal testing performed without a planning
or documentation and without having knowledge of
the applications/software functionalities.
Monkey testing is a type of testing that is performed
randomly without any predefined test cases or test
inputs.

THANK YOU

Interview Questions
With answers
Part - 6

51.SEVERITY AND PRIORITY?
Priority→
o “How prior we need to fix the bug is priority.”
o It means the occurrences of defect.
o Decide by developer team. Types(low, medium, high, critical)
SEVERITY→
o “How severe the bug is severity”.
o It means how bad the defect is and what impact it can cause in our
application.
o Decide by the testing team. Types(minor, medium, major)

52. What is defect priority?
A defect priority is the urgency of the fixing the
defect. Normally the defect priority is set on a scale
of P0 to P3 with P0 defect having the most urgency
to fix.

53. What is defect severity?
Defect severity is the severity of the defect
impacting the functionality. Based on the
organisation, we can have different levels of
defect severity ranging from minor to critical
or show stopper.

54. Give an example of Low priority-Low severity, Low
priority-High severity, High priority-Low severity, High
priority-High severity defects.
1. Low priority-Low severity - A spelling mistake in a page
not frequently navigated by users.
2. Low priority-High severity - Application crashing in some
very corner case.
3. High priority-Low severity - Slight change in logo color or
spelling mistake in company name.
4. High priority-High severity - Issue with login functionality.

55. When you install any software how you make sure that
software installed correctly? Tell any 5 test cases.
● First while installation I will check the message at the end which
will tell me whether application is successfully installed or not.
● Then I will go to Installation folder and try to run the Application
exe.
● Then I will check the icon on desktop or program list.
● Then I will check the detail of installed application in add/remove
program.
● Then In the registry I will able to see the entries of this software.

56. Tell me the test cases of door and how to
perform integration testing of door?
Functionality:
● Verify that height & width of the door as per the given
specification.
● Verify the material used for the door as per the given
specification.
● Verify the effect of environmental condition on the door.
● Verify whether lock attached to door is functioning properly or
not.
● Verify that fittings of the door is fitted at the desired location

Integration:
● Verify whether user is able to assemble or
dismantle the door from the wall.
dismantle the lock of the door.
dismantle the Grip of the door.

Performance:
● Verify whether door is able to sustain the given
specified maximum pressure.
● Verify whether door is able to sustain the given
specified maximum pressure for a longer period of time.
● Verify the behavior of door after applying a pressure
beyond its specified maximum limit.
Usability:
● Verify the look and feel of the door.
● Verify the furniture polish of the door.
● Verify the design of the door.

57. What are your considerations while writing down test
cases?
➔ First I will completely understand the functionality.
➔ Then I will start writing down the test cases
➔ While writing down the test cases I will use Black
Box Test Case Design Techniques i.e. BVA,
Equivalence Partitioning, State Transition Testing
along with understanding the Scenarios and use
case.

58. Have you written any test cases without any document
like FSD or design document? Do you require updating the
initial test case in project life cycle any time?
➢ No, I haven’t written any test cases without any
documents. But if you know the functionality well then we
can write down the test cases.
➢ Yes, most of the time we are getting the CR’s (Change
Request) for the given functionality from the business, in
that case we are pulling our previous test cases related to
that functionality and update it appropriately.

59. If there are 50 modules in the test plan what will you
do? Will you write 50 test plans?
Depends. We have a master test plan for entire big
project. And for each module we have Module Test
Plan. If the entire module we are testing in a similar
way then we can write a single module test plan
which represents all the 50 Module Test Plan.

60. What is test cases and test plan? Difference between
test case and test plan?
Test Case is a sequence of keywords or steps used
to test the specific feature of an application. While,
Test Plan is nothing but Road Map for testing & Test
Plan is used for the Planning of Testing Activity

THANK YOU

Interview Questions
With answers
Part - 7

61.WHAT IS UNIT TESTING?
It is also called as module testing /component testing.
It is done to check whether the individual unit or module of the source
code is working properly. It is done by the developer.

62. INTEGRATION TESTING?
❖ It is a process of testing the interface between the
two s/w units.
It is done by 3 ways:- big-bang , top-down, bottom-up
approach.
Process of combining & testing multiple components
together.
Normally done by developer but a tester can also
perform if he has the knowledge of coding.

63. SYSTEM TESTING?
It is a black box testing technique performed to
evaluate the computer system. It include both
functional and non-functional testing. Verifying the
completed system to ensure that the application
works as intended or not.
“The behaviour of the system is tested as defined by
the scope of the development project”.
Carried out by specialist tester/independent tester.

64. USER-ACCEPATANCE TESTING?
User-requirement testing is done.
Done by client as well as end user.
It is a final stage of testing before used.

65. ALPHA-BETA TESTING?
Alpha→
● o Developer records all the issues.
● o Done by the end user at dev site. (involves client or
tester+dev)
Beta→
● o Dev go through all the issues after specific period of
time.
● o Done by the end user at the client site. (involves
client/user)

66. Suppose you are the PM and you have to design test
plan, how you will design test Plan?
Basically test plan is nothing but road map for testing & Test Plan is used for the planning for
Testing Activity. I will consider below points while designing a Test Plan
● Objective
● Introduction
● Assumption and Test Approach
● Entry Criteria
● Exit Criteria
● Resumption Criteria
● Suspension Criteria
● Risk and Mitigation
● Resource and Responsibilities
● Test Environment Set up
● Training Requirements
● Test Schedules
● Deliverables

67. Who is preparing Test Plan?
Test Lead is responsible for preparing the Test Plan.
But In my company I am helping my lead to generate
a Test Plan.

68. What is Entry Criteria? Or what are Entry Criteria for
Testing Phase? Or what should be the Entry criteria for
system testing?
Entry Criteria will tell you, when to start testing?
We can start testing only when
1. All the Resources are in Place.
2. All the Hardware and Software in Place.
3. All the Test Cases are in place.
4. Drop/Build is ready for testing.

69. What is Exit Criteria? Or when to stop testing? Give at
least 5 reasons?
Exit Criteria will tell you, When to Stop Testing?
We can Stop Testing only when
1. No S1 or P1 Defects are in open state.
2. Open P2 Defects must have mitigation plan and work-around
3. All CRs(Change Request) = Closed or Deferred
4. System, Integration and Regression Testing = Complete
5. STG Environment must be Stable.

70. Can project will be delivered with few open defects in
it? What do you think about it?
Yes. Provided no S1 or P1 defects should be in open
state. As we already mentioned this in the exit
criteria in our test plan.

THANK YOU

Interview Questions
With answers
Part - 8

71.WHAT IS SMOKE AND SANITY TESTING?
SMOKE→
o It is a kind of Software Testing performed after software build to ascertain that the
critical functionalities of the program are working fine.
o The purpose is to reject a badly broken application so that the QA team does not
waste time installing and testing the software application.
o In Smoke Testing, the test cases chose to cover the most important functionality or
component of the system. The objective is not to perform exhaustive testing, but to
verify that the critical functionalities of the system are working fine.
SANITY→
o Sanity testing is a kind of Software Testing performed after receiving a software build,
with minor changes in code, or functionality, to ascertain that the bugs have been fixed
and no further issues are introduced due to these changes.

72. Smoke Testing Vs Sanity Testing - Key Differences

73. Tell me a Bug having High Priority and Low Severity and
a Bug having Low Priority and High Severity and a Bug with
High Priority and High Severity? Or
Give the example of high severity and low priority defect in
any your project? Not general answer required.
❖ High Priority High Severity:
In our application while creating an Account with special characters in the name it
was crashing the application. So this was a bug having High Priority and High
Severity.
Justification: Priority of the Bug was high because it was application crash and
user was losing the data which he entered while creating the account.
Severity of the Bug was high because it was application crash.

❖ High Priority Low Severity
In our application we have Account Profile Report which was giving us Revenue related
information for the given Subsidiary, Date and Products filter. But when I was selecting All
subsidiaries then it was not showing data for India Subsidiary. So this was a bug having High
Priority and Low Severity.
Justification: Priority of the bug was high because it was a data loss for India Subsidiary and
90% of the users were from US subsidiary.
Severity of the bug was low because we were able to test the report for the rest of the
subsidiary.
❖ Low Priority High Severity
In our application while creating more than 100 Contacts for the given account it was crashing
the application. So this was a bug having Low Priority and High Severity.
Justification: Priority of the bug was Low as the chances of creating contacts more than 100 for
the given account by business was very less.
Severity of the bug was high as it was application crash.

❖ Low Priority Low Severity
There was spelling mistake in our help file of the application. So this was a bug
having low priority and low severity.
Justification: Priority of the bug was low as the chances of accessing that help file
was less.
Severity of the bug was low as it was not affecting any functionality.
❖ Medium Priority Medium Severity
In our application we have Account Profile Report which was giving us Revenue
related information for the given Subsidiary, Date and Products filter. But for the
selected date it was showing wrong revenue. So it was a bug having Medium
Priority and Medium Severity.
Justification: Priority and severity of the bug was Medium because it was affecting
the main functionality.

74. What is Bug Report?
Bug Report will give you the information about
How many bugs we logged? How many of them are
in Proposed State? How many of them are in Active
State? How many of them are closed? How many of
them are Re-opened? How many of them are
rejected? Bugs by Severity? Bugs by priority?

75. What is the Format of Bug Report?
Bug Report is a report which we send daily to our
managers.

76. What is an issue/Defect/Bug? Or what is mean by
Defect or Bug?
● Error: If the Expected Output is not matching with the Actual
Output then it’s an Error.
● Bug: If the error is found during testing phase then we called it
as a Bug.
● Defect: If the error is found by customer after release of the
application then we called it as a defect.
● Issue: If we are expected something from the application and if
we are not getting that then we called it as an issue.
E.g. when user runs a report he is expecting to see some data, but
he is not able to get any data. He then called it as an Issue as the
user is not sure that whether this is a defect or not?

77. If today we have the release and the end of testing we
found one bug which crashes the application then should
we Release it or not?
If the application is crashing then it’s a S1P1 issue
and we cannot give the test signoff unless that S1P1
bug resolved. So here we need to postpone the
release.

78. What is scrum?
A scrum is a process for implementing Agile
methodology. In scrum, time is divided into sprints
and on completion of sprints, a deliverable is
shipped.

79. Who Assign the Severity to the defect and who assigns
the Priority to that Defect?
Normally Tester Assign the Severity to the defect and
Project Owner assigns the Priority to that defect. But
In our company we only assign the Priority.

80. You have logged a defect but it is not reproducible to
the developer, please specify the reason.
The Reason may be…
➔ the reproducible steps are not clear
➔ the role of the developer on that application may be different than the tester e.g. developer
may have guest user role and tester may test it with system administrator role
➔ some of the services may be down while testing which causes the error on test
environment
➔ Environmental issue e.g. the environment on which user is testing may be differing than
where developer is trying to reproduce the defects.
➔ Some other software in the test environment may create a problem to our testing
application which may not be the case with developer machine
➔ Some of the sql jobs may failed in the test environment which causes a problem to test
environment but that may not be the case with the dev environment.

THANK YOU

Interview Questions
With answers
Part - 9

81.If developer rejects the bug then what should you do? Give
the 5 reason of defect rejection?
If you found bug and developer said that this bug is not
reproducible at his place then what you will do?
If Developer rejects a bug and if it’s really a bug I will attached the references of FSD and error snapshot which will give him correct
understanding of that bug.
If he still doesn’t agree on that I will arrange a live meeting with him and reproduced this issue in front of him.
If still he don’t agree on that and saying this is the problem with your environment then I will escalate it to my Manager.
Developer can rejects Issues ……
1. If it is an Environmental issue.
2. If the functionality is out of scope.
3. If the logged defect is as per design spec.
4. If the logged defect is unable to reproduce
5. If the logged defect is not able to fix due to technical limitation
6. If the logged defect is postponed till next release

82. What are the different types of Bugs we normally see in
any of the Project?
➔ Bugs related to functionality
➔ Bugs related to missing requirement
➔ Bugs in the FSD/BRD
➔ Usability related bugs
➔ Bugs related to performance e.g. Application is very slow
➔ Bugs occurred at the boundary value
➔ Bugs in the developed code etc.

83. What are the contents in defect reporting? or What are
different field in your bug defect life cycle?
Contents in defect tracking tools are
● Title of the Bug
● Severity
● Priority
● Found & Fixed in Build
● Description of the Bug
● Attachment
● State
● Reason
● Created By
● Creation Date etc.
● Application Name

84. If you found bug then how you will conclude that
this is bug?
When I found a bug first I will try to reproduce it on
my machine 2 or 3 times. Then I will cross verify the
same issue on different machines having same drop.
At the same time I will confirm it by cross verifying
the Functional Specification Document.

85. If you found any bug then what is your next step?
Once I found a bug then I will first ensure that
whether it’s a really bug or not? And at the same
time I will ensure that has any one already logged it
or not? Then I will log that issue in Bug tracking
tool/Defect tracking tool(DTT).

86. How you decide severity and priority?
❖ S1 is assigned if the bug will cause a system crash or data loss.
❖ S2 is assigned if the bug will cause major functionality or other
severe problems.
❖ S3 is assigned if the bug will cause minor functionality problems.
❖ S4 is assigned if the bug is the cause of unclear wording or error
messages in low visibility fields.
➢ Priority 1 – Crash, Data Loss, Unrecoverable Error, or Ship
Stopping issue.
➢ Priority 2 – Critical issue. May or may not be critical for release,
but is a severe problem.
➢ Priority 3 – Minor issue, affects less than 5% of users,
edge/corner case. A workaround may exist.

87. Tell me the latest bug which you found recently? Or
Client appreciations for any bugs? Interesting bugs you
logged
In our application on Home Page we are showing the
number of vendors deleted. But when I verified at the
back end it was actually not deleted but was marked
for deletion. So I logged this issue having S3 and
Priority P2.

88. Can duplicate bug reassign?
Ideally we should not reassign the duplicate bug.
But if you reassign it nothing will happen, only dev
will see 2 similar bugs in his bucket and reject one
of them.

89. If there is no company Logo on web page what will be
the Severity and Priority for this?
Severity of this bug is S3 and Priority of the Bug is
P1. As it is not affecting the functionality the severity
of the bug is S3 but Company Logo is a like a Brand
symbol for that company so the Priority of the bug is
P1.

90. What is Risk Analysis?
Risk Analysis is a process of Identification of risk
under different conditions, finding out cause-&-effect
relationship between probable happenings. How we
can reduce that risk along with privative measures.

Part 10(imp) will be coming soon.
Video Link: https://youtu.be/z3W6L38wL94
THANK YOU

Interview Questions
With answers
Part - 10

91. What is GUI Testing?
GUI Testing is nothing but testing the product or application
that uses Graphical User Interface, to ensure that it meets the
customer requirement.

92. What is Security Testing?
Security Testing is nothing but to test how well the system
protects against unauthorized internal and external access,
willful damage etc. In security testing we are finding out the
vulnerabilities of the application.

93. What is Stress Testing?
Stress Testing is nothing but to test the software
beyond its limit. Stress Testing are of two types:
● By Keeping the H/W resources constant and
increasing the load of the user.
● By keeping the load of the user constant and
gradually decreasing the H/W resources.
E.g. to test the software using Low Ram, Low
Hard Disk, Low CPU etc.

94. What is Load Testing?
Load Testing is nothing but to test the software at its
limit. Load testing is mainly performed to find out
how much maximum user application can handle
without losing the performance.

95. What is Soak Testing or Endurance Testing?
To Test the Software at its limit for a longer period of
time e.g. for more than 2 days. The main purpose of
Endurance Testing to check the behavior of
application if it is under heavy load for a longer
period of time.

96.What is the difference between Load and Stress
Testing?
In Load testing we are testing the software at its
maximum limit. The basic purpose of Load testing to
find out how many maximum user applications can
handle without losing the performance.
But in Stress Testing we are testing the software
beyond its limit to check the behavior of application
when it crosses the maximum limit of user.

97. Tell me the difference between functional and
system testing?
In Functional Testing we are testing the functionality
of the application while in system testing we are
testing the functional as well as non functional
aspects i.e. Security, Performance, Installation, Up
gradation, etc of the application along with
functionality

98. What is mean by Ad-hoc testing and exploratory
testing? Or what is the difference between Ad-hoc testing
and Smoke testing?
❖ Exploratory testing is nothing but testing the application
without having requirements. So here in Exploratory testing first
we explore the application and then test.
❖ Ad-hoc means we know our final target but don’t know how to
reach to that target. So Ad-hoc testing is nothing but to test the
application with the intention of finding the bugs. This type of
testing is carried out without any test cases or test plan.
❖ Smoke Testing is nothing but testing the main-main
functionality of the application to ensure that nothing has been
affected and we can go for further exhaustive testing.

99. What is Requirement Understanding Document
(RUD)?
When analyst gathers the requirement from the
customer, he prepares a document where he puts all
the requirements told by the customer, we called this
document as Requirement Understanding document.
By going through this document customer gets the
confidence whether analyst properly understood his
requirement or not?

100. Explain the testing cycle you will follow if you have
100 test cases in the first cycle... 25 failed and 75 passed.
How many test cases you will pick for the second cycle?
I will pick all the 100 Test Cases in second cycle, to
ensure that there should not be any side effect of
fixing the bugs on other functionality.

Share with all your Friends.👫
“Whatever you want to achieve in life, Help others to achieve that!!! “
Video Link: Part 10
Testing Jobs: https://t.me/TestingJobsAndInterview
All PDF file: https://t.me/Mohanty_Academy
THANK YOU
Jaikishan Mohanty

Interview Questions
With answers
Part - 11

101. How will you test the application without having any
requirements?
We will perform exploratory testing. Means we will first explore
that application and then test. We can explore that application
by taking the help of superiors who is having knowledge about
that application, or by going to help files of that application or
by understanding the domain for which this product belongs
etc.

102. Did you get any bug which was not in the requirement
or in ad-hoc testing (which was not in the test case)? Or did
you get any bug in Ad-hoc testing? Explain
Yes. In our application on the home page first we were
showing all the accounts but later on it was creating a
performance issue when number of accounts was more than
100. Then I logged a bug saying that paging functionality
and search functionality should be provided to navigate to
and to find out the specific account. Earlier it was not
mentioned in the Requirement documents

103. Explain memory leak with example?
Memory leak is nothing but unintentional
consumptions of memory. Most of the
Application when we closed gets invisible from
the desktop running in the backend.
Or
Unintentional memory consumption by a
computer program where the program fails to
release Memory when no longer needed.

104. You have only 4 line of requirements how you
will test it?
I will try to split that requirement into functionality
first. Then I will try to create user scenarios and write
down test cases on that and will test it.

105. What is Web Testing? What is the Thing we need to
consider for Testing Web Based Applications?
Web Testing is nothing but testing the Web Based Application.
We need to consider:
● Functionality
● Usability
● Performance
● Security
● Server Side Interface
● Client Side Compatibility while performing web based
application.

106.What is difference between Integration and
Incremental Integration testing?
Integration Testing is nothing but testing the interface
between different components or modules.
After performing integration testing of all the modules
if any new functionality is added into that application
then we can integrate it with our application and
perform the integration testing called as incremental
integration testing.

107. Difference between System Testing and System
Integration Testing?
In system testing we are testing the functional as
well as non functional aspects i.e. Security,
Performance, Installation, Up gradation, etc of the
application. While in System Integration Testing we
perform the integration of existing system with
another system. E.g. Integration of two or more
systems with each other.

108. Tell me who is responsible for Unit Testing either
developer or tester?
For any testing related activity Tester is responsible.
So ideally speaking Tester is responsible for unit
testing. But practically speaking most of the testers
are not aware of development languages so
developer is performing unit testing.

109. What is Traceability matrix? What are Forward
Traceability and Reverse Traceability?
Traceability Matrix is used to mapped your:
● Requirement with Test Cases or
● Functionality with Test Cases or
● Requirement with Defects or
● Functionality with Defects or
Forward Traceability matrix helps you to provide information about how
many test cases you have written for a given requirement/functionality. Or
how many bugs we have logged for a given requirement/functionality.
Reverse Traceability matrix helps you to provide information about; this
given test case belongs to which requirement/functionality. Or this logged
bug belongs to which requirement/functionality

110. What is traceability Matrix? And when and who
is preparing it?
Traceability Matrix is used to mapped your:
● Requirement with Test Cases or
● Functionality with Test Cases or
● Requirement with Defects or
● Functionality with Defects or
When we start writing down test cases for a given functionality
or requirement, test lead prepares this requirement traceability
matrix.

Video Link: Part 11
THANK YOU
Jaikishan Mohanty

Interview Questions
With answers
Part - 12

111. What are the challenges that you faced in your project?
Or What are the difficulties You faced in your project.
A. The biggest challenge we faced in our current project is to satisfy the customer, as his
expectation is too high from all of us. E.g. Customer is expecting to execute more than 50
test cases per day per person. Which is quite difficult as our functionality is very complex.
B. The other challenges we faced is that requirements are changing every often and then
without any prior notice or discussion.
C. We are lagging behind the schedule, so every one of us has to stretch hard. So here
effort estimation is not correct.
D. We don’t have any defined process. This creates a lot of problem. E.g. Deployment
doc is not clear and we are not in sync with the dev people. So in case of any issue while
deploying the drops we have to struggle a lot.
E. As a new Team Member for this project, I am facing problem to understand the process,
getting domain knowledge, understanding the functionality which is dependent on other
functionality. As we don’t have proper Training plan in place.

112. I have to test an application with 1000 users without any
automation tool and time limit is also less. Is this possible?
How?
It totally depends on the functionality we are going to test.
For example if I want to create a Account with 1000 different
user, then through UI it is very difficult but I can test this
either through back end by running a sql query or at the API
level where we are directly passing the required parameter
to that function. Here we can take help of scripting language
or excel sheet to generate 1000 different users.

113. Tell me how you will perform stress testing of bike?
Stress Testing is nothing but testing the application beyond its limit.
So in order to test the bike for Stress Testing:
➔ Try to run it at the speed of 10 KM/HR in 4th gear.
➔ Try to run it at its highest speed when bike is in 1st gear
➔ Try to run it on a very steep road.
➔ Try to run it on a very rocky road where in we can test the shock ups
and tyres of the bike.
➔ Try to run a bike at highest speed when tyre pressure is very low
➔ Try to run when there is no engine oil present etc.
➔ Try to run a bike on 1st gear from a very sloppy area here we can
check the performance of the gear

114. What are the considerations while writing down
the test cases?
Before writing down the test cases one should fully
understood the functionality, he should be aware that
what are we going to test e.g. are we going to test
security, functionality, or usability etc. He should be
aware of the different test scenario, he should be
aware of different test case writing techniques, he
should refer the FSD.

115. What is mean by cookies? How to work cookies?
Which protocol used for cookies?
Cookie is small information stored in text file on
user’s hard drive by web server. This information is
later used by web browser to retrieve information
from that machine. Generally cookie contains
personalized user data or information that is used to
communicate between different web pages.
➢ HTTP Protocol is used for cookies.

116. How do you decide what to test in the Project?
First we have a client meeting where we try to
understand what he wants from us. If possible we
suggest from our end if he misses something. And
then we documented all this things and in test
strategy we decide what kind of testing we need to
perform by considering customer requirement.

117. What is difference between in inspection,
walkthrough, Peer Review and Formal Review?
Peer Review: In peer review the code written by one developer or the test cases
written by one tester will be reviewed by another developer/tester. It is also called as
buddy review. The main purpose of this review is to find out where all the coding
standards/Test Cases writing standards follows or not. To find out early defect peer
review is important.
Walkthrough: Is a informal type of review where the code written by the developer
or Test Cases written by the tester is getting reviewed by a group of 5 to 6 peoples.
The owner of the code or Test Cases will present his code/Test Cases and explain
them line by line. The Main purpose of walkthrough is to find out the design related
issue and any missing things.
Inspection/Formal Review: Is a most formal type of review. A group of 3 to 8
including a moderator, reader, and a recorder to take notes. The main purpose is to
find problems and see what's missing, not to fix anything. Participant should be
prepares for such type of meetings by reading the document sent by the presenter

118. What should be the Goal of Software Tester?
The Goal of a Software Tester should be to find the
bug, find them as early as possible and make sure
they get fixed. At the same time ensuring that
software application meets the entire requirement
given in the BRD.

119. Tell me the difference between incremental Testing vs
Big Bang Testing?
Normally software is developed in multiple pieces called as Module.
In Incremental Testing we are testing the software pieces by pieces
once all the individual modules are working fine a few of them tested
together. Testing combination of pieces of product is called
integration testing. And in Big Bang Testing we are testing the
application as a whole in one shot
If two modules are working fine independently and after integrating if
some error occurs then certainly the problem is in the interface
between them. Another benefit of incremental testing is that
programmer focuses on each module individually, which probably
yields better test coverage

120. What is SRS,FS,BRS?
SRS: Software Requirement Specification
FS: Functional Specific
BRS: Business Requirement Specification

Video Link: Part 12
THANK YOU
Jaikishan Mohanty

Interview Questions
With answers
Part - 13

121. What is BVT/BAT?
Build Verification test is a set of tests run on every new build
to verify that build is testable before it is released to test team
for further exhaustive testing. These test cases are core
functionality test cases that ensure application is stable and
can be tested thoroughly. Typically BVT process is automated.
If BVT fails that build is again get assigned to developer for fix.
BVT is also called smoke testing or build acceptance
testing (BAT) New Build is checked mainly for two things:
● Build validation
● Build acceptance

122. How will you perform field validations?
I will use Equivalence Class Partitioning and Boundary value
analysis in order to perform field validations.

123. What kind of challenges you faced when monitoring
the team members?
➔ Attitude problems
➔ Conflicts within the team members
➔ Career aspirations are different than what
kind of work they are doing now
➔ No out of the box thinking
➔ Frequent Follow up

124. What is function decomposition?
Functional Decomposition is a process of splitting a
function into different parts in such a way that
original function can be reconstructed from these
parts.
The main advantage of functional decomposition is
that we can get better insight into specific parts of
that function. Those parts we can test thoroughly
and easily

125. What is your future goal?
Short Term Goal:
❖ For exp: 1 to 4 yrs: To become a Lead down the
line 2 years.
❖ For exp: 4+: To become a Manager down the line
2 years.
Long Term Goal: To become an entrepreneur down
the line 10 yrs.

126.What is one to one, one to many and many to many
Relationships in DB? Give example?
One to One Relationship: In 1 to 1 relationship, one primary record is
associated with 1 related record. For example: 1 Person has only 1 Pan
Number. Or 1 student is associated with only 1 division.
One to Many Relationships: In 1 to many relationships, one primary
record is associated with multiple related records. For example: 1 Person
has many Bank Accounts or 1 student is associated with multiple subjects.
Or 1 Purchase order is associated with many line items.
Many to Many Relationships: In Many to Many Relationships, multiple
records are associated with multiple related records. For Example: Multiple
Sales People are associated with multiple Accounts.

127. When should we go for Load Testing and when
should we go for Volume Testing?
If we want to test the application with certain amount of data then we
should go for volume testing.
For example: How much maximum number of records SQL Server is
able to process when number of user is hitting the sql query?
If you want to understand the behavior of the application under a
specific expected load without losing the performance, then we
should go for load testing.
For Example: How many users are able to perform certain set of
operation without affecting the response of time of the application?

128. You are working on a critical release, and we are
going to release that product tomorrow and but you have
your own personal problem in that case how will you
handle such type of scenario?
Though I am critical release for that project, I have to
have completed my task in any circumstances. What I
will do, I will try to finish my personnel problem during
first half and will come office a little late and stay till I
finish my work else I will assign that ask to my family
member and will come to the office and try to finish my
task ASAP , as job is on top priority for me.

129. Can we do Load testing manually?
No

130. What is product vs project?
Product: Developing an application based on global
market needs and requirements and no specific client.
Project: Developing a product based on the Client needs
or requirements. Project is something that converts an
idea or design or a plan in to some concrete entity.
E.g. Construction of a new highway is a project;
construction of a software is a project.

Video Link: Part 13
THANK YOU
Jaikishan Mohanty

Interview Questions
With answers
Part - 14

131. What will be your action if there are 4 people in your team
and are not good with each together still you want the people to
work together to get your work done? Or How will you handle
team conflicts?
● First I will try to understand their problem
If the problem is personal then in the office they should not bring it.
● If the problem is related to career aspiration then I will give them
assurance that I will work on that
● If the problem between them is related to attitude then I will delegate the
work appropriately so that there should not be any conflicts.
● I will schedule a regular 1 on 1 with them to monitor the changes
If needed I will arrange a skip level manager meetings.

133. Pros and Cons of Waterfall Model?
Pros :
➔ It is the simplest software process model in terms of
complexity and ease of implementation.
➔ This model is extremely easy to understand and therefore, is
implemented at various project management levels and in a
number of fields (not just software development).
➔ It employs a systematic, orthodox method of project
development and delivery.
➔ It allows you to set expectations for deliverables after each
phase

133. Pros and Cons of Waterfall Model?
Cons
➔ Being a strictly sequential model, jumping back and forth between two or
more phases is not possible. The next phase can be reached only after
the previous one has been completed.
➔ Due to this, bugs and errors in the code cannot be discovered until and
unless the testing phase is reached. This can lead to a lot of wastage of
time and other precious resources.
➔ This process model is not suitable for projects wherein the project
requirements are dynamic or constantly changing.

134. What is Database Testing?
Data base testing is also called as back end testing.
We conduct this testing based on data validation and
data integrity. Data validation means that whether
front end values are correctly storing into back tables
content or not. Data integrity means that whether
impact of front end operations is working on back
end tables content or not.

135. Tell me the Different types of joins?
There are 4 types of joins :
1. INNER JOIN
2. LEFT JOIN
3. RIGHT JOIN
4. FULL JOIN
For More: https://www.javatpoint.com/dbms-sql-joins
https://www.geeksforgeeks.org/sql-join-set-1-inner-left
-right-and-full-joins/

136. What is configuration testing?
Configuration testing is nothing but to test whether
our software/hardware is configurable with other
software/hardware.
e.g. To check whether Processor (intel,asus etc.) is
easily configurable with different Hard Disks (like
Seagate ) or to check whether OS is configurable
with different combinations of processors, Hard
Drives, CD ROM etc

137. What are the pre project activities you follow?
● Understanding the requirement
● Defining the scope & Schedule of work
● Identifying the cost required to execute the
project.
● Resource availability etc.

138. What are the post project activities you follow?
● What went wrong & what went well
● New learning from this project
● Root Cause analysis of the problem we faced
● Customer feedback etc.

139. What are some advantages of automation testing?
Some advantages of automation testing are
★ Test execution using automation is fast and saves considerable
amount of time.
★ Carefully written test scripts remove the chance of human error
during testing.
★ Tests execution can be scheduled for nightly run using CI tools
like Jenkins which can also be configured to provide daily test
results to relevant stakeholders.
★ Automation testing is very less resource intensive.
★ Once the tests are automated, test execution requires almost no
time of QAs.
★ Saving Qa bandwidth for other exploratory tasks.

140. What are some disadvantages of automation testing?
Some advantages of automation testing are
➢ It requires skilled automation testing experts to write
test scripts.
➢ Additional effort to write scripts is required upfront.
➢ Automation scripts are limited to verification of the
tests that are coded.
➢ These tests may miss some error that is very glaring
and easily identifiable to human(manual QA).
➢ Even with some minor change in application, script
updation and maintenance is required

End of Manual Testing Series👫
Don’t Forget to Like and Subscribe & comment your feedback.
Video Link: Part 14
THANK YOU
Jaikishan Mohanty

Manual Testing real time questions .pdf

More Related Content

What's hot (20)

Similar to Manual Testing real time questions .pdf (20)

Recently uploaded (20)

Manual Testing real time questions .pdf