{"id":3815,"date":"2015-09-22T13:32:03","date_gmt":"2015-09-22T11:32:03","guid":{"rendered":"https:\/\/usersnap.com\/?p=3815"},"modified":"2025-08-05T17:44:37","modified_gmt":"2025-08-05T15:44:37","slug":"bug-reporting-workflow","status":"publish","type":"post","link":"https:\/\/usersnap.com\/blog\/bug-reporting-workflow\/","title":{"rendered":"Fundamentals on setting up your bug reporting workflow"},"content":{"rendered":"\n

With all these emerging new devices – from mobile devices, to wearables, to VR, to smart devices – having a proper bug reporting workflow<\/strong> in place becomes quite a challenge.<\/p>\n\n\n\n

Building web applications in particular might seem quite painful due to the different screen sizes of the used devices. It can even be worse than testing native apps for the Android ecosystem.<\/p>\n\n\n\n

In this post, I\u2019d like to show you different ways of setting up your bug reporting workflow. Including manual, automated and crowd-sourced workflows.<\/strong>
<\/p>\n\n\n\n\n\n\n\n

The What and Why of bug reporting.<\/h2>\n\n\n\n

First things first. In order to understand the basics of bug reporting, we need to answer the questions of what bug reporting is all about and why it\u2019s a necessary step in every web project.<\/p>\n\n\n

Try Usersnap for Bug Reporting Workflow<\/h2>Try Usersnap Now<\/a><\/div>\n\n\n\n

<\/p>\n\n\n\n

The What.<\/strong>
Bug reporting<\/a> can be defined as the workflow used by quality assurance personnel and developers to keep track of software problems and resolutions.<\/p>\n\n\n\n

The result of the bug reporting workflow are so-called bug reports<\/strong>.<\/p>\n\n\n\n

\n

Bug reports are the only tangible product of the testing process itself, solid technical documentation that describes a failure mode in the system under test that could affect the customer’s experience of quality.<\/h3>\n<\/blockquote>\n\n\n\n

(source: rbcs-us.com<\/a>)<\/em><\/p>\n\n\n\n

The Why.<\/strong>
The short answer: Because we want to release bug-free<\/a> applications and keep our users happy.<\/p>\n\n\n\n

Bugs and misleading errors can be found in nearly every software ever shipped on this planet, right? So how can we ensure a bug- and error-free software while developing it?<\/p>\n\n\n\n

Well, it\u2019s time for some proper bug reporting.<\/p>\n\n\n\n

It\u2019s time for bug reporting.<\/h2>\n\n\n\n

Bug reporting<\/a> takes place in various steps of a project. If you\u2019re working on new web applications, websites or apps, you probably follow the following steps:<\/p>\n\n\n\n

    \n
  1. User needs: Identify the user needs.<\/li>\n\n\n\n
  2. Design<\/li>\n\n\n\n
  3. Code<\/li>\n\n\n\n
  4. Test (internal bug reporting)<\/li>\n\n\n\n
  5. Release your website \/ app \/ product<\/li>\n\n\n\n
  6. User feedback (external bug reporting)<\/li>\n<\/ol>\n\n\n
    \n
    \"bug<\/figure>\n<\/div>\n\n\n

    As displayed in the workflow above, I\u2019d like to distinguish between internal and external bug reporting. Of course this workflow might differ depending on your project- and team size. <\/span><\/p>\n\n\n\n

    However, there will and should always be a project stage for internal testing (sometimes referred to as alpha testing) which includes bug reporting template<\/a> by web development and\/or QA teams.<\/span><\/p>\n\n\n\n

    3 ways of bug reporting in web development teams<\/h2>\n\n\n\n

    Depending on your project and company, you\u2019ll probably end up with one of the three following ways of bug reporting.<\/p>\n\n\n

    Try Usersnap for Bug Reporting Workflow<\/h2>Try Usersnap Now<\/a><\/div>\n\n\n\n

    Automated Browser Testing<\/h3>\n\n\n\n

    If we take a look at automated testing<\/a> or bug reporting, it\u2019s all about setting up test cases which can be run without any human interaction. Automated bug reporting requires a comprehensive testing suite which enables you to execute pre-scripted tests on a web application before releasing it into production.<\/p>\n\n\n

    \n
    \"automated<\/figure>\n<\/div>\n\n\n

    There are currently great tools and workflow suites out there for running automated tests for your website or web application.<\/p>\n\n\n\n