Just for more information to throw in the mix: http://www.gnome.org/projects/outreach/a11y/tasks/testing/.
We currently have one person interested in this task (Nags from LDTP), but my fear is that this task will never really get of the ground because the testing space is so crowded and the politics are too thick to really handle this at the GNOME level. Instead, I think it makes sense for Sun to be bold and make its best choice among the various testing projects available (e.g., LDTP, Dogtail, Strongwind, write-your-own, etc.) and just move forward with it. We might also try to join forces with others that have already made this choice (e.g., RedHat). Will On Jul 10, 2008, at 9:14 AM, Paul Mei wrote: > Brian Cameron ??: >> >> Alfred: >> >>> Just one thing need to be made clear. Could we trust the testing >>> results from other companies or communities? I think GNOME has the >>> similar situation with Firefox/Thunderbird. Solaris shares most code >>> with Linux distros but there are still some differences. >> >> Considering that each company has limited test resources, and that >> some >> aspects of QA testing are very labor intensive (such as accessibility >> testing), I would think that today each company is probably only >> testing a small percentage of the total overall functionality. If >> companies were working more closely together, it might be possible to >> ensure that the work is divided up so that a larger overall percentage >> of GNOME gets tested for each release. Some testing, even if on a >> different operating system, is better than no testing. >> >> Also, some aspects of testing could be shared even if every company >> did their own separate testing. For example, the work to generate >> (and keep up-to-date) effective test specifications could be something >> that companies could better share. This way testing across different >> organizations would be more consistent and each organization wouldn't >> be re-inventing the same wheels. >> > Yes. I agree if we can have way to do it. Also the automation testing > is > one important part for sharing and collaboration across different > organization. > >>> If a Linux distro releases a test report with GO, do we still need to >>> do the test again on Solaris? >> >> It would probably make sense to address this on a case-by-case basis. >> Some applications are more critical (or more likely to have distro >> specific issues) than others. Each distro probably would want to >> do their own testing to make sure that mission critical programs >> are working properly. Other programs (for example the GNOME calculator >> or hex editor) might be of lower priority, and testing such programs >> could perhaps be rotated so a different distro would test the >> application for each GNOME release. >> >> I am just trying to suggest that there are likely opportunities >> for different organizations involved with GNOME to share QA testing >> work, and making QA testing efforts more effective overall for >> GNOME. Obviously working out the details would require some >> discussion and coordination across the different organizations to make >> any sort of program workable. >> >> At the moment, I do not think the GNOME community has any real >> infrastructure for sharing this sort of work, so the first step would >> probably be to start a discussion with the GNOME community and see if >> other companies have an interest in working together in this way. >> > I'd like to see the GNOME community can have the infrastructure to > share > work. Actually we also want to communicate with people on GNOME > community about testing, maybe we can refer to what Mozilla has done. > > Thanks, > Paul. >> Brian > > _______________________________________________ > desktop-discuss mailing list > desktop-discuss at opensolaris.org -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/enriched Size: 3899 bytes Desc: not available URL: <http://mail.opensolaris.org/pipermail/desktop-discuss/attachments/20080710/422858ab/attachment.bin>
