From andras.barna at gmail.com Mon Aug 25 03:48:08 2008 From: andras.barna at gmail.com (Andras Barna) Date: Mon, 25 Aug 2008 13:48:08 +0300 Subject: [desktop-testing] please dont use internal URLs Message-ID: <56dc2e760808250348u45f53311oa4fb302df9a4ba6a@mail.gmail.com> hi see subject, * testing/gnome # Latest Gnome 2.24 and Desktop other projects test result points to http://jdsbj.prc/reqe/testreport/vermillion/vermillion96.html * multimedia # Progressive Networks Audio (PNA) points to: http://jdsbjwiki.prc/index.php/Progressive_Networks_Audio_%28PNA%29 in the Plugins which can be purchased from the Fluendo WebStore] there's an extra ] knwn issues: all -- Andy http://blog.sartek.net From Paul.Mei at Sun.COM Tue Aug 26 08:08:14 2008 From: Paul.Mei at Sun.COM (Paul) Date: Tue, 26 Aug 2008 23:08:14 +0800 Subject: [desktop-testing] collect feedback about remote testing requirement for desktop testing Message-ID: <48B41C5E.30509@sun.com> Hi All, We are working for the infrastructure setup for desktop testing. Now I'd like to collect the feedback about remote testing requirement for desktop testing. You know, the testing community in OpenSolaris community has provided some hardwares and one program called "Test Farm", then it can let community user leverage Sun's hardware for Solaris kernel/driver development and testing. For desktop testing, because all of our applications are GUI, the requirement is a little different from that. So I'd like to get your feedback if we need to do something like this way. If I can get enough positive feedback about it, I can discuss with team about how to setup it. The questions can be like this: 1. Do you think it is necessary to provide community user hardwares for desktop application remote testing? 2. If yes, could you please list some reasons? I'd like to set time limit from Aug. 26 to Sep. 1. Please give me your feedback. Thanks, Paul. From andras.barna at gmail.com Tue Aug 26 08:38:18 2008 From: andras.barna at gmail.com (Andras Barna) Date: Tue, 26 Aug 2008 18:38:18 +0300 Subject: [desktop-testing] [desktop-discuss] Announcement for OpenSolaris Desktop testing link and mail alias desktop-testing@opensolaris.org In-Reply-To: <48B287C0.2040200@sun.com> References: <48B287C0.2040200@sun.com> Message-ID: <56dc2e760808260838t1aedcac2r543dda2fad3d42a3@mail.gmail.com> On Mon, Aug 25, 2008 at 1:21 PM, Qi-Bo Paul Mei wrote: > Hi All, > > Thanks for Glynn and all the people's good comments, the proposal for > "Proposal to setup desktop-testing community" has been approved. > > Now I am glad to announce that the OpenSolaris Desktop testing link and > mail alias desktop-testing at opensolairs .org has been created. > > The link about destkop testing is under OpenSolaris desktop community, > you can check the contents from > http://www.opensolaris.org/os/community/desktop/testing/ > > We have published some contents below it, it is still on-going. It is > welcomed to give your comments. i sent a mail to desktop-testing .. > > According to plan, we will update our test result under the link time by > time. And we are working on the evaluation for test management tool, > and update and discuss about the test management tool with desktop > community people soon. After decide to choose one test management tool, > we will setup one external test management tool, it can be used and > accessed by all desktop testing people. Then we will try to make some > policy how to attend and contribute your test cases/test session/test > report for the desktop testing. We hope to setup one consistent testing > environment for Sun employees and community users about desktop testing > in the future. Please stay tune. > > The mail alias desktop-testing at opensolaris.org also has been created, > Sun's desktop testing team are all on it. We will begin to bring in all > desktop testing discussion on it, like the evaluation for test > management tool and future automation work. Please subscribe if you are > interested in the destkop quality and want to contribute for the desktop > quality. > > Cheers, > Paul. > > > > _______________________________________________ > desktop-discuss mailing list > desktop-discuss at opensolaris.org > -- Andy http://blog.sartek.net From William.Walker at Sun.COM Tue Aug 26 09:34:32 2008 From: William.Walker at Sun.COM (Willie Walker) Date: Tue, 26 Aug 2008 12:34:32 -0400 Subject: [desktop-testing] collect feedback about remote testing requirement for desktop testing In-Reply-To: <48B41C5E.30509@sun.com> References: <48B41C5E.30509@sun.com> Message-ID: <48B43098.1050803@sun.com> Hi Paul: I'm not quite sure about what you mean for the infrastructure for desktop testing -- do you mean the hardware or the software infrastructure? For software, the AT-SPI infrastructure is used in a number of testing environments, including LDTP, Dogtail, and Strongwind. We also use it for testing Orca (see http://live.gnome.org/Orca/RegressionTesting). It works well. As testing moves forward, I think it will be important to lay out a plan to test fresh bits as early as possible in order to detect regressions across the board. I've noticed a pattern over the past several releases of JDS/GNOME where testing was still being done on relatively old stuff while the new stuff was regressing. We can definitely do better, and much more can be automated. For hardware, I often just run a vncserver and run all my Orca regression tests within that environment. With that, I don't need to be logged in behind the console. I can also have several tests running at the same time on the same machine without tying up my keyboard/mouse. I can also remotely view the vncserver using the vncviewer application so I can monitor the tests if I want. As such, as long as a machine is capable of running a vncserver, testing works OK. The only 'gotcha' is that the runtime environment is dependent upon the installed machine. As such, different VirtualBox environments can be used to help test different flavors of JDS/GNOME. Will Paul wrote: > Hi All, > > We are working for the infrastructure setup for desktop testing. Now I'd > like to collect the feedback about remote testing requirement for > desktop testing. You know, the testing community in OpenSolaris > community has provided some hardwares and one program called "Test > Farm", then it can let community user leverage Sun's hardware for > Solaris kernel/driver development and testing. For desktop testing, > because all of our applications are GUI, the requirement is a little > different from that. So I'd like to get your feedback if we need to do > something like this way. If I can get enough positive feedback about it, > I can discuss with team about how to setup it. > > The questions can be like this: > 1. Do you think it is necessary to provide community user hardwares for > desktop application remote testing? > 2. If yes, could you please list some reasons? > > I'd like to set time limit from Aug. 26 to Sep. 1. Please give me your > feedback. > > Thanks, > Paul. > _______________________________________________ > desktop-testing mailing list > desktop-testing at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/desktop-testing From James.Walker at Sun.COM Tue Aug 26 10:07:59 2008 From: James.Walker at Sun.COM (Jim Walker) Date: Tue, 26 Aug 2008 11:07:59 -0600 Subject: [desktop-testing] [desktop-discuss] collect feedback about remote testing requirement for desktop testing In-Reply-To: <48B41C5E.30509@sun.com> References: <48B41C5E.30509@sun.com> Message-ID: <48B4386F.6020300@sun.com> Paul wrote: > Hi All, > > We are working for the infrastructure setup for desktop testing. Now I'd > like to collect the feedback about remote testing requirement for > desktop testing. You know, the testing community in OpenSolaris > community has provided some hardwares and one program called "Test > Farm", then it can let community user leverage Sun's hardware for > Solaris kernel/driver development and testing. For desktop testing, > because all of our applications are GUI, the requirement is a little > different from that. So I'd like to get your feedback if we need to do > something like this way. If I can get enough positive feedback about it, > I can discuss with team about how to setup it. > > The questions can be like this: > 1. Do you think it is necessary to provide community user hardwares for > desktop application remote testing? > 2. If yes, could you please list some reasons? Paul, Thanks for putting this question out there. Once you get some specific remote desktop testing requirements, I may be able to allocate some test machines from the test farm for non-Sun developers to use for desktop testing. I assume external users will have a hard time getting access to Sparc machines. Cheers, Jim From Paul.Mei at Sun.COM Fri Aug 29 00:29:35 2008 From: Paul.Mei at Sun.COM (Qi-Bo Paul Mei) Date: Fri, 29 Aug 2008 15:29:35 +0800 Subject: [desktop-testing] collect feedback about remote testing requirement for desktop testing In-Reply-To: <48B43098.1050803@sun.com> References: <48B41C5E.30509@sun.com> <48B43098.1050803@sun.com> Message-ID: <48B7A55F.9050306@sun.com> Hi Will, Thanks for your reply, please see below: Willie Walker wrote: > Hi Paul: > > I'm not quite sure about what you mean for the infrastructure for > desktop testing -- do you mean the hardware or the software > infrastructure? > It means everything related for our desktop testing, like web page setup(for test result, quality progress), test management tool selection, mail list, hardware, policy for involvement, hardware support for community user, etc. We want to setup one consistent testing environment for Sun Employees and community users, then people who want to contribute for desktop testing can involve the testing work as we are doing. > For software, the AT-SPI infrastructure is used in a number of testing > environments, including LDTP, Dogtail, and Strongwind. We also use it > for testing Orca (see http://live.gnome.org/Orca/RegressionTesting). > It works well. As testing moves forward, I think it will be important > to lay out a plan to test fresh bits as early as possible in order to > detect regressions across the board. I've noticed a pattern over the > past several releases of JDS/GNOME where testing was still being done > on relatively old stuff while the new stuff was regressing. We can > definitely do better, and much more can be automated. > Automation is also the target we want to do more. We'd also like to involve community people to the automation work. I also think automation can help lots on our testing. For the testing on relatively old stuff, it is somehow related with build system. Actually we also discussed about our build system internally, there is something as you are talking. I will give them the feedback. We'd also want to work more closely with community. > For hardware, I often just run a vncserver and run all my Orca > regression tests within that environment. With that, I don't need to > be logged in behind the console. I can also have several tests > running at the same time on the same machine without tying up my > keyboard/mouse. I can also remotely view the vncserver using the > vncviewer application so I can monitor the tests if I want. > > As such, as long as a machine is capable of running a vncserver, > testing works OK. The only 'gotcha' is that the runtime environment > is dependent upon the installed machine. As such, different > VirtualBox environments can be used to help test different flavors of > JDS/GNOME. > It looks like the remote testing can be supported by this way. Thanks for your feedback. Thanks, Paul. > Will > > Paul wrote: >> Hi All, >> >> We are working for the infrastructure setup for desktop testing. Now I'd >> like to collect the feedback about remote testing requirement for >> desktop testing. You know, the testing community in OpenSolaris >> community has provided some hardwares and one program called "Test >> Farm", then it can let community user leverage Sun's hardware for >> Solaris kernel/driver development and testing. For desktop testing, >> because all of our applications are GUI, the requirement is a little >> different from that. So I'd like to get your feedback if we need to do >> something like this way. If I can get enough positive feedback about it, >> I can discuss with team about how to setup it. >> >> The questions can be like this: >> 1. Do you think it is necessary to provide community user hardwares for >> desktop application remote testing? >> 2. If yes, could you please list some reasons? >> >> I'd like to set time limit from Aug. 26 to Sep. 1. Please give me your >> feedback. >> >> Thanks, >> Paul. >> _______________________________________________ >> desktop-testing mailing list >> desktop-testing at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/desktop-testing >