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


Reply via email to