What is Bug Validation? What can be a different resultant
after the same?

Answers were Sorted based on User's Feedback



What is Bug Validation? What can be a different resultant after the same?..

Answer / harry

Ravi, you have the understanding of concepts to some extent
but it looks like you have tried to explain everybody the
bug process which you are probably following somewhere (in
a week process based company). Moreover you also didn't
understand the question.
What is Bug Validation? (its not a process)
Bug validation: Bug and Validation are two different terms.
Bug means an anomaly and validation means checking with the
appropriate data whether the functionality is working as
per the requirement. If a bug is reported on a
functionality on earlier build(this could be alpha or beta)
then on next consecutive build (alpha or beta) it should be
validated in order to Determine if the system complies with
the requirements and performs functions for which it is
intended and meets the user needs.

What can be a different resultant
after the same?
Different resultants of bug validation could be:
1. The bug could be validated using various inputs
If the bug is passed:
2. Then before closing the bug user/tester can also provide
information like screenshot of whether the output was
expected or not.
3. Then before closing the bug user can also provide
information whether the fix has fulfilled the requirement.
If the bug fails:
4. Then on re-opening the bug what was the outcome could be
provided as screen shot
5. Then on reopening the bug what other
features/functionalities are affected can also be informed.

Note bug validation is not only done by testing team it
could also be done by development team. For e.g, if
development team reported bugs on alpha build they were
testing then they might validate on next alpha consecutive
build or fix it for beta build so that testing team can
validate it. Thats why I have used the alpha(development
team) and beta(for testing team) terms for the build.

Ravi, what you have been trying to explain is bug
process/bug life cycle. What you were trying to provide is
as follows:
1. Tester finds a bug and logs it with appropriate Priority
and severity (tester doesnt have to ask to anybody for P/S)
2. Change control board verifies whether the bug (its
earlier existence in Bug logging software, whether its
valid) and then assigns it to the appropriate functinality
stake holder in development.
3. Developer fixes it and provides the information in the
bug as well as during the release build notes of the next
consecutive build carrying the fix for the bug.
4. Tester validates the bug in next build and updates the
status of bug.
5. If the bug passes then its closed else if its failed
then the above process is followed as it is.

Is This Answer Correct ?    4 Yes 0 No

What is Bug Validation? What can be a different resultant after the same?..

Answer / kashyap srinivas

Once a bug is found by the tester it is sent to the test lead for validation. The possible outcome of this validation process can be defect open or not a defect.

After the bug is marked open by the test lead, its once again validated by development lead. and the possible outcome of this process can be (assign to fix,not a defect, differed(can be fixed in later releases)).

For more information go through Defect/Bug life cycle.

Is This Answer Correct ?    0 Yes 1 No

What is Bug Validation? What can be a different resultant after the same?..

Answer / ravi

hi

bug validation of is the process after finding the bug in
application which is duty of tester and it should be done
first and foremost as the tester find the bug.

its important in the sense when tester finds the bug , and
by doing bug validation he himself makes sure that whatever
he found is valid one and can be reported to senior

steps to perform bug validation:

when he/she finds the bug at first they have to do:
.note the severity of bug
.check with change request team( to make sure generation of
bug is due to changes made in application)
. refer old release to make sure the bug found is valid and
not repeated.
.check with test case/ test plan/any requirement documents.

to avoid confusion after finding bug, according to me One
should do 'bug Validation ' before reporting it to higher level

cheers

ravibyndur@yahoo.com

Is This Answer Correct ?    0 Yes 4 No

Post New Answer

More Manual Testing Interview Questions

what is mean by test suite?

5 Answers  


write a test cases for facebook

2 Answers  


Which are the standards for software test plans?

0 Answers  


How to write test case for view the table(i.e it is already stored in database and see the content in the table)

0 Answers   TCS,


How to test when the web application expired time (cookies,sessions testing) in real time

1 Answers   ABC, Tech Mahindra,






What is the Input of Testcase?

13 Answers   GE,


What is the test harness?

0 Answers  


Hi Friends, What are the steps involved in STLC

16 Answers   Polaris,


Can you explain process areas in cmmi?

0 Answers  


what is production defects?

1 Answers   SSP, TCS,


difference between change management and configuration management

0 Answers  


eqivalance testing class is made from data and this is made to minimize the test cases and it is black box testing what at which particular time we do this testing i guess while creating test cases we consider this testing .plz if lett me know if i am wrong

1 Answers  


Categories