The image should be mentioned by name in bug description or in comments to bug report (Otherwise why do we need this image and why should I or Dev, PM check attachments if it's not mentioned in bug-report?)Īny other suggestions? Is there anything wrong in my idea? Timestamp followed by clear description what is going wrong. And to use tools created especially for this purpose (e.g. To reduce differences in style and avoid usage of old, inconvenient tools (e.g. See also Teachers should stop using red pens to mark homework), green for highlighting correct behaviour and for short comments what actually should be done to fix the bug. Orange color for highlighting errors (personally don't like red cause I want to have good relations with Devs. As I see it would be great to have short guidelines for all testers and there are three of them till now: Devs and PMs could go crazy from different ways five testers create screenshots and highlight them. Which set of guidelines should be used in a big testing team to reduce differences in created screenshots.
0 kommentar(er)
