Goal of survey: understand strengths and weaknesses of release process to improve for 3.5 release
Survey recipients: development teams, including Malawi UAT, managers
Testing
- Test cases: gather any details about confusion in executing or test steps
- How clear are the test cases and execution steps? Rate 1-5
- Comments
- Demo data: same users across components for different test cases
- Do you know what demo data to use when executing a test case? Rate 1-5
- Comments
- Communication of status: do you know what you're supposed to do for the day? (responsibilities)
- When release testing begins, do you know what you are testing for the day? Rate 1-5
- Did you know what testing phase we were in? RC1, RC2, bug fix, etc
- Comments
- Environments
Bug fixing
- Creating bugs
- Did you use the bug template when creating bugs? Yes or No
- Bug triage
- ???
- Bug fixing
- Are responsibilities and assignments for fixing bugs and testing bug fixes clear? Rate 1-5
- Comments
- Other work, is it clear that teams can work on other things including new features during this time?
Release
- Communication of releasing components
- During the release of 3.4 how clear was the progress of the release to you? Rate 1-5
- Checklist
- How useful was the release checklist during the release process? Rate 1-5