> Something as "simple" as a tracker would work. If you want something > tested, raise a ticket. Developers can look at the ticket to see what > the status of your test request is. Testers can look at the list of open > tickets to see what is ready for testing. Every request has a date and a > log of what has been done. This is how the test groups work in the > software development houses I've worked with. > > Do we use the olpc tracker or the sugarlabs tracker? Starting another > one seems like a bad idea.
If it's testing of Sugar, Sugar Activities, or Sugar on a Stick, http://dev.sugarlabs.org/ is the place to go (set the component to either the Activity you're testing, or to soas). --Mel _______________________________________________ Testing mailing list [email protected] http://lists.laptop.org/listinfo/testing
