Confirmed users
6,361
edits
QA/Firefox3/TestPlan/PostMortem: Difference between revisions
m
→Things to improve on
| Line 35: | Line 35: | ||
* Keep the PRD up to date! An outdated PRD for certain sections, kept QA from knowing what new features were landing and obscuring out testplans. [tchung] | * Keep the PRD up to date! An outdated PRD for certain sections, kept QA from knowing what new features were landing and obscuring out testplans. [tchung] | ||
** Also, having a better ETA on dates when these features were going to land would help QA know when to expect them in builds [tchung] | ** Also, having a better ETA on dates when these features were going to land would help QA know when to expect them in builds [tchung] | ||
* more communication and updates across the board (eg. graphical changes) | |||
* status meetings has details, but a dashboard or quick status would be easier to take in. | |||
* Flag major changes for the week so QA knows ahead of time. | |||
* Status meetings were inconsistent (some developers were there every week, but others were not avaliable for update status) | |||
* earlier accessibility UI reviews in the process (awesome bar had huge adjustments late in the game) | |||
* Include QA into more review discussions | |||
* Don't jam so many changes into a release (web changes, animated favicon -- broke release) | |||
* More automation for BFT's | |||