For the sake of understanding, I will break it down into episodes based on the chronology of how it occurred to me.<\/p>\n\n\n\n

Episode 1-Reporting Time<\/h3>\n\n\n\n

As a hands-on tester, one big problem I faced is the time to report bugs when testing on a mobile phone. Take a screenshot – send it over email – download it on the laptop – again upload to Jira and write the bug report. Every bug I found – I wasted 15 minutes in reporting it and hence it slows down my testing. Also, I don’t want to spend time writing steps to reproduce for things that are obvious.<\/p>\n\n\n\n

As a passionate tester, I wanted to<\/strong><\/p>\n\n\n\n

• find more bugs<\/li>
• improve my test coverage<\/li>
• spend more time thinking and running tests<\/li><\/ul>\n\n\n\n

  That is how Bugasura was born!<\/em><\/p>\n\n\n\n

  Bugasura:<\/strong><\/p>\n\n\n\n

  • Helps speed up testing<\/li>
  • Helps people keep bug reporting away from Whatsapp and akin<\/li>
  • Helps people explain less about their testing<\/li><\/ul>\n\n\n\n

    Episode 2-Reproducibility<\/h3>\n\n\n\n

    Back in 2006, I worked at a company where every time I reported a bug – the dev would get a notification and they would call on my desk phone and say, “Come and reproduce in front of me”<\/p>\n\n\n\n

    As odd as it sounds, every tester in my team faced the same situation and they would go, err, reproduce the bug in front of the dev.<\/p>\n\n\n\n

    Every bug the tester finds – 20 minutes is spent on going, showing, coming back – and getting back into the flow of testing.<\/p>\n\n\n\n

    I asked the developers, “If all we need to do is to show you the bug – why am I wasting time writing bug report?” and that is when some devs shared that not all testers are good at expressing what they did and what they saw and what they think. Sometimes – it might also be a lack of investigation.<\/p>\n\n\n\n

    I setup a protocol with the developers I worked with. If you don’t understand the bug report I write – please give me feedback but please don’t keep saying, “Come and reproduce in front of me”<\/p>\n\n\n\n

    When I was building Bugasura – all those developers and my fellow testers came in my mind. I need to save testers from this menace.<\/p>\n\n\n\n

    With Bugasura – people get the whole flow, tap, scroll, data entered and location of the bug. Don’t reproduce in front of anyone!<\/p>\n\n\n\n

    Episode 3-Visibility<\/h3>\n\n\n\n

    There are two sides of the IT industry<\/p>\n\n\n\n

    Type 1: Has trust deficit on the people it hires,<\/p>\n\n\n\n

    Type 2: Has people who don’t know to translate the trust into visibility.<\/p>\n\n\n\n

    Plenty of people’s time is wasted in the name of reports. I love writing inferences of my observations and not writing what I did, which device I tested on, how long did I test.<\/p>\n\n\n\n

    Bugasura is an automation of the visibility of testing. Bugasura helps in automating reporting – saving time of anyone who tests in an organization so that more time is spent doing test coverage and finding more bugs.<\/p>\n\n\n\n

    Organizations who look to help their testers are adopting Bugasura<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

    <\/span> 2<\/span> minute read<\/span><\/span> For the sake of understanding, I will break it down into episodes based on the chronology of how it occurred to me. Episode 1-Reporting Time As a hands-on tester, one big problem I faced is the time to report bugs when testing on a mobile phone. Take a screenshot – send it over email – download it on the laptop – again upload to Jira and write the bug report. Every bug I found – I wasted 15 minutes in reporting it and hence it slows down my testing. Also, I don’t want to spend time writing steps to reproduce […]<\/p>\n","protected":false},"author":6,"featured_media":2167,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[135],"tags":[26,28,27],"yoast_head":"\n