NX: testing considerations

[Don Resnik]

Hello,
There are two things I cannot test and I was wondering if anyone had any comments on the possible problems of not doing the testing.
1. Multiple platforms - I am only able to test my project on Windows. Should I set the look and feel, or default it to the machine? I am hoping they test it on the platform I created it on, but it should work on any platform anyway.
2. Multilple machines - I have been testing this on my one desktop so far. I have created multiple clients and added a sleep call in the locking so I could have multiple clients try to reserve the same room. It seems to me this should be a good enought test without actually running it on a network.
Has anyone passed with testing on only one platform and with one machine? Any comments would be greatly appreciated.
Thanks,
Don

[Javini Javono]

Hi,
Concerning the look and feel, I've decided to
only use Sun's default look and feel (I believe
that it is called metal); because metal ships
with all Java run-time environments for JRE 1.4
(perhaps earlier versions), then I am assured that
my applications will look the same on any platform.
Concerning testing on different platforms. This
can be a problem for who can afford different
platforms? Here's an idea perhaps: place your
completed project on a CD-ROM and then go visit
your local computer store; run your applications
on a Mac G4 or G5 computer and this at least brings
in Unix stuff to some extent (it's a little confusing,
but the Mac OS X is build on top of Unix ).
Thanks,
Javini Javono

[Matt R. Hansen]

To be safe, I would definitely use the default look and feel.
For testing your networking, I would highly recommend testing from different
machines. For example, when the client looks for the server in rmi, if the
url is wrong or not found, the default might look at the loopback address on your machine.