Como você pode incentivar relatórios de bugs da equipe e dos desenvolvedores

How you can encourage bug reporting from staff and developers

You can't solve a problem until you know it exists. And that's why you need better bug reporting.

relatório de bugs

Did you receive an error? If so, what did the error say?

Better yet, create an internal form that allows users to select drop-down menus or checkboxes. The less a user needs to input, the more likely they are to report the bug.

One thing to consider is that you will need to add clear instructions to help users understand what is expected from bug reports and guide them through the process. This may seem a little harsh, but don't let your programmers write these instructions. Why? Many software engineers fail to communicate their ideas in terms that the end user can understand. Use a middle manager, an experienced developer, or someone adept at translating otherwise complicated concepts into human-readable information.

It's also important to ensure your bug reporting system strikes a balance between easy for end users and informative for developers. If your end users aren't submitting information that actually helps engineers improve their Ruby , Node.js , or cloud project, they might as well not submit bug reports.

Improve lines of communication

The conversation goes both ways. You need end users willing to take on the task of filing useful bug reports, but you also need developers willing to communicate with end users in a helpful way.

When an end user submits an unhelpful bug report (“When I click a button, it crashes!”), if your developers attack the end user (“What can I do with this stupid bug report?”), that just will help discourage the user from filling out another report. Your developers need to understand that end users don't speak their language or understand how the software works behind the scenes. To that end, make sure your developers handle the end of the communication path with a friendly nod and patience.

When a user submits a suboptimal bug report, a developer should follow up with the user and ask questions in a way that is not discouraging or demeaning. Improve this specific line of communication and bug reports will flow much more regularly.

Conclusion

You owe it to your company, your developers, and your team to improve the bug reporting process for the software you use. Even if this software is not developed in-house, these bugs can help third-party developers not only improve the application in question for you, but for everyone.

Bug reporting is a win-win proposition. Take the time to develop a simple, seamless process and your business will run more smoothly and efficiently.

Source: BairesDev

Conteúdo relacionado

Back to blog

Leave a comment

Please note, comments need to be approved before they are published.