Epic > 019 > Parent: Write all Articles in Book V² > DIY > QA

[VillageHubertChen]

This week you will build the ViPC and install its OS, update its drivers and install basic apps. Once it is done you need to test that all is working. Those testing Procedures is exactly what you will be documenting in the Articles in this Book.

Testing a PC after assembly and installation is important, so that any problems will show in the V²Shop side and not on the customer side. Test Procedures are tedious and error prone. If not compiled in a Preflight Checklist it is likely that test procedures are forgotten and problems remain unveiled and are shipped to the customers. This is more expensive to fix and bad for reputation which in turn will reduce added sales through word of mouth.

Documenting QA procedures has the following benefits

• Tom has detailed instructions on how to QA (Quality Assurance) the ViPC before shipping
• Less mistakes shipped to customers
• More sales through word of mouth
• Lower after sales cost and time exposure
• I have reviewers lined up who can improve your QA test procedures
• If a problem was shipped to customer because the QA procedure did not unveiled it, you have a place to go in, add / modify the test and from then on the same problem will not shipped again

Reference

• Epic > 019 > Parent: Write all Articles in Book V² > DIY > QA