In this article we will discuss the process of integration with Github as defects management tool. With this implemented, a tester can automatically report issues in Github, when a test case fails while it is being run.

Please note that integration with Github is a Premium feature.

The defects settings are done by administrator(s) of the company. While working on a project, you start by navigating to "Defects" page accessible through "Settings" menu. The first option is to enable or disable the defects management for current project.

After enabling defects management, Github can be selected as defects manager. On selection. Then the administrator needs to connect his/her Github account that will be used for integration, for this, one needs to "Sign-in to Github"

You would then be shown details of the developer app that TestCollab uses to provide integration services with Github, so that you can read and understand them and then authorize the app to perform the operations listed.

Once you authorize the application you can then configure the settings.

This includes providing information related to

  • Repository - the Github repository where the issues will be reported in an event of test case failure

  • Milestone

  • Labels

  • Assignee(s)

Save the settings and test the connection, please note that this would create a test issue in your selected Github project so that you can verify the settings.

Connecting other user's Github accounts

Let us now see how a user, other than the administrator (who has configured defects management) can link his/her Github account to be identified as an issue reporter.

Navigating to defects management settings page, would let the user connect (or disconnect) his/her Github account (see below)

Once user has linked Github account, he would be treated as reporter for the issues reported by him while running test cases.

Reporting defect

To know about how tester can report defect at the time of running a test case if it fails, please refer this article.

Note: If you encounter an error that is not specific to the defect being reported then please consider checking the project specific defects management settings to see if the connection you configured is still valid, as sometimes change in Github profile may invalidate the connection.

Did this answer your question?