Coordenar QA e Desenvolvimento no Workflow | GitScrum

Alinhe QA e desenvolvimento para releases mais rápidos e com qualidade. GitScrum rastreia testes, gerencia handoffs e mantém qualidade visível no processo.

4 min de leitura

How to coordinate QA and development workflow?

Coordinate QA and development by creating testing columns in your workflow (Ready for QA, In QA, QA Passed), having QA create test tasks before development starts, including QA in sprint planning, and using labels to track test status. Prevent bottlenecks by limiting work in progress and having developers help with testing.

Development-QA workflow columns

Column	Purpose	WIP Limit
Backlog	Prioritized work	-
In Development	Active coding	5
Ready for QA	Waiting for testing	3
In QA	Actively testing	3
QA Passed	Ready for release	5
Done	Released	-

QA labels

Label	Purpose
qa:ready	Ready for QA
qa:in-progress	Testing in progress
qa:passed	All tests passed
qa:failed	Bugs found
qa:blocked	Testing blocked
test:manual	Manual testing required
test:automated	Automated test exists
regression	Regression issue

Coordinated workflow:

Sprint planning - QA reviews acceptance criteria

Test case creation - QA writes tests during dev

Development complete - Move to Ready for QA

Testing - QA tests, creates bug tasks if needed

Bug fixes - Developer fixes, returns to QA

QA passed - Move to QA Passed

Release - Deploy with confidence

Feature task with QA integration

## Feature: User Export Functionality

### Acceptance Criteria
- [ ] Export users to CSV
- [ ] Export users to JSON
- [ ] Filter by date range
- [ ] Include all user fields

### Development
- [ ] Build export service
- [ ] Add UI components
- [ ] Write unit tests

### QA (to be filled by QA)
Test cases: [Link to test cases]
- [ ] CSV export with 1000+ users
- [ ] JSON format validation
- [ ] Date filter accuracy
- [ ] Permission verification
- [ ] Edge cases tested

### Definition of Done
- [ ] Development complete
- [ ] Unit tests passing
- [ ] QA test cases passed
- [ ] No open bugs

Preventing QA bottlenecks

Problem	Solution
QA column overflows	Lower WIP limit, devs help test
Testing takes too long	Automate regression, focus on new
Bugs found late	QA involved earlier
End-of-sprint crunch	Stagger feature completion
Context switching	QA embedded in team

QA involvement timeline

Sprint Day	QA Activity
Day 1	Review acceptance criteria, write test cases
Day 2-4	Prepare test data, automation
Day 5+	Test completed features as they arrive
Day 8-9	Focus on integration testing
Day 10	Final regression, sign-off