Skip to content
Testsigma DOCS

Atto AI Coworker

Integrating GitHub with Testsigma


You can integrate GitHub with Testsigma to automatically generate test cases using Atto when a pull request (PR) is raised. This integration uses GitHub Webhooks and a fine-grained Personal Access Token (PAT) to connect your GitHub repository with Testsigma securely. This article discusses the steps to configure the integration & attaching the PR template in GitHub.


Prerequisites

  • Before you begin, ensure you have admin access to your GitHub organization.

  1. Navigate to Settings > Integrations.

  2. Enable toggle on Github widget.


  1. Go to GitHub, select an organization, and click View organization. View Org

  2. In the top navigation bar, click Settings. Settings

  3. In the left navigation pane, under Code, planning, and automation, click Webhooks. Webhooks

  4. On the Webhooks page, click Add webhook. Add Webhook

  5. On the Add webhook page, do the following:

    • In the Payload URL field, enter the Webhook URL.
    • For Content type, select application/json.
    • In the Secret field, enter the Webhook Secret.
    • Under Which events would you like to trigger this webhook?, select Let me select individual events.
    • From the list of available events, select Pull requests.

    Add Webhook page

  1. Select Add webhook to save the configuration. Add Webhook

Step 2: Generate PAT and Owner Details from GitHub

Section titled “Step 2: Generate PAT and Owner Details from GitHub”
  1. Go to GitHub, and click your profile picture in the top-right corner. Profile

  2. In the profile menu, click Settings. Profile Settings

  3. In the left navigation pane, scroll down and click Developer settings. Dev Settings

  4. Under Developer settings, click Personal access tokens, and then select Fine-grained tokens. Fine-grained tokens

  5. Click Generate new token. Generate new token

  6. On the New fine-grained personal access token page, configure the following:

    A. In the Token name field, enter a name for the token.

    B. (Optional) In the Description field, enter the token’s purpose.

    C. Under Resource owner, select your organization.

    D. Under Expiration, choose the desired validity period.

    E. Under Repository access, select one of the following options:

    • Public repositories: to grant access only to public repositories.
    • All repositories: to grant access to all current and future repositories.

    F. Under Permissions, configure the required repository & organization permissions.

    New Token Details

  7. Click Generate token. Generate Token

  8. In the New personal access token dialog, click Generate token. Generate Token

  9. Click Copy and securely store the generated token. Copy Token

  10. Enter the generated Personal Access Token and Resource Owner, click Save & Enable. Save