TestMtg, 2008-06-12
Jump to navigation
Jump to search
QA Meeting 2008-06-12
Dicussed:
- How to get the new QA team up to speed on things that they don't know about yet
- Decide who/what/how the team will be testing for the upcoming August release
- Community testing
- Training - Getting new volunteers/interns/employees up to speed in a technical sense
- Ensuring knowledge isn't lost when interns/volunteers change
- More interns/temps?
- Defined release criteria.
- Process? (OLPC-3)
- Release notes w/ build and firmware (for consistency in testing)
- Bugs fixed + features added
- Release manager moves bugfixes and features to QA (test) stream
- Trac
- Who is responsible for closing bugs?
- Workflow
- QA closes bugs, devs resolved them.
- Test Environment
- Alpha test (real use cases)
- Home
- School
- Specific AP(s)
- 100 laptop testbed
- Alpha test (real use cases)
- Background tasks for QA for when there isn't a specific task needing to be finished at the moment
- Test 8.1.1 thoroughly
- (Create) test cases
- Smoketests on new builds
- Test case management (possibly done on Trac?)
- Wiki links -- so people new to testing can get themselves up to speed quickly, and without large amounts of one-to-one help.