RE: different testing OS

["Bryant, William" <mbryant@c-cor.net>]

Hi Linda,

We've been developing and unit testing on WinNT/Win2K and deploying to
Solaris for over a year without any issues whatsoever.  We do, however, do
final system testing on a box that resembles the deployed system as closely
as possible.

Two issues I would suggest looking out for:
- Graphics.  Java uses the OS graphics environment for any graphic work that
you do.  If you are using any king of graphics (dynamically generated
charts, AWT, Swing, etc) in your application be extra careful.  Many *nix
servers do not have the graphics environment that is taken for granted on
Windows machines.  If your *nix box does not have a graphics card or an X
server it can use you won't be able to render graphics on the deployed
system.  Even with an X server, *nix and Windows WILL render the graphics
differently.  I believe JDK 1.4 will address this issue.

- Threads.  The JVM/OS combination you are using on the development system
may handle threads  somewhat differently on the deployed system (green vs
native threads).  This may show some bugs in multi-threaded code
(synchronization, timing issues, deadlocks, etc) that were not as easily
found during unit testing.

That's my $0.02, hope it helps.


... Mike


---------------------
Mike Bryant
Sr. Software Engineer
C-COR.net
mbryant@c-cor.net
770-814-0984 


-----Original Message-----
From: linda fan [mailto:lxfan_2000@yahoo.com] 
Sent: Tuesday, April 09, 2002 11:44 AM
To: ajug-members@www.ajug.org
Subject: different testing OS


Hi,
Can anyone told me what is the harm by testing
application on a Window machine and actual production
is running on the Linux or unix OS beside the path and resources?

Thanks a lot!
Linda


__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax http://taxes.yahoo.com/