defect life cycle in testing code example

Example: defect life cycle

In my company we use Jira XRay for as bug tracking tool.
So when I found a bug it means somehow the
expected result is not matching with actual result.
Then I make sure that it’s a real defect.
First I double check my test scripts whether they are ok.
Then I check my enviroment whether everything
up and running. Then also I check if it is
known or duplicate issue. 
Once I am sure that it is defect 
then I take screenshots and
contact with the responsible developer and
tell him/her about the test results.
If he fixes immediately that is ok. 
If he consent that is a bug then
I create a new ticket on Jira and I add all
screenshots and to help him to understand how
bug looks like. I link the bug with related test
and I assign to developer and he/she starts
fixing the bug. After fixing he deploys the code 
and I re-test it again.
If it is passed this time it means
we are good to go, close the defect life cycle.
But if it is still failed then I reopen the ticket. 
After everything is ok then I am closing the cycle.

Tags:

Misc Example