Bug life cycle:-
1:-tester find a bug and give its status "new" and send to TL(team leader)
2:-TL verify its wheater its a geniune bug or not if yes then give its status "open" and forward to developer for fixing
3:-developer now fix the bug and can give its status:
iii-or if he/she solve it give its status fix and send to tester
4:-now tester verify it if the bug is fix then give its status-closed
and if bug is still exist then give its status-reopen
it was bug life cycle
The bug life cycle is so easy and simple when going thru it theoritically and all the above post are perfect and very informative .Thnx for the answers. I am actually working in a small company and this is very much different .... I wanna know that the above mentioned process work in mnc's ....or its jst a theory??? and my other question is ....In small companies there are alot of projects and jst one test lead so will he still validate whether each and every bug in projects are genuine???? Can anyone explain about this???
According to me companies follow their own approach to fix the bug.. Friend please understand a single thing in an application fixing all bugs is not so easy and not possible too .. fixing the bug immediately depends of the severity of the bug or else fix in the later version... We stop testing a project due to time line specified us ends and some other conditions..
This is the fact happens not some times but many times in the real time.
Bug life cycle
1.First tester find the bug in the application then send it to the test lead or team leader.
2.team leader see the Bug is valid or not if it is not valid the he assign the bug as "Rejected".
2.If the team leader finds the bug is valid then he send the bug to the Development team and status of the bug is"Open".
3. development lead checks the bug is valid or not if it is not valid then he send the bug to the team lead and the status is the "rejected".
4.If bug is valid then development lead assign the bug to the developer then the status of the bug is the "open"
5.Developer checks the bug is valid or not if it is not valid then it is send to the development leader and status is "rejected".
6.If bug is valid then developer fix then bug and send to the development lead.status is "Fixed".
7.The fixed bug send to the team lead ,team lead send to the tester.Tester test the bug if it really fixed.if it's really fixed then it get closed by the Tester.And status of the bug is "Closed".
8.If the bug is not import to developer then also it is rejected.
9.or it can be postpone by developer.Then the status of the Bug is"Differed".
Thank u !
Pl'z correct me if anything wrong.
The bug needs to be communicated and asssiged to developers that can fix it.
After the problem is resolved , fixes should be retested, and determinations made regarding requirments for regression testing to check that fixes didn't create problems elsewhere.
hi, can anyone explain about the build in bug life cycle. Thanks.
a new bug found by tester/customer. Bug is submitted in bug host account. Bug review after review its assigned to development team. Development team fixed that bug and send to qa. Qa verifies bug and gives status fixed or not. Re-assigned/closed.
u said that bug life cycle never change from company to company its true. bug cycle is same. BUT, the main tool is tracker, its on the tracker, which is used by the company. you can find that every tracker have the different status to set for Tester and designer. and Also, if u point out then check that medium level company have their own tracker tool. and somewhere the tester is directly assigns bug to developer. so there, changes occurs.
build-once the business analyst gives the requirment document to devlopment department,they develop the appication based on the customer requirements and it is released to the testing department,that type of the release is called build.
Applying for a job can be a stressful and frustrating experience, especially for someone who has never done it before. Considering that you are competing for the position with a at least a dozen other applicants, it is imperative that you thoroughly prepare for the job interview, in order to stand a good chance of getting hired. That's where GeekInterview can help.