...
Goals
- Introductions Introductions
- Test Strategy
- Version 2
- Communication
- QA slack channel daily updates
- Informal questions about processes, tasks, tickets, concerns
- List tickets that have been reviewed with devs for test coverage
- Weekly meetings every Monday
- Tracking time accurately for dev tickets and test case executionCreating a test case cycle
- Adding test cases for dev tickets: Identify missing test coverage, documenting, creating new test cycles
- Test cycles for each sprint: Sprint testing, regressions, bug tracking
- Showcase test cycles
Discussion items
| Time | Item | Who | Notes |
|---|---|---|---|
...
- Add edge cases and defining that QA process to the Test Strategy
- Tracking time accurately
- Communicating when regressions are scheduled (small and big)
- Showcasing regressions
- Agreeing on how to define and implement contract tests (writing contract tests - what is the contract test coverage)
- Build a culture of test driven development
- Push devs to finish before end of sprint
- Open communication (#QA check in everyday), talk about general testing, potential issues, if they haven't started testing tickets, can we review tickets with devs here, questions about process or tasks, questions about scheduling, informal concerns, back channel, list tickets that have been reviewed with devs - how we show the status of this and if it hasn't been done
- Orientation of product, walk through of where to go for documentation, walk through of version 2, other history
Action items