{ "componentChunkName": "component---src-templates-page-jsx", "path": "/docs/test-management/qi-home/context-mapping/map-github/", "result": {"data":{"markdownRemark":{"html":"

Map GitHub pull requests to sprints or Ad-Hoc sessions so Atto can generate or update test cases based on code changes.

\n

For GitHub App setup on the developer side, see Connect GitHub.

\n
\n

When your developers open or update pull requests in GitHub, Atto detects them and shows them in the Unmapped Context view in QI Home. Each pull request appears with an AI-generated suggestion for which module and sprint it belongs to. You review the suggestion and map it with a few clicks.

\n

Once mapped, Atto generates new test cases or updates existing ones based on the code changes in that pull request.

\n
\n
\n

Prerequisites

\n

Before you begin, ensure that:

\n\n
\n
\n

View Unmapped GitHub Context

\n
    \n
  1. From the left navigation, go to QI Home.
    2. \n
  2. In the left sidebar, click View next to Unmapped Context.
    3. \n
  3. The Unmapped Context tab opens. GitHub PRs are identified by the GitHub PR badge.
    4. \n
\n

Each GitHub PR entry shows:

\n\n
\n

Map a GitHub PR to a Sprint

\n
    \n
  1. On the PR you want to map, click Map to Module.
    2. \n
  2. In the Map to Module dialog, select the Project from the dropdown.
    3. \n
  3. Under Map to, select Sprint.
    4. \n
  4. Select the Sprint you want to map this PR to.
    5. \n
  5. Select the Stories within the sprint that this PR relates to.
    6. \n
  6. Review the What happens next message: \"This PR will be mapped to the selected stories in the sprint and test cases will be auto-generated by Atto.\"
    7. \n
  7. Click Map.
    8. \n
\n

Atto triggers test generation for the selected sprint. New test cases are generated or existing ones are updated based on the PR's changes.

\n
\n

Map a GitHub PR to an Ad-Hoc Session

\n
    \n
  1. On the PR you want to map, click Map to Module.
    2. \n
  2. In the Map to Module dialog, select the Project.
    3. \n
  3. Under Map to, select Adhoc.
    4. \n
  4. Under Existing Adhoc Session, select the session you want to map to, or select + Create New Adhoc Session to start a new one.
    5. \n
  5. Click Map.
    6. \n
\n
\n

Map Multiple PRs at Once

\n
    \n
  1. Select the checkboxes next to the PRs you want to map.
    2. \n
  2. A bottom action bar appears showing the number of PRs selected and a Map to Module button.
    3. \n
  3. Click Map to Module.
    4. \n
  4. In the Map to Module dialog, the selected PRs are listed at the top. Configure the mapping settings and click Map.
    5. \n
\n
\n

Dismiss a GitHub PR

\n

If a PR is not relevant to your test coverage, click Dismiss. The PR is removed from the Unmapped Context list.

\n
NOTE:

Dismissed context does not contribute to coverage. You cannot recover dismissed context from this view.

\n
\n

View Mapped Context

\n
    \n
  1. In the Unmapped Context view, click the Mapped Context tab.
    2. \n
\n

The Mapped Context tab shows:

\n\n

Each mapped context entry shows the sprint and story it was mapped to, and the number of test cases generated.

\n
","frontmatter":{"title":"Map GitHub Context","page_title":"Map GitHub Context","metadesc":"Map GitHub pull requests to sprints or Ad-Hoc sessions so Atto can generate or update test cases based on code changes.","noindex":false,"contextual_links":[{"type":"section","name":"Contents","url":null},{"type":"link","name":"Prerequisites","url":"#prerequisites"},{"type":"link","name":"View Unmapped GitHub Context","url":"#view-unmapped-github-context"},{"type":"link","name":"Map a GitHub PR to a Sprint","url":"#map-a-github-pr-to-a-sprint"},{"type":"link","name":"Map a GitHub PR to an Ad-Hoc Session","url":"#map-a-github-pr-to-an-ad-hoc-session"},{"type":"link","name":"Map Multiple PRs at Once","url":"#map-multiple-prs-at-once"},{"type":"link","name":"View Mapped Context","url":"#view-mapped-context"}]},"fields":{"slug":"/docs/test-management/qi-home/context-mapping/map-github/"}}},"pageContext":{"slug":"/docs/test-management/qi-home/context-mapping/map-github/","prev":{"fields":{"slug":"/docs/test-management/qi-home/context-mapping/connect-codex/"},"frontmatter":{"title":"Connect Codex","metadesc":"How to install and connect the Arcus plugin for Codex so your coding context is captured and sent to QI Home for test generation.","canonical":null,"keywords":null,"social_share_summary":null,"social_share_desc":null,"social_share_image":null,"noindex":false}},"next":{"fields":{"slug":"/docs/test-management/qi-home/context-mapping/map-developer-context/"},"frontmatter":{"title":"Map Developer Context","metadesc":"Map Claude Code, Cursor, GitHub Copilot, and Codex context to sprints or Ad-Hoc sessions so Atto can generate or update test cases based on development activity.","canonical":null,"keywords":null,"social_share_summary":null,"social_share_desc":null,"social_share_image":null,"noindex":false}}}}, "staticQueryHashes": ["2855385900","63159454"]}