QA TOUCH + GITHUB
Keep GitHub issues and Actions runs inside QA Touch
Connect your GitHub account once. Send bugs to a repository’s Issues tab, and review GitHub Actions workflow runs without leaving QA Touch.
Testers find the bug. GitHub holds the code. Both stay in view.
The integration links your QA Touch project to a GitHub repository, so bugs reach the place developers work and pipeline results show up where testers report.
-
Problem: Bugs found in testing are retyped into GitHub Issues.
With the integration: Bugs logged in QA Touch are sent to the repository’s Issues tab.
-
Problem: Checking a pipeline means leaving QA Touch for GitHub.
With the integration: Workflow runs and their status are listed inside the project.
-
Problem: A failed run doesn’t tell the tester which code it came from.
With the integration: Run details show the branch, commit SHA, commit message and who triggered it.
Repository
Illustrative sample data. Names and statuses are examples.
What the integration does
Five capabilities from QA Touch’s GitHub and GitHub Actions documentation.
Connect with an API key
An administrator opens Integration Settings, clicks GitHub, enters the GitHub API key and clicks Connect. That one connection serves both bugs and Actions.
Bugs sent to GitHub Issues
Once the repository is mapped to the project, bugs created in QA Touch are posted to that repository’s Issues tab.
GitHub issues in your project
Open Integration Issues in a project to see the repository’s GitHub issues without switching tabs.
Actions workflows and runs
Browse a project’s workflows and their runs. The workflow’s status, such as Success, appears next to its name.
Run details and actions
Four tabs: Run details, Workflow file, Jobs and Annotations. Open the run in GitHub, or rerun all jobs where supported.
From API key to a workflow run in QA Touch
Step through the flow. The screens are schematic, drawn from the paths and labels in QA Touch’s guides.
GitHub developer settings
Create the key in GitHub
QA Touch's 2019 GitHub blog creates a personal access token with the repo scope. The Actions guide only says "GitHub API Key".
QA Touch Administrator → Integration Settings
Connect from Integration Settings
Click GitHub, enter the API key in the overlay, then click Connect to authenticate.
QA Touch project integration
Map the repository to a project
After a successful connection, choose the GitHub repository for the project, and the Actions workflow you want to follow.
QA Touch project → Integration Issues → GitHub Issues
Log bugs, see issues
Bugs created in QA Touch are sent to the repository's Issues tab. The issues list in the project shows what is in GitHub.
QA Touch Integration Issues → GitHub Actions → workflow → run
Open a run and read its details
Pick a workflow, then a run. Use the Run details, Workflow file, Jobs and Annotations tabs, then open it in GitHub or rerun all jobs if supported.
Illustrative sample data. Names, SHAs and values are examples.
What changes for your QA team
Fewer tabs, fewer handoffs, and more context on every failure.
No double entry for bugs
A bug logged once in QA Touch reaches the repository, so testers don’t retype it in GitHub.
Bugs live where developers work
Developers see the bug in the repository’s Issues tab, next to the code it concerns.
Pipeline context on hand
Branch, commit SHA, commit message and the person who triggered the run sit beside the result.
Quicker follow-up on failed runs
Open the run in GitHub or rerun all jobs, where supported, after a temporary failure or a fix.
Who uses it, and for what
Choose a role to see a scenario the integration supports.
The team ships from GitHub
You want QA Touch projects tied to the right repositories.
What they do
- Open Administrator, Integration Settings, and click GitHub.
- Enter the API key and click Connect.
- Choose the repository and workflow for each project.
Result: the project can send bugs and show Actions runs.
You found a bug during a test run
The developer works in GitHub, not QA Touch.
What they do
- Log the bug in QA Touch as usual.
- Let the integration send it to the repository's Issues tab.
- Check the GitHub Issues list in the project.
Result: the bug is where the developer will see it.
A tester reported a bug
You want it in the repository you already work from.
What they do
- Find the issue on the repository's Issues tab.
- Fix it and push your change.
- Let the tester check the workflow run in QA Touch.
Result: the tester sees your branch and commit with the run.
Checking a build before sign-off
You need to know whether the latest workflow run passed.
What they do
- Open Integration Issues, then GitHub Actions.
- Pick the workflow and its latest run.
- Read the status, jobs and annotations, and rerun all jobs if supported.
Result: the build status is checked without leaving QA Touch.
Set it up in four parts
These steps follow QA Touch’s GitHub Actions guide and its GitHub integration blog.
Before you start
- A GitHub API key.
- Access to Administrator, Integration Settings in QA Touch.
- A QA Touch project, and a GitHub repository with an Actions workflow.
The Actions guide doesn’t say which token scopes the key needs, or how often run data is refreshed. The blog is from 2019 and mentions a repo scope, so confirm against GitHub’s current token screens. Where the two differ, this page follows the newer Actions guide.
- In GitHub, open your personal settings, then developer settings, then personal access tokens.
- Click Generate new token and add a description.
- The blog selects the
reposcope. Submit, and keep the token to enter in QA Touch.
- In QA Touch, go to Administrator, then Integration Settings.
- Click GitHub.
- Enter your GitHub API Key in the overlay and click Connect.
- After a successful connection, configure the GitHub repository and Actions workflow.
- The blog maps the repository from Projects, then Integration, by selecting it and submitting.
- For issues: open the project, then Integration Issues, then GitHub Issues.
- For pipelines: open Integration Issues, then GitHub Actions, pick a workflow and click a run.
- Use the Run details, Workflow file, Jobs and Annotations tabs.
Connected? See what you can do from a run.
Questions about the GitHub integration
Answers are based on QA Touch’s GitHub Actions guide and GitHub integration blog.
What does the QA Touch GitHub integration do?
It connects your GitHub account to QA Touch. Bugs logged in QA Touch are sent to a repository’s Issues tab, and GitHub Actions workflow runs can be reviewed inside the project.
What do I need to connect GitHub?
A GitHub API key and access to Administrator, Integration Settings in QA Touch. Click GitHub, enter the key and click Connect.
Which permissions does the key need?
The Actions guide doesn’t say. The 2019 blog creates a personal access token with the repo scope. Check GitHub’s current token options before you create one.
How do bugs get to GitHub?
After the integration is connected and the repository is mapped to the project, bugs created in QA Touch are sent to the repository’s Issues tab.
What can I see for a workflow run?
The workflow, run number and attempt, event, branch, commit SHA, who triggered it, duration, start and update times, workflow file, commit message, number of jobs and annotations. The status shows next to the workflow name.
Can I rerun a workflow from QA Touch?
You can click Rerun all jobs if it’s supported for that run, or Open run to go to GitHub. The option may not appear for every run.
Do changes sync back, and how fresh is the run data?
The 2019 blog says issues can be added or edited from the project’s GitHub Issues view and the changes are reflected in GitHub. The Actions guide doesn’t describe how often run data refreshes.
Connect GitHub to QA Touch
Add your API key, choose the repository, and see bugs and workflow runs side by side.