| Table of Contents | ||||
|---|---|---|---|---|
|
...
Day 8:
Day 9:
Day 10:
Testing
Discussion with Grace - April 4
Bugs addressed during the sprint. Leave some space for bug testing during the sprint
...
What will the test cases be used for? (e.g. backlog testing, automated testing, future use)
How can we minimize the amount of work required to write a test case? E.g. focus on developing a specific feature per sprint, so test case writing can start on day 1 - ? Perhaps identify which backlog items will need test cases at the beginning of the sprint, so test case writing can start at the beginning?
QA free from manual testing
Dev’s test each other’s work / test cases
Ad-hoc testing - Grace, Maggie, dev’s, Ewa, PO - anyone who can help
Automated testing - B Unit testing - more like unit testing for the UI - not full UI automated testing
Concern - not to add to many testing activities to dev team
Basic level: - Dev’s only
Writing test cases
Reviewing each other test cases - manually
Executing each other test cases - manually
Still valuable - can start automating in the future
If QA:
First three days, can catch up on testing
Writing test cases
Ad-hoc testing
Review test cases with one of dev team’s members
Executing test cases
Test all tickets within one sprint - if possible
Currently we have 3 dev’s and one QA
Need to keep quality or speed
Other work environments - 1 to 1 dev team - work at writing the user stories from the beginning of sprint
Scope
Time
Quality
Automated Testing
...
2 month release schedule - Release Train
Total: 4 sprints
Sprint 1
Tech debt - some tech debt might need to be tested. But it is safe to do tech debt at the end of the sprint. At minimum, as sanity check might need to happen.
Dev:
60% - New development
...