What is Bug Validation? What can be a different resultant
after the same?
- 3 Answers
- 19603 Views
- Satyam, I also Faced
- E-Mail Answers
Answer Posted / 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 |
Post New Answer View All Answers
Encapsulation of attributes and operations inside objects makes it easy to obtain object state information during testing. is it true.explain
Hello Varun, Kindly send me the material as well as sample question papers as i am interested in doing the certification. Kindly help me out in this regard. Here is my mail ID: bjyothitesting@gmail.com
date format and we should 8 digits - not accepted only /accepted write how many in test cases in the date format valid , and in valid
If anybody from banglore having the real time exp in manual testing with 3+ yrs exp and looking for change send your profile to vinodhanandhan@gmail.com
What are differences in testing a client server and a web application?
How do u go about testing of web application?
in transfer funds module, how you come to know that amount has been transferred successfully or not....explain in detail
can any one post the format of tracebility martrix Plz...... Maid Id: sandhya.shyamala@yahoo.com
what is base time , how can we base time your doc"s ?
write test case for linked in sign up page ?
what is the common in all s.o.p (standaed operating procedure)?
hi, I m looking for a career in manual web testing. so PLZ anybody who have the practical knowledge of dis field help me. GIVE ME UR MAIL ID so that i can ask regarding some doubts. my MAIL ID is ankurtester819@gmail.com
Build with fixes has been deployed on QA environment if asked by your manager to reproduce how can you reproduce the issues? (by using the previous build) Can you access the previous build? If so ,what are the tools or how can you access?
In testing environment have you ever found any areas for improvement while you at work. (Please give some real life example).
What is smoke testing and user interface testing ?
