On Monday 06 November 2006 23:35, Timothy A. Holmes wrote: > > I think running the build in a testing environment first is > > your best bet. > > > > -Mike > > Mike: > > I agree and in essence this is what I have done, the system is built and > sitting there, what I need to know is how to test the system in that > environment to make sure its gonna work properly >
If you want to be really thorough set it up (as you have done) and then try to use it for the intended purpose. Sit down and go through every step taken in an average day or user session. Intentionally do things wrong to see how it handles it. Then rope a few students in to sit down and use it for an average session - users have a habit of breaking simple things that work the admin ;) If you want to stress test it run a few compiles or similar that will take lots of cpu time. On top of that check out http://www.opensourcetesting.org/ - Noven -- >-- Novensiles divi Flamen --< >---- Miles Militis Fons ----<
pgpp4bkH6epFh.pgp
Description: PGP signature
