Full testing procedures after new build

[kasm]

I was wondering is anyone has a good guide regarding complete testing and diagnostics procedures during and after a new build.

What tools and software do you use?
Are there some diagnostics that should be done during the build to save time in case something is not done correctly at the beginning?
How do to ensure that every component is performing correctly before you proceed with installing apps and data?

Thanks

---------------
Edit(2007 01 15 12:40 pm Easern)

let me clarify a bit. I was thinking af things like memtest, running a util to check the temp of the CPU and Video cards to see that they are not too hot. Running other utils to make sure your CPU and memory are running at the right speeds. Any software to test the power supply? maybe even running a benchmark util to just check that overall performance is not out of wack.

[TwoRails]

Parts have become a lot more reliable overall and many (if not most) folks don't run things like overnight stress tests anymore. It it works, it works. My testing, anymore, consists of installing apps and running them to make sure they installed OK.

[newbuilder14]

You could run a program called Orthos for stress testing to see how your computer runs under a heavy load.

[Cricket]

I really don't do any "testing" or "diagnostics" after I finish a build. I just do as TwoRails does and install my normal assortment of security, utility and productivity apps and run them. If there is something wrong with the computer I probably won't even reach this point as the installation of Windows will usually bring up a problem if there is one.

Cricket