devender prasad
Answered On : Jul 21st, 2005
will you please explain the life cycle of a bug
Login to rate this answer.
Raj
Answered On : Aug 12th, 2005
The Life Cycle of a bug in general context is:
Bugs are usually logged by the development team (While Unit Testing) and also by testers (While sytem or other type of testing).
So let me explain in terms of a tester's perspective:
A tester finds a new defect/bug, so using a defect tracking tool logs it.
1. Its status is 'NEW' and assigns to the respective dev team (Team lead or Manager).
2. The team lead assign's it to the team member, so the status is 'ASSIGNED TO'
3. The developer works on the bug fixes it and re-assings to the tester for testing. Now the status is 'RE-ASSIGNED'
4. The tester, check if the defect is fixed, if its fixed he changes the status to 'VERIFIED'
5. If the tester has the autority (depends on the company) he can after verifying change the status to 'FIXED'. If not the test lead can verify it and change the status to 'fixed'.
6. If the defect is not fixed he re-assign's the defect back to the dev team for re-fixing.
So this is the life cycle of a bug.
Login to rate this answer.
M.Ravinder
Answered On : Sep 6th, 2005
which types of Bugs your find at the time of Integration Testing?
Login to rate this answer.
high
Answered On : Sep 13th, 2005
Login to rate this answer.
srikanth-bangalore
Answered On : Sep 21st, 2005
three types of bugs, they are 1) crictal bugs 2) major bug 3) minor bugcritical bug - It affect the next module.Major Bug- It affects within the module.Minor Bug- Only spelling mistakes.
Login to rate this answer.
Sriram.B
Answered On : Oct 6th, 2005
What is the test case format for the real time projects.
Login to rate this answer.
Sandeep Korde
Answered On : Oct 7th, 2005
The application is suppose to be as per the user req
Login to rate this answer.
The different types of bugs are as follows:--
1)Textual error (Message prompted error)
2)GUI(Graphical User Interface) error
3)Functionality error
4)Design error
5)SQL query error
6)Hardware failure
Severity of the bug is assigned according to the impact of the bug on the application. Various types of Severity could be:--
Feature, trivial, text, tweak, minor, major, crash, block

2 Users have rated as useful.
Login to rate this answer.
pallavi
Answered On : Nov 7th, 2005
System Crases by any resion like Not Declere NULL pointer ---------High
Login to rate this answer.
We will come across various types of bugs while Testing an application.
1. User Interface bugs. Severity is low
2. Functionality related bugs. Severity is high or Critical depending upon the module that was affected.
3. Bugs relating to validations.Severity is high depending upon the importance of the module that was affected.
Login to rate this answer.
hi pallavi can you pls tellme what exactly you said in the questions
Login to rate this answer.
SCHITTOOR
Answered On : Apr 24th, 2006
see. we will give siviarity and priarity based on the Business Rule on perticular project . this is not same to all project , different project different business rules.
Thanks
Srinivasulu,chittoor
Login to rate this answer.
rekha
Answered On : Apr 26th, 2006
i am getting cleared with so many doubts
Login to rate this answer.
Leena Saraf
Answered On : May 16th, 2006
1)GuI Related(spelling mistake,non-uniformity of textbox, colors)--Low--P3
2)Functionality related--Medium--P2
3)System/application crashes---High---P1
Generally high priority defect are those on basis of those build may be rejected
Login to rate this answer.
Different types of bugs :Severity depends upon the impact of this defects over the functionality and according to the users requirements.I am not able to specify the severity of the below mentioned bugs.
User Interface Bugs
Input Domain Bugs
Error Message Bugs
Calculation Bugs
Critical Bugs
Hardware Bugs
Load Scenario Bugs
Source Bugs
Version Control Bugs
ID Bugs

1 User has rated as useful.
Login to rate this answer.
shann
Answered On : Sep 28th, 2006
common types of software bugs. * Divide by zero * Infinite loops * Arithmetic overflow or underflow * Exceeding array bounds * Using an uninitialized variable * Accessing memory not owned (Access violation) * Memory leak or Handle leak * Stack overflow or underflow * Buffer overflow * Deadlock * Off by one error * Race hazard * Loss of precision in type conversion almost every bug listed will have high and medium severity depending onthe project.
Login to rate this answer.
sridevi
Answered On : Dec 11th, 2006
what are the things to test when a GUI is changed?
Login to rate this answer.
HARI KRISHNA
Answered On : Apr 13th, 2007
- A bug is found by QA or customer
- That bug is assigned to developer
through bug report
- Then developer fixes the bug.
- Then the tester verifies it by
retesting
- If the bug is fixed, it is closed,
otherwise it is send it back to developer
Login to rate this answer.
vajra
Answered On : Jun 14th, 2007
new
open
reopen
fixed
closed
Login to rate this answer.
Kaarthi - Kovilpatti
Answered On : Nov 5th, 2007
Yaa.. The different types of bugs are Critical,Major and Minor. According to the priority the bugs will fix in the projects.
Login to rate this answer.
GUI bug
Login to rate this answer.
1. Usability issues
2. Functional issues
3. Security related issues
4. GUI issues
5. Hardware/software issues
6. Globalization issues
Srinivas
Login to rate this answer.
Severity varies between scanrio to scenario.
Different types of bugs :
User Interface Bugs
Input Domain Bugs
Error Message Bugs
Calculation Bugs
Critical Bugs
Hardware Bugs
Load Scenario Bugs
Source Bugs
Version Control Bugs
ID Bugs
Login to rate this answer.
Raaj sorry to say but in ur bug life cycle dev doesnt reassigned to tester its the test manager
Login to rate this answer.