Writing clear bug reports requires precise collocations. Practise the phrases QA engineers and developers use in issue trackers every day.
0 / 5 completed
1 / 5
Fill in: 'Please ___ a bug in the tracker as soon as you notice unexpected behaviour.'
We 'file a bug' — 'file' is the standard collocation in professional software contexts, borrowed from legal/administrative language. 'Log a bug' is also common but slightly more informal; 'open a bug' is acceptable; 'write a bug' is not idiomatic.
2 / 5
Fill in: 'The QA engineer spent two hours trying to ___ the issue on a clean environment.'
We 'reproduce an issue' — 'reproduce' is the technical standard for demonstrating that a bug can be triggered again. 'Recreate' is informal but acceptable; 'repeat' implies doing something again deliberately; 'replicate' is used more for data or studies than for bug verification.
3 / 5
Fill in: 'Once the fix is verified in production, the engineer can ___ the ticket.'
We 'close a ticket' — 'close' is the standard workflow-state verb in issue trackers (Jira, GitHub Issues, etc.). 'End a ticket' is not idiomatic; 'finish a ticket' is informal; 'resolve a ticket' is also used but 'resolve' refers to the fix, while 'close' refers to the workflow state.
4 / 5
Fill in: 'The support team needs to ___ incoming defects before the weekly planning meeting.'
We 'triage a defect' — 'triage' (borrowed from medicine) is the industry-standard collocation for assessing severity and priority of bugs. 'Sort' is too generic; 'classify' focuses only on categorisation; 'group' implies aggregation rather than prioritisation.
5 / 5
Fill in: 'After discussion, the team decided to ___ the cosmetic layout issue ___ because it only affects 0.1% of users.'
We 'mark as wont-fix' — this is the standard resolution status in issue trackers for acknowledged but intentionally unresolved issues. 'Close as invalid' implies the bug is not real; 'label as low' is a priority, not a resolution; 'tag as deferred' is informal.