Paul,
If the testing machine can be accessed out of SWAN, multi-testers can
use Xvnc to login the machine at the same time and test most of GUI
programs.
This is the way we are using in our lab for multi-users login and testing.
It is very easy to setup Xvnc:
# Warning: restart will kill all current dtlogin sessions!
svccfg -s cde-login setprop 'dtlogin/args=""'
svcadm restart cde-login
# Add xvnc service to /etc/services if it isn't already (CR 6614889)
printf "vnc-server\t5900/tcp\t\t\t# VNC Server\n" >> /etc/services
# Enable Xvnc inetd service:
inetadm -e xvnc-inetd
Connect from another machine with:
vncviewer hostname:0
Thanks
--Ava
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
>
