![]() ![]() We have defined two colors because sometimes the area which you want to highlight already have either same background or border, which makes highlighting not usable. So, you can use Red color without any issue as this is part of job which team should understand (I don't mind your Orange color idea too), but Red color is more eye catching. ![]() I have gone through the posted article and will say, If highlighting bugs with red color can lead to team issues then creating bugs is more offensive then that. Regarding the color, we have been using Red (R =255, G=B=0) and Blue (R=G=0, B=255) color only for highlighting in our team (via SnagIt) from last couple of years and didn't faced any issue with any developers. I will answer/go through your points one by one and will try to add some valuable information in addition to your useful & precised description.Ĭolor usage in images: Highlighting becomes critically important when creating bugs related to GUI. I put all that meta-data into the bug tracking system that includes the screenshot, e.g. Personally I do NOT pay attention to date stamp and screenshot file name description. So make sure you supplement a picture with such context. A picture doesn't explain the expected result.A picture by itself doesn't explain what is right, and what is wrong. #Timestamp snagit 12 fullThis addresses one of the main useful things of a full screenshot.Ī picture doesn't explain how we got there Many screensavers use a data and time in the filename. Should contain date in the filename format when available by default. #Timestamp snagit 12 freeThis can be done on top if images using free or low cost tools such as For example: Commonly done with red to circle items or write comments. #Timestamp snagit 12 movieRemember that a 9"x9" movie is nine times bigger than a 3"x3" (9*9=81 and 3*3=9)īe annotated with additional text to help indicate the problem. For movies you may want to limit yourself to a part of a window in order to save space and reduce file size. This can be incredibly helpful when bugs are hard to find and reproduce. In this case I expand 'screenshot' to include using a movie and I use QuickTime (OSX) to do screen recordings. Also it often means you then have to zoom in to see the actual window and issue.īe taken in a format that allows the image to be shown embedded into your ticket tracking system if you are using one. I am not a fan of the whole desktop screenshot as it includes too much non-relevant, distracting and possibly even personal, information. So for browser screenshots use the whole browser window so people can see the browser, browser version and any toolbars that reflect installed tools and any footer toolbars that show info. It's very usefull for regression testing you see the configuration where the problem was found.Ĭontain all the information needed. added several tools for screenshots and image edition as suggested by (1):Īs 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.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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |