-
When should I write Bug report?
Is it compulsory or just it helps in the process of testing?
I was thinking about Bug report? Why we should write bug report when we have already bug tracking tool to raise and write down details about it? If we need to write it, where it will be useful?
thanks in Advance
SAlex
- Jun 9th, 2015
@gaurav.khurana, shivakumar is right, it need not to be interchanged. And reporting a bug is different from bug report. Bug report is summary of bug reported.
Gaurav.khurana
- Apr 18th, 2015
Writing details in bug tracking tool is nothing but - Bug report. When you are sure that there is bug in the system you should open a bug in the tool and mention all the necessary details for it so th...
-
Top Ten Tips for Bug Tracking
A good tester will always try to reduce the repro steps to the minimal steps to reproduce; this is extremely helpful for the programmer who has to find the bug. Remember that the only person who can close a bug is the person who opened it in the first place. Anyone can resolve it, but only the person who saw the bug can really be sure that what they saw is fixed. There are many ways to resolve a bug....
kurtz182
- Dec 30th, 2009
Top twelve tips for initial bug reporting:1) Ensure you can reproduce the defect before entering defect report2) Ensure there are no duplicates before entering defect report3) Include all relevant det...
preethi.gollamandala
- Sep 9th, 2009
Tester should be able to reproduce the bugbug description should be understadable to everyonewe should assign proper priority & severity to the reported bug we should attach proper screen sh...
-
What is build interval period? in simple words plz
srinivasulub1981
- Dec 10th, 2008
Hi This can be decided completely by managers or leads, it's just a interval between current build and future build.. yes it may be 1 week or 1 month or 3 months..Srinivas
jainbrijesh
- Dec 30th, 2006
Build interval time is the frequency of build it may be daily or weekly etc.
-
If the customer requirements are changing continuously as a tester how you are going to manage the situation?Suppose you have prepared test cases but still some more time is required to receive the build in between time what you can do?How you know the bug you sent is fixed or not?
Read Best Answer
Editorial / Best Answer
srinivasulub1981- Member Since Dec-2005 | May 2nd, 2007
If the customer changing the reqs ... : If the change came in between the testing time of previous requirement ( change) then i can stop testing and intimated to my TL... if the change came after completion testing of prev change then i can go for testing .. I think in this situation we can't do anything like reporting to PM or any except doing testing for new changes.. at present we doing like this only.. coz all the risk analysis, cost estimations are already done by PM and given it for testing..
Suppose you have.... : In between we can review test cases ( by me or peer).. try to prepare effective test cases , or can test application upto completion part if possible...
How you know..... : 1. Daily we check the BTS for bug status
2. Actually we sent a mail with bugs to concerned developers to fixed, he revert back with status of bugs, then we can go for re testing.
3.If using any test management tool, if automatic email configuration is configured then concerned tester should receive a conformance email that the bug is fixed...narendra
- Oct 1st, 2015
As per Project is concerned, we are working for customers and their requirements to be met... so in this case I hope every tester must be flexible at any moment and accept the change at any time... an...
vasudha
- Apr 21st, 2015
The information at. The top of the file is XML namespace
-
What are the difference between rational clearquest and testdirector?
srinivas
- Jul 13th, 2011
Rational is powered by IBM. Test Director is powered by Mercury.
Rational is bug tracking tool,
test director is test management tool and tracking tool
srinivasulub1981
- May 20th, 2009
TD or QC is a test management tool which contains below modules.-> Requirements-> Test plan-> Test lab-> DefectsWhere as Clear Quest is purely a bug tracking tool
-
On what basis the planned testing efforts is calculated for the entire project?
gauravworks
- Mar 5th, 2010
To estimate the testing effort for complete project following points need to be analyzed:1) Number of Functional requirements to be tested.2) Complexity of the Testing Task3) Number of resources avail...
G.D.S.Prasad
- Mar 12th, 2009
We follow TCP analysis to calculate the testing effort required for a change request. Some organizations follow FTP Analysis. Test Case Points (TCP) Test Case Point deals with the estimation of the ef...
-
On what basis we give priority and severity for a bug and give me one example for high priority and low severity and high severity and low priority?
Pradeep Ind
- Dec 27th, 2006
Severity - Depending upon the testers mind, with the impact of the client, severity will be stated. Priority - Depending upon the urgency on the tester and his workaround. i.e.,.how long the tester can work until the bug is rectified
P.M. Reddy
- Dec 20th, 2006
I think wrong alignment will comes under high priority and low severity
-
What is the seviority if we will give the duplicate account number?
mithr17
- Oct 31st, 2011
QA never sets severity. Severity and priority are set during defect review AKA triage meeting. BA, devs and QA team sit down and decide the severity. If this is an interview question you can still say the above fact and add to it: high severity.
Nagaraju.Keta
- Dec 23rd, 2006
Hi,Duplicate A/C NO. is VERY PROBLEMATIC ISSUES due to that reason we can give for that "Seviority is FATAL and Priority is HIGH" How much seriousness of the Bug is "SEVIORITY" and How much importance to solve that problem is "PRIORITY" regards,Nagaraju.Keta9989818605(Corporate Trainer)
-
What do you do when the developer disagrees with a failed test result?
srinivasulub1981
- May 7th, 2009
HiThis will happens in below conditions.a. Bug logged, dev rejected due to unavailability of clear steps or not able to reproduce. In this situation, we need to mention t...
-
What are Attributes of a Bug?
kk01041883
- Jan 17th, 2010
Bug attributes1. Synopsis - Brief description about the issue2. Description - Steps to reproduce the defect3. Serverity4. Priority (Optional)5. Regression or New issue 6. Raised build number7. Action ...
Shakkila
- Dec 10th, 2008
Here are some of the bug attributes,1. Bug's Occurence ( Source or which version of the application it has occured ).2. Severity and prority of the bug in order to resolve it.3.Current status of t...
-
Report the Bug
How did you report the bug in your last job?
mathan_vel
- Jun 10th, 2010
How did you report the bug in your last job? Its all up on the Organization, Project, Client and varies.Lot many tools is there to Reporting the bug. In my case I used Excel sheets & Is...
kurtz182
- Dec 22nd, 2009
Posting a bug is typically done in a defect management tool. However, some test groups use a spreadsheet program. Make sure the defect report contains: 1) defect id2) test case refere...
-
How do we track a bug? What is the format of excel sheet in which we write the bug details? How do we give the severity and priority to the bugs?
kurtz182
- Dec 30th, 2009
BUG TRACKING PROCESS: This is a process used to manage defects from the time testers discover them to the time they are closed. When testers discover defects they open bug reports and the ...
-
WHAT IS A GOLDEN BUG ?
srinivasulub1981
- May 7th, 2009
HIGolden Bug: A bug which occured in all instances of application of high severity and high priority.Ex: If an app having 3 pages, in each and every page doesnt have submit buttons then this can be considered as GOLDEN BUG.Srinivas
rupesh kumar
- Jun 28th, 2007
The bug finds in build before release build to customer rmeans complete all types of testing , comes release time that time to find bug that bug is golden bug, we go for final regression testing on high defect density module
-
How we can explain a bug which may arrive at the time of tesing. explain that bugs in details.
kurtz182
- Dec 20th, 2009
Explain a bug by doing the following:1) Verify the defect isn't already known and entered in the defect tracking database2) If you have any questions about it, ask other member of the group f...
mathan_vel
- Aug 21st, 2009
Reviewed the bug once to confirm and logged the bug in the Bug Tracking tool with the status as Opened. If still the confustion is there in the bug, consult the same bug with TL and get reproduce. The found bug is described in the Bug Description section.
-
Can anyone please tell me "what will be the role of tester if bug is reproduce "This question was asked in the Interview.
chanakyaniti
- Jan 24th, 2007
Do you meanWhat is the role of a tester if a bug is reproducible?or do you meanWhat is the role of a tester if a bug is duplicable?If the bug is reproducible, the developer has to fix it and send it b...
neha
- Jan 16th, 2007
The main objective of a tester is to report a bug to the developer.and it is the responsibility of the developer to clear the bug only if he feels that the reported bug is a valid one and is of high p...
-
Suppose a bug was found by the customer, As a Testing what is your comments on this issue?
thebobblogs
- Nov 20th, 2011
Review the bug to see the root cause. Then, plan and do preventive action.
thebobblogs
- Nov 20th, 2011
Review and analyze that bug. If testers are missing, we should consider what is the gap and see how to prevent it.
-
What is bug leak?
mithr17
- Oct 31st, 2011
I agree, they are 2 different things. bug/defect leak is when something is caught by UAT testers or end users or client.
naresh reddy
- Jan 18th, 2007
Bug leak also called as bug slip,after testing and releasing the application the end user raised the issue then it is called bug slip.this is given the p1.more bug slip occur when we perform ad-hoc testing.RegardsNareshvallabhareddy@gmail.com
-
-
What is difference between BUG and DEFECT ?
priti
- Dec 28th, 2011
Bug: Bug is a fault in a program or application which is found when the actual result diverts from the expected result.
Defect: A flaw in a component or system which causes the component or system to fail to perform its required function. e.g. an incorrect statement or data definition.
-
Bug Tracking Interview Questions
Read Best Answer
Ans