Quality Testing

Quality is delighting customers

Hi guys,

I'm new  to testing.

I want to know the bug life cycle of bugzilla and Jira.

and what status developer will give if he is working on Bug

 

 

Thanks in Advance

regards

Akbar

Views: 134

Reply to This

Replies to This Discussion

I can speak for Bugzilla, but I'm not familiar with Jira.

 

Out of the box, Bugzilla's bug lifecycle looks like this: http://www.bugzilla.org/docs/2.18/html/lifecycle.html.  When a developer is working on the bug, the status will be "Assigned".  

 

An organization may choose to customize the lifecycle though.  For example, I once worked for a company that had an additional state called "In QA", which sat between "Resolved" and "Closed".  The "In QA" state meant that the developer believed the bug was fixed and the fix had been deployed to the company's QA environment.

 

 

thanks Bill
On Jira, when a developer works on that bug,the task is "in progress"(there is on left side - Start progress) and when the task is finished and he sends the task to QA, he selects "Test Issue" - status "in testing". After testing, the QA approves or rejects the task, depending on the result of testing.
thanks Diana

hi akbar,

  While developer working on bug, he wont change the status. once it got fixed he ll change it to fixed....

see hemavathi....devloper will change d status when he went on to the bug probably might be ny case is it fixed,rejected,cant reproduce............so dont say its just fixed status from developer side status can vary from company to company hope u get me nw :)

BUGZILLA:

Bug Life cycle: UNCONFIRMED,NEW,ASSIGNED,REOPENED,RESOLVED,VERIFIED,CLOSED

As a Developer: FIXED,INVALID,WONTFIX,DUPLICATE,WORKSFORME,MOVED,REMINDLATER

RSS

TTWT Magazine

Webinar

You Can


Call for Articles

Advertisement

Videos

  • Add Videos
  • View All

Badge

Loading…

© 2012   Created by Quality Testing.

Badges  |  Report an Issue  |  Terms of Service