4 min read • Guide 525 of 877
How to Use GitScrum for QA and Testing Teams?
How to use GitScrum for QA and testing teams?
GitScrum supports QA teams with columns for test planning, execution, and bug tracking. Configure workflow for testing phases, use labels for test types and severity, track defects with priority labels, and document test plans in NoteVault. QA teams using structured PM find 30% more defects before production [Source: QA Industry Report 2024].
QA project setup:
- Create project - QA or Testing team
- Configure columns - Testing workflow
- Add severity labels - Bug classification
- Set WIP limits - Testing capacity
- Create NoteVault docs - Test plans
- Subscribe to columns - Get notified
QA workflow columns
| Column | WIP Limit | Purpose |
|---|---|---|
| To Test | 15 | Queue for testing |
| In Testing | 5 | Active testing |
| Passed | None | Tests passed |
| Failed | 10 | Defects found |
| Fix in Progress | Team size | Dev fixing |
| Verified | 5 | Fix confirmed |
| Closed | None | Complete |
Bug severity labels
| Label | Description | Response |
|---|---|---|
| severity-critical | System down | Immediate |
| severity-major | Major feature broken | High priority |
| severity-minor | Cosmetic/minor | Normal |
| severity-trivial | Minimal impact | Low priority |
Bug tracking workflow
| Stage | Actions |
|---|---|
| Reported | Create task, add details |
| Triage | Assign severity, priority |
| Confirmed | Reproducible |
| In Progress | Dev working |
| Fixed | Dev complete |
| Verified | QA confirmed |
| Closed | Done |
Test type labels
| Label | Test Type |
|---|---|
| test-manual | Manual testing |
| test-automated | Automated tests |
| test-regression | Regression suite |
| test-smoke | Smoke tests |
| test-exploratory | Exploratory testing |
| test-performance | Load/perf tests |
| test-security | Security testing |
| test-a11y | Accessibility |
Test planning in NoteVault
| Document | Content |
|---|---|
| Test Plan | Scope, approach |
| Test Cases | Detailed cases |
| Regression Suite | Regression tests |
| Test Environment | Setup guide |
| Release Checklist | Pre-release tests |
QA-Dev coordination
| Need | GitScrum Solution |
|---|---|
| Ready for test | Column subscriber |
| Bug reports | Failed column |
| Verification | Verified column |
| Communication | Team Standup |
| Status | Board visibility |
Auto-assign for QA
| Column | Auto-Assign |
|---|---|
| To Test | QA team |
| Failed | Original dev |
| Verified | QA lead |
QA metrics tracking
| Metric | How to Track |
|---|---|
| Bugs found | Failed column count |
| Test coverage | Label analysis |
| Verification time | Column cycle time |
| Escape rate | Production bugs |
| Test velocity | Passed throughput |
Bug report template
| Field | Content |
|---|---|
| Title | Clear bug description |
| Severity | Label |
| Steps | Reproduction steps |
| Expected | Expected behavior |
| Actual | Actual behavior |
| Environment | Browser, OS, etc. |
| Evidence | Screenshots, logs |
WIP limits for QA
| Column | Limit | Reason |
|---|---|---|
| In Testing | 5 | Focus on completion |
| Failed | 10 | Visibility |
| Verified | 5 | Keep flow moving |