How to use GitHub Bug Reporting while Testing
By Vivek Mannotra, Community Contributor - August 30, 2022
GitHub is a web-based hosting service for software development projects that use the Git version control system. It is among the most popular code versioning, storage, and collaboration platform out there. Having a bug tracking system with GitHub is an easy-to-implement yet powerful way of managing issues related to a code project.
This guide will walk you through the steps you need to follow to set up a GitHub bug reporting workflow with BrowserStack cloud testing.
Evolution of GitHub Issue Tracker
Github was launched in 2008, so it is among the earlier players in the market for source code versioning and repository management. In 2018 Github was acquired by Microsoft. GitHub offers both paid plans for private repositories and free accounts for open-source projects.
Github has evolved in recent years to add more features and functionality to the platform and become a CI/CD integration and automation solutions provider. For bug reporting, Github already has a built-in issues section which can be used to log issues linked to a particular repository.
We will be using this section to create bug reports directly from within the BrowserStack cloud testing environment.
Note: Check out the range of Integrations with BrowserStack including Github.
Integrating with BrowserStack Account
To get started, you can login to an existing account or signup to create a new BrowserStack account. Once you log in to the dashboard you can go to the integrations section there you will find an option to connect GitHub.
When you click on connect under the Github section, a pop-up window will launch asking you to sign into your Github account and provide permissions.
After entering your credentials and allowing access through permissions, the pop-up window will close, and you will see a success message on the integrations page.
You have now successfully connected your GitHub account, and you can now proceed with testing login issues.
Create a Bug Report for GitHub
After starting the session, you can perform a test activity on the device. When you find an issue that qualifies as a bug for your application, you can capture it by clicking on the ‘Report on Github’ button.
Clicking on the report on the GitHub button will launch an overlay window. This window contains a screenshot of the device, pen, and marking tools to mark and explain the issue visually.
On the left-hand side of the overlay, you get input fields to set the name, related repository and other information to be logged with the issue. You can also click on more fields to add extra variables to the issue.
Here it is important to ensure that the bug being reported should be captured with all relevant section information and the appropriate context such that other members of the team can understand the severity and relevance of the issue. Once you have entered all the relevant information, you can click on the create button to complete the bug creation process.
Also Read: How to write an Effective Bug Report
Clicking on create will close the overlay window and take you back to the device Session where a green banner indicates successful logging of the issue; if there is any error during the process you will get a red banner as a failure message.
Just like this, the App Live section also provides similar functionality with a similar button which is located on the second toolbar at the top of the page.
Review Issues on GitHub
After successfully creating the integration and GitHub issue tracking pipeline, all your reported issues should be accessible in the issues section of the relevant repository on GitHub.
The issue tracking feature on GitHub is a powerful way of managing defects. You get the ability to label, filter, and manage issues and progress in one place. It also allows for efficient collaboration.
Clicking on an individual issue will take you to the details page where you can find all the information logged with the issue and the screenshot of the session.
With this, you have successfully completed setting up the bug reporting workflow on Github. Because it is tightly integrated with BrowserStack’s cloud suite, it helps you streamline the testing and development part of the bug-fixing process.
In case, you are looking for official documentation of BrowserStack, visit here.
With this integration, you not only have the ability to log defects for specific code projects, but you can also update issues with further rounds of testing as the integration provides the feature to select existing issues and add updates to them.
When you update existing issues, you get a message.
Any updates you are making to existing issues through the integration, you can see the details again on the issues detail page through Github.
All new updates to an issue will be marked as an additional comment with the relevant screenshot attached so that the thread shows the complete list of entries for a particular bug.
This setup can be used to test mobile and desktop applications in any combination, so it has a wide range of applicability for several real-world tech scenarios.
Benefits of GitHub Bug Tracking
There are many approaches to establishing a bug tracking setup. But doing it through BrowserStack + Github provides a few advantages:
- Setting up your testing infrastructure on BrowserStack cloud suite allows you to access a wide range of realistic test environments and scale as you need.
- Github offers modern features like Github Actions for CI/CD and Post-processing on Code projects, which opens up new ways of extending your development setup and making it more powerful.
- Since Github is a platform that is already used for collaboration amongst developers, having the bug reports over there means that the relevant developers can be taken into the loop and assigned directly.
- BrowserStack’s test infrastructure streamlines your testing efforts on one platform, which has powerful integration and collaboration capabilities.
With BrowserStack Live for Teams, your users can test from anywhere and are ideal for remote testers because it fosters collaborations through integrations like GitHub, Slack, Jira, and Trello. Create sub-teams, customize dashboard views, and allocate parallel threads to teams based on their testing needs.
With project management tools such as GitHub, testers can report bugs, track issues, and keep track of their entire bug lifecycle.