...
How do we feel about information available to test?
- Seth: Not good, accurate information being made available. Right hand/left hand problem. The only thing that knows what the different hands doing is QA (head).
Spent a lot of time
Hannah: Do we have identified information.
CM API - information is technical. passed onto dev. teams. Where should I be looking for info, technical, functional, ui, how changes affects
...
Possible to come up with template
- design documentation
- functional specs
- Jira's: describe what they think is required by testing to verify the changes made.
Assignments was mature.
Cavalier attitude
- Chat replacement. Was a semi nightmare.
- Message Center Split is not complete. Release notes
Who cracks down? Should it be us? Should it be . Peter hopes that creating milestones will help alleviate this. Seth disagrees . .this is just another attempt. We need to have come sort of central coordination. Will attempt web bridge via sakai001.
Question: When did we move away from running a tool for a semester. Reminds Hannah of Mark Nortons requirement of tool status. Seth gives community credit for following the requirement model.
...
Have designated times to test together.
- How can we better buidl
- Need more
...
- information.
Continuing to recommend that there are a lot of bug fixes. Decreases the workflow on implementors, know that they don't need