unit3 wrote:
> Lance Levsen wrote:
> Not hard, but how do you effectively test a complex component for
> problems? For instance, do you have the hardware to test everything on a
> recent-ish video card, which is often more complex than the rest of the
> system combined? Sure, personally you can do a reasonable amount of
> testing on your own system, but I'd doubt that a white-box company can
> put the same level of testing in that a first tier company can.
>
> G
Oh, I agree there. Component testing isn't the subject of this thread
though. Let's face it, the small white box stores simply buy x amount of
y,z,a,b,and c. Throw them together and hope for the best. They don't
spec the drives, or test the memory.
The problem as exemplified by two examples here though is when y isn't
y. Component testing _should_ be upstream of the white box though, if it
isn't then the white box store has to raise a little hell with their
suppliers. I also doubt that the Dell's, Gateways, and Compaqs of the
world do that level of testing either.
QA isn't just a one spot thing. As you mention, it's also on the head of
the end-user.
Cheers,
lance
-- Lance Levsen, Catprint Computing Tel: (306) 493-2249 Cell: (306) 230-8783 Blog: http://www.catprint.ca/blog/ SaskBlogs: http://saskblogs.catprint.ca/
This archive was generated by hypermail 2.1.8 : Wed Feb 07 2007 - 11:41:35 CST