Interested to Buy Any Domain ? << Click Here >> for more details...
What is Bug Validation? What can be a different resultant
after the same?
- 3 Answers
- 21707 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
Can you explain regression testing and confirmation testing?
how to creat 2 test plan in 2 different environment exp:tour and travel
Can you explain boundary value analysis?
How to do Pixel Size testing in a PDF document. Is there any Open tool that will be avaiable?
what is entry and exit criteria and explain it?
What is the difference between Sleep and wait in winrunner what is integration testing and types of testing present what is system testing what is data driven testing what is functionality testing if requirements are given to you then how do you write the test cases for it Account number = Ok cancel For above given form the valid account number starts from 1 to 1000 so is it necessary to input the 1,2,3 ….998,999,1000 test cases to check the conditions of valid account numbers I,e is it compulsory to write 1000 test cases for the above form
how recovery manager works in winrunner
Tell me agile process in your company
Pls u can u r mail id to my personal mail id also if they dont want to give u r mail id n comman place
Once automated, what are the types of functionality provides the highest Return On Investment (ROI) to the company?
What is the difference between stlc and sdlc?
what are questions asked in TCS for database tester (sqlserver)?ay idea
Can any1 tell me suppose u r doing manual testing on unix platform with Shell Script, then how it is done? How u r implementing it & what is the use of Shell scripting on Manual Testing? plzzzzzzz i need ur help.
What are the typical risks that you identify during test planning and their mitigation plan and Contengency plan.
What is the limit for test steps?It should be 10/20/30etc
