In every software testing company 'Defect Analysis' report is used to analyse the issues.
If team consists of a single QA member then this is the responsibility of that particular member and if multiple members are involved in QA team then majorly this is the responsibility of QA Lead of the project.
With the help of this report, QA can showcase the other ...
Turn it around.
Instead of viewing it as
A particular use case does not work as expected (view booking history), as it has several defects and the business requirements need to be revised from a quality standpoint.
view it is
A particular use case does not work as expected (view booking history), as it has several defects and the quality requirements need to ...
Testing is a risk analysis and mitigation activity. You mention a specific use case is failing.
- how likely to occur is this use case? And what would be impact be if it did?
From what you've stated, it sounds like the user would not see any booking history. Is this the most typical user type or an edge-case/fringe user? Is the history relevant ...
You state you are junior. I wonder if you are a "team of senior + junior QAs and you are one of the juniors of the team" or you are "alone in charge of this".
If it's the first case, don't do any report, just tell your senior QAs teammates what you see and ask them for advice.
From now on for the rest of the answer I will assume that you are in this latter ...
Is there a possility of financial loss by the end-user and that loss that is significant?
If so, advise management.
If there is no loss, raise it as a functional issue and prioritize it's importance against other issues for the product.
Wonder why you want to present this to management? What is your goal here, what do you hope to achieve. Do you want to show them they have unknown quality issues?
Normaly I would expect the product to have either an issue tracker or a backlog. Just put the issues on the list, discuss it with the business owners and let them prioritize. Together consider the ...