NWAM West: 8:30AM MPK/11:30AM BUR/4:30PM DUB
Attendees: Darren, Steff, Karen, Victor, Alan, Michael, Anurag, Renee
1. Phase 1 status
- Alan, Anurag, Michael, and Renee are wrapping up existing dev tasks
and rolling in new tasks from last month's meetings (many of which are
already complete); will have new dev complete date end of this week.
- GUI dev moving along; Darren estimates about 2 more weeks.
- Design review: it's been a while since we've had a formal one; need
to figure out what's needed.
2. Menlo Park week: February 2 - 6
- Victor has conference rooms reserved
- Will plan on a time when we can all gather, though it's unlikely to
be at the regular west meeting time (8:30 AM in Menlo Park)!
3. Doc status
- Steff mostly working on crossbow; planning to review latest GUI spec.
4. Equipment
- Victor will be placing an order this week; let him know if you need
anything (this is small stuff, not capital). We already have a request
in for some wireless gear.
NWAM East: 5:00PM MPK/9:00AM BJS
Attendees: Karen, Victor, Eric, John, Lizhong, Renee
1. Test development status
- We need updated end dates for the schedule, so we can better gauge
where we are.
2. Parallel test and feature development
The process has to be more iterative than we'd sometimes like: the test
developers come up with good questions while doing their development,
which lead to changes/clarifications in the feature code and design, which
then forces changes to the tests. Though this isn't always optimal, the
feedback loop does help improve the product, and the alternative of
completing the feature development before beginning test dev isn't feasible.
3. Man page update
Renee updated the nwamcfg draft man page yesterday to reflect the changes
we've been discussing in the past couple weeks.
4. Test priorities
John posed a question about relative priority of different parts of test
effort; the automated tests are good to validate the code, and for future
regression testing. However, past experience with phase 0 and 0.5 point
to the importance of manual testing (how nwam responds with different
hardware, different APs, on reboot, on restart, etc.). Are there things
we can do to improve/better prepare for that aspect of our testing?
John will think about this and follow up over e-mail.
