Manual Testing Part 9

Uploaded by

chahsam.cs

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

5 views

Manual Testing Part 9

Uploaded by

chahsam.cs

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 12

Manual Testing Real Time

Interview Questions
With answers

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