Which set of guidelines should be used in a big testing team to reduce differences in created screenshots. Devs and PMs could go crazy from different ways five testers create screenshots and highlight them. As I see it would be great to have short guidelines for all testers and there are three of them till now:
- color usage in images
- tools used to create screenshots
- naming of images
Color usage in images
Orange color for highlighting errors (personally don't like red cause I want to have good relations with Devs. 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.
Tools used to create screenshots
To reduce differences in style and avoid usage of old, inconvenient tools (e.g. Paint). And to use tools created especially for this purpose (e.g. TechSmith's Jing or SnagIt)
Naming of images
Timestamp followed by clear description what is going wrong. Like in TechSmith tool:
2015-10-14_1531_[description of the image clear to human being]
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?)
Any other suggestions? Is there anything wrong in my idea?
- added several tools for screenshots and image edition as suggested by @Dhiman
As of now we don't use timestamp in image names (it's enough of create time in image-file attributes), but we added release number and server to the name. E.g.:
It's very usefull for regression testing you see the configuration where the problem was found.