-
What do we do when we get a bug in an application first? Explain it with the help of an example of Bug Life Cycle.
Siva Anand
- Apr 27th, 2011
Reproduce the bug twice.Analyse the steps in which scenario the bug arise and report the bug.
munnu
- Apr 29th, 2008
when we found a bug,we have to retest to know whether the bug found is valid or not,if it is a valid bug it will be posted.
-
What is the process of bug cycle?
Siva Anand
- Apr 25th, 2011
Bug Life Cycle1.Open2.Assigned3.Acknowledged (If Issue reproduced by developer)4.Feedback(If Issue not reproduced by developer)5.Resolved (If Developer fixed the bug)6.Retesting 7.Closed (If Issue fixed)8.Reopen (If Issue exist)
jyoti_02
- May 29th, 2008
Bug life cycle is the cycle through which a defect goes starts when bugs found and ends when bugs is closed after ensuring its not reproduced.Phases of Bug life cycle:-1) New: When bugs found2) Open: ...
-
Bug Status
You Opened a Defect, for that you got a comment that "Its not a defect, this is according to new changes in requirement, later this point will added in requirement document" What status you will provide for this bug until the requirement update?
gsrmohan
- Feb 21st, 2011
The developer set the status as "Wont Fix" for this .We don't have to close the defect.Once SRS is updated we can reopen the defect by adding comment to the defect.
TumuPavan
- Feb 16th, 2011
There are 2 parts to this answer: 1) The bug that was reported was on Build X which is developed and deployed based on a frozen set of requirements. If the product deployed does not confirm to t...
-
Defect Responsibility
Suppose you found a defect and got a status as "Defered/ Suspended" and got comment that this defect will not be no longer in the next release from developer side. Deployment completed for next release and came for testing. What is your responsibility of this defect.
TumuPavan
- Feb 16th, 2011
In my experience i have not followed the practice of logging new bugs to associate with a deferred bug. What I have seen and practiced with in my projects is have Developer will only resolve a bug...
sabnekar
- Oct 30th, 2010
Generally such defects are called as Migrated defects.As per my experience.. We move such defects to new project in Quality center, so a new defect number is created in new release. Now that has to te...
-
Bug Weightage
What are different weightages given for a Bug?
TumuPavan
- Feb 16th, 2011
Severity (Severity is Absolute ) Severity 1: Bug causes system crash or data loss.Severity 2: Bug causes major functionality or other severe problems; product crashes in obscure cases.Severity 3...
vaibhavst
- Dec 11th, 2010
Severity 1 - Show stopper issue. In which case testing cannot be continued.Severity 2 - Not a show stopper but can considerably damage the system which is under testSeverity 3 - Minor functional...
-
Suppose that you are running tests on the windows calculators and find that 1/1=2,2/2=1,3/3=10,4/4=1,5/5=26&6/6=1..write a bug description that effectively describes this problem...iits urgent
iamtheone
- Jan 9th, 2011
(x/x) operation where x = Positive odd integer uses the formula ((x*x)+1) instead of integer division.The (x/x) operation works fine for even numbers.
sidharthaIBM
- Jul 16th, 2010
The output will be always one when a number is divided by itself.It is giving correct output when the no is even i.e when the no is divisible by 2.But when the no is odd it is squaring the no and increasing it by 1.Ex--3*3+1=10
-
Who will Change the status of the Bug...say : Deferred " ?
pandit
- Dec 14th, 2010
Development Team & Delivery Manager will decided to change the Status in deferred.( If I am wrong pls inform me.)
mathan_vel
- Sep 30th, 2010
It depends up on the Bug. Those who responsible for the bug will change the status as "Deferred" (who had to decide when to test it again). Most probably Project Manager..example: If the Bug...
-
Enterprise Edition of QC
Which extra module comes along with the Enterprise Edition of QC?
Rose1
- Dec 13th, 2010
The Quality Center has 4 basic modules and 2 additional modules.The 4 basic modules are1.Requirement2.Test Plan3.Test Lab4.DefectThe 2 additional modules are1.Business Components(Used to business process testing)2.dash board(for real time project tracking)
sheetal.chelwa
- Feb 3rd, 2010
HP Quality Center Enterprise Edition (formerly HP TestDirector for Quality Center software): Suitable for mainstream QA organizations that may not have expanded globally and may not yet be managing large, complex QA initiatives.
-
Change Defect Status
A Defect is Deferred/Suspended State and stated the comment as "The defect wont be no longer in next release" by developer. On next deployment you retested the Defect and noticed that the defect is still there.Now Question is, Who is responsible to reopen the Defect? Tester or Developer?
vaibhavst
- Dec 11th, 2010
In this case Tester is the one who is responsible for opening the defect. Since in QC "Deferred" is end status after which the status cannot be modified (local admin can modify the end statu...
-
What is build interval period?
mathan_vel
- Sep 30th, 2010
The Time Gap between one build completed time to next build introduced time.Time gap between Build 1.0 to build.1.1
preethi.gollamandala
- Sep 9th, 2009
Its a period of getting two different AUT s from the developers.it means the gap b/w two different testing builds received from the developers to testing team
-
Missing important bug
If i miss a important bug and i realise it very late then what will i do?
kishore11m
- Aug 11th, 2010
First check whether the bug existed in your scope or not, if it is in your scope, check whether you have covered the senario in testcase document, if not, prepare a Root Cause Analysis Report and send to the team lead.
DattaDeshmukh
- Apr 9th, 2010
Every bug you founf is important. If you found it at the end of release cycle then also inform it/log it. Let the BA decide what to do with it. If it is critical/major then it should be fixed. If it is normal/minor/corner case then can be deffered to next relase.ThanksDatta Deshmukh
-
Test cases on bug tracking tool
What are the test cases on bug tracking tool?
jatinjain
- Jul 30th, 2010
There can be many types of test cases like functional,usability, GUI,database,security etc.For the functional part high priority ones should be :1.Validating all states of bug cycle.2.Validating ...
kurtz182
- Dec 17th, 2009
I'm not sure I fully understand this question. Bug tracking tools are like any other client-server or web-based distributed applications, so the test cases will be identical. These inc...
-
New Bug and Open Bug
What is the difference between New and Open bug? Who is responsible for changing the phase of bug from New to Open?
krishnalatha
- Jun 23rd, 2010
When a tester creates or enters a new bug, he can assign the bug to 2 different people, one is directly to the concerned Developer, or TL or PM. When we directly assign to the developer, the deve...
kurtz182
- Dec 17th, 2009
A new bug is one that has not been reviewed and assigned. An open bug is one that has undergone a review process and a Project Manager has assigned it to someone (ex: development staff, business analyst, etc.) for further research.
-
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...
-
Defect tracking system objectives
What is the prime objective of a defect tracking system?how is defect fix validated?
mathan_vel
- Jun 10th, 2010
The Prime Objective of the Defect Tracking the System is to Manage & Organize the Defects/Bugs in the Test Life Cycle from Open to Close state
kurtz182
- Dec 26th, 2009
The prime objective of defect tracking systems is to manage the life cycles of defects from open to closure.
-
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...
-
What are the fields in the summary report preparation.
What type of reports are to be generated by a Tester.
gauravworks
- Feb 27th, 2010
Fields in the summary report depends on project to project. Summary is a brief detail of all the things done and discovered during testing. Most important things to be included in a summary repor...
srinivasulub1981
- Dec 9th, 2008
What are the fields in the summary report preparation. - This template is diff company to company, we followed the below fields -> Test Case Summary Report: -Company Name ...
-
Estimate a Bug
How do you estimate the Bug?
kk01041883
- Jan 17th, 2010
The bug is prioritized based on the impact of the defect on the application on that module or on the dependent modulee.g If you are not able to create a data which is consumed by the other modules of ...
kurtz182
- Dec 17th, 2009
A bug estimate is based on guidelines established for Severity and Priority. A defect's Severity and Priority levels depend on these factors:1) It's impact on users2) Liklihood of occurrence3) It's perceived value to end-users4) It's value to your company
-
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...
-
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...
Bug Tracking Interview Questions
Ans