TestCollab lets you create new Github issues from inside TestCollab!

Before proceeding- Make sure you have enabled defect management and connected your issue manager

Once the configuration is done , while running a test case, the tester will get option to mark it as failed and also report a defect.

When you click on report bug icon on run panel, you will see a preview of bug to be posted in Github, if needed you can modify the issue details before it is posted in Github.

Formatting the content of defect being reported

Github accepts text in markdown format as value for relevant fields, if you want to apply formatting options to text fields then you may please refer this article.

Link existing Github issues with failed test case

If you want, you can also link an existing Github issue with test case as defect instead of creating a new one.

Please note that you have to enter the id of the issue that is already present in Github repository selected while configuring defects management settings, otherwise you may get an error.

Who will be considered as reporter for the issue?

Scenario 1: Tests are being run by the administrator who has configured the defects management for project:

The issues would be shown to have been reported by the the user whose credentials were used to configure defects management settings in TestCollab project.

Scenario 2: Tests are being run by a user other than the administrator who has configured defects management for project

  • Scenario 2.1 : The tester has connected his/her own defects manager account with TestCollab profile

    The issues in defects manager app would be shown to have been reported by the user whose credentials have been used to link defects manager app account with current user's TestCollab user profile.

  • Scenario 2.2 : The tester has not connected his/her own defects manager account with TestCollab profile

    In this case all the issues would be shown to have been reported by the user whose credentials were used by administrator while configuring defects management for the project.

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, because sometimes change in Github profile may invalidate the connection.

Before reporting a defect

The user who is getting an option to report a bug can also check the status and validity of access token linked on defects settings page for current project, this is done by hovering the mouse over the "Fail and report bug" button on test case run page.

Here are the various status :

Fail and report bug

The user has linked his account and the access token is still valid so a defect can be reported.

User not linked

User has not linked his/her account on defects settings page, in this case default account will be used to report the defect.

User does not have access to the requested resource

User may or may not have linked his/her account on defects settings page, but the credentials are no more valid and they need to disconnect and reconnect their Github account.

Did this answer your question?