![]() So while it might be a good idea capture and attach a video to to explain a UI issue better, its usually not done due to the perceived effort it takes to do the task. It just doesn’t seem as fast and instant as taking a screenshot, cropping and saving it. The only issue is that you have to create a video- and creating a video sounds like too much work to do in comparison to taking a screenshot. But when the UI issue occurs in time- either in transition or the time it takes to change states, then a video should be the obvious choice to capture a descriptive visual. Images can be used to capture UI issues that can be explained by capturing a single or multiple UI states. In most cases, an image (or images) of the user interface state is all that is required. When filing UI bugs through a bug tracker or even reporting them informally through email, along with the description of the bug, one usually provides a cropped screenshot or screenshots of the UI in different states to illustrate the bug better. For such scenarios, video is effective method of capturing the issue, and there is a tool that makes it as easy and fast to execute as is capturing a screenshot. ![]() ![]() ![]() In this case, it is not possible for an image to describe the issue. Some UI issues are not only state based, but time based as well- where the bug might occur in transition of states or the time taken to change states (transitions and states are explained at the end for the unaware).įor example, you might want to illustrate the usability problem of a pull-down menu which has a zero time delay, thus making the selection of items down and up the hierarchy difficult for the user as the slightest overshooting of the target results in disappearance of the desired item. All UI bugs cannot be captured through images. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |