Software testing relates to a feature or broken functionality testing which software testers perform after developers have worked on it. For this, almost all top software testing companies use some tracking tool where the tickets for feature development or fixing a broken functionality are reported. This helps in keeping the track of the issues or tickets and the progress on them as well.
These tickets are tracked by their status. These statuses have phases like ‘In Dev’, ‘Code Review’, ‘Impeded’, ‘In progress’, ‘Ready for test’, ‘In Test’ and ‘Done’. As, we are talking here about only ‘Done’ so we will be focusing on this status mainly.
The ticket is reported in the tracking tool to say Jira by the product owner (if it is a new feature) or by the software tester (if it is a broken functionality). These tickets are further worked upon by the Developer and they will further changes the status of the ticket to ‘In Dev’ or ‘In progress’ when they start working. Once it’s done from his end. it is made ‘Ready for Test’. From here the software tester picks up the ticket and starts working on it. The tester will test all the possible scenarios and the aspects which can break the new feature or the broken feature again. Tester changes the status of the ticket to ‘In Test’ before start working on it. Once the tester has tried all end-user scenarios and he declares the ticket good to go he changes the status of the ticket to ‘Done’.
Now the point here is that software Tester can make a ticket status to ‘Done’ but this is not just done by the tester. When it comes to a feature development all the acceptance criteria is decided by the product owner and Dev & QA works on that. Now, when it comes to a feature development ticket, it’s not important that QA will change its status to ‘Done’ once the work is being done on the ticket. It’s sometimes the responsibility of product owner to change the status of the ticket to ‘Done’ once he approves that all the changes requested by him are implemented.
‘Done’ is the last status of the ticket, at this point, we can think that the ticket is closed and not need any more work to be done upon. But it is not always necessary that a Done ticket cannot be worked upon again. Done ticket can be reopened and can be reworked if needed. This ticket is then closed again once the work is done again.
‘Done’ is the status which is given to the ticket when we can consider that this feature is implemented properly or the broken functionality is working completely fine.
Hope this information will be helpful for you.