AdaptUI Research Study
Participant Task Protocol — Pilot Study Evaluation
Study Overview
Thank you for participating in the AdaptUI framework pilot study.
This study evaluates how developers interact with GitHub while performing
realistic software engineering workflows under different interface conditions.
Participant Instructions
- Complete all tasks in the provided order unless instructed otherwise.
- Work at your normal pace. Accuracy is more important than speed.
- Do not use external websites, AI assistants, or search engines.
- If you encounter a technical issue, notify the facilitator.
-
During the study, please verbalize your thoughts and decisions whenever possible
(Think-Aloud Protocol).
Study Sessions
| Session |
Duration |
Included Tasks |
| Session 1 — Familiarization |
20 Minutes |
A1, A2 |
| Session 2 — Core Study |
35 Minutes |
A3, A4, B1, B2 |
| Session 3 — Advanced Study |
30 Minutes |
B3, B4, C1 |
Session 1 — Familiarization
Task A1 — Repository Orientation
You have just joined a new development team.
Your goal is to understand the current state of the repository.
-
Navigate to the repository:
adapt_ui_probe_task_manager
AdaptUI Pilot Repository
- Identify the primary programming language used.
- Identify the date of the most recent commit.
- Determine how many open issues currently exist.
Please record your answers on the provided response sheet.
Task A2 — Issue Investigation
A bug related to authentication behavior has been reported.
-
Locate the issue titled:
"Login page does not redirect after timeout"
- Identify the user assigned to the issue.
- Identify all labels attached to the issue.
- Determine how many comments currently exist on the issue.
Session 2 — Core Operations
Task A3 — Pull Request Review (Read Only)
A new feature branch has been submitted for review.
- Open Pull Request
#15.
- Determine what problem or feature this PR addresses.
- Identify the total number of files changed.
Important: Do NOT merge or close the pull request.
Task A4 — Create an Issue
You discovered a UI issue during testing.
-
Create a new issue titled:
"Button alignment broken on mobile"
- Add the label
bug.
- Assign the issue to yourself.
- Submit the issue successfully.
Task B1 — Code Review
A teammate has requested a formal code review.
- Navigate to Pull Request
#14.
- Open the Files changed tab.
-
Add an inline comment on any changed line:
"Please add a unit test for this function."
-
Submit your review using:
Comment
Do NOT select "Approve" or "Request changes".
Task B2 — Branch & File Exploration
You need to inspect a feature branch currently under development.
-
Switch to the branch:
feature/user-auth
- Locate the file
src/services/UserService.js.
-
Identify the name of the first function defined in the file.
Record your answer on the response sheet.
Session 3 — Advanced Triage & Investigation
Task B3 — Issue Filtering & Triage
The project backlog requires issue organization.
- Navigate to the Issues tab.
-
Filter the list to display only:
- Open issues
- Issues labeled
bug
-
Determine how many issues match the filter criteria.
-
Assign the oldest issue in the filtered list to yourself.
Task B4 — Actions Workflow Investigation
A CI/CD workflow execution recently failed.
- Navigate to the GitHub Actions tab.
- Locate the most recent failed workflow run.
- Identify the name of the failed workflow.
-
Determine which step in the workflow caused the failure.
Task C1 — Git History Investigation
You need to investigate the history of the database configuration setup.
-
Find the commit that first introduced:
config/database.js
- Identify the author of the commit.
- Record the exact commit message.
-
Determine whether the commit was associated with a Pull Request.
Optional Extended Tasks
Task C2 — Multi-Issue Management
- Locate all issues labeled
duplicate.
- There should be exactly 3 matching issues.
-
Before closing each issue, add the comment:
"Closing as duplicate"
- Close each duplicate issue.
Task C3 — Security & Insights
- Navigate to the Security tab.
- Check whether any Dependabot alerts exist.
-
Navigate to:
Insights → Contributors
-
Identify which contributor has the highest number of commits.
Task C4 — Project Board Management
- Navigate to the Projects tab.
-
Locate the card:
Fix login timeout
-
Move the card from:
In Progress
to
Done