GitHub is one of the most popular community among software developers. It helps you with version control by providing a code hosting platform for all. From open source to business, one can share their codes, discover new ideas and discuss about roadblocks, all in order to deliver a better software. GitHub also serves as a project management tool. It allows a team to collaborate from all around the globe.
The LambdaTest GitHub Integration allows you to create a card directly in your repository from LambdaTest platform. Push an issue to your respective repository anytime, even in the middle of your test session. The fields populated by you when marking as bug through LambdaTest are displayed as information on the bug in GitHub repository for that testing instance.
GitHub Integration with LambdaTest, like all of our other integrations to 3rd party applications, is available for freemium as well as premium plan.
Step 1: Login to your LambdaTest account. You would need to have Admin or User level access to see and install integrations.
Step 2: Select ‘Integration’ from the left navigation menu bar. This will guide you to a screen where you will find a list of 3rd party applications, available to integrate with your LambdaTest account.
Step 3: Click on ‘ADD’ under the block that says ‘Github’.
Step 4: Once you click on install, you’ll be redirected to a screen. There would 2 options available for you to choose in order to authenticate GitHub.
Select the radio button on ‘Via OAuth’ and hit ‘Next’.
You will be redirected to GitHub login page where you need to provide your login credentials.
The purpose of logging in is to bypass the authentication that is applied when two different applications interact using their respective APIs. GitHub APIs uses OAuth 2.0’s authorization code grant flow for generating access tokens on user’s behalf.
Access tokens are strings with authorization key required to access an API. They are issued to the client server and are usually opaque. They are used for requesting access to protected, user-specific resources. Access tokens are vital from a security point of view & can be generated in different formats, depending upon security requirements specified on the resource server.
That’s it! Go to Integrations again and you will be able to notice a green tick indicating that GitHub is successfully installed. You can now experience bug logging in a fly from any of your running test session in LambdaTest to your repository directly by a single click.
Select the radio button on ‘Using Personal Access Token’ and hit ‘Next’. You will be redirected to GitHub login page. Provide your login credentials to access your account. If you are already logged in then you will be redirected to your account directly.
Once, you are logged in. Go to ‘Settings’ on the top-right corner.
Hit the ‘Developer Setting’ option on the bottom left.
Go to “Personal access tokens” button & hit “Generate new token”.
In scenarios where OAuth is excessively utilized, Personal Access Tokens comes to aid in accessing the API. While generating a token, make sure you provide a description that is easy to remember, as your Personal Access Token will be derived from it. Treat this token just as you would treat your own password! Access tokens are strings with authorization key required to access an API. They are issued to the client server and are usually opaque. They are used for requesting access to protected, user-specific resources. Access tokens are vital from a security point of view & can be generated in different formats, depending upon security requirements specified on the resource server.
Provide a token description, provide one that is easy for you to remember! Select the checkboxes for ‘repo’ & ‘user’ as scopes. These scopes will define the access to authenticate API over Basic OAuth for their respective personal token. After selecting the scopes hit the green button to “Generate token”.
Your personal access token is now ready. Copy the token & store it safely with you, as you will not be able to see this token again. Paste the copied token into LambdaTest GitHub Authentication.
That’s it! Go to Integrations again and you will be able to notice a green tick indicating that GitHub is successfully installed. You can now experience bug logging in a fly from any of your running test session in Lambdatest to your repository directly by a single click.
Step 1: Go for any of the test from the left navigation menu. For demo, we will be taking “Real Time Test” option.
Step 2: Present a URL of the web-app you need to test in the dialog box. After that, select any configuration for browser and operating system of your choice & hit ‘Start’.
Step 3: After the VM is launched and operable. You can perform testing on your web-app for finding bugs. If a bug gets revealed, then you need to click on the Bug icon from the left panel for capturing a screenshot of the same. We have highlighted that option with yellow in the below image.
Step 4: After a screenshot is captured, you can annotate any issue or a task with an in-built image editor. Once you are done highlighting the bug, click on the button that says “Mark as Bug”.
Step 5: After clicking on “Mark as Bug” button a GitHub specific form would open up. Fill the fields as per your requirement.
Step 6: Click on “Create Bug” & observe it being successfully marked through a single click effort. Once you hit the button, you will get prompt messages on top of your Virtual Machine indicating the progress of bug logging. You will get a prompt message in few seconds mentioning “Bug successfully marked” indicating that the bug has been pushed to the desired GitHub repository.
Step 7: Visit your GitHub repository. You will be able to notice the bug logged right away under your recent activity.
Click on the description of bug and you will be redirected to the detail page of the bug. You will find all the data that you provided through LambdaTest already presented in the bug. LambdaTest automatically includes test environment details and related screenshots in the GitHub repository as attachments.
You can work with one integration at a time. So if you would want to integrate to some 3rd party application of the similar type, other than the GitHub then you would have to remove your present integration. Here is how you can do it.
Step 1: Login to your LambdaTest account.
Step 2: Select ‘Settings’ from the left navigation menu bar & click on ‘Integrations’. This will guide you to the same screen from where you initiated GitHub installation. You will also find other 3rd party applications, available to integrate with your LambdaTest account.
Step 3: To remove the GitHub integration, click on ‘REMOVE’. You can find the Remove button right under the GitHub block which is highlighted with a green tick.
That was all you need to know for LambdaTest + GitHub Integration. Increase your productivity with our integrations. If you still have any questions for us, please feel free to let us know. Our experts are always available on available on chat to help you out with any roadblock regarding our product. Happy testing!