Scribd
Upload
8 views14 pages

Manual Testing - Part 8

Uploaded by

chahsam.cs
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
8 views14 pages

Manual Testing - Part 8

Uploaded by

chahsam.cs
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 14

Manual Testing Real Time

Interview Questions
With answers

Part - 8
By : Jaikishan Mohanty
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.
Share with all your Friends.👫
“Whatever you want to achieve in life, Help others to achieve that!!! “

Video Link: Part 8

Testing Jobs: https://t.me/TestingJobsAndInterview

All PDF file: https://t.me/Mohanty_Academy

THANK YOU
Jaikishan Mohanty

You might also like