Hi All,
Overall the plan looks good. During this phase it makes sense to manage the overall testing manually, and to cultivate tools that make this testing easier as needs are identified. The general test goals (catalog discoverability, schema validity, completeness, etc) seem reasonable.
My main suggestion is that implementation specific bugs/issues discovered during testing shouldn't be logged in the main ioos_tech Google Code issue tracker. Tracking issues for multiple implementations along with continuing IOOS standard discussions could clutter up the tracker quickly. Instead, I think each implementation lead should identify where issues should be logged.
Best,
Shane