thread top ad



No announcement yet.

Post-repair testing - how far do you go?

  • Filter
  • Time
  • Show
Clear All
new posts

  • Post-repair testing - how far do you go?

    I'm curious what steps you guys take to test a repaired machine and how you guys do it.

    Myself, when a repair was an obvious fix like a missing component, damaged lvds connector or blown filter someplace, I'll check whatever wasn't working and if its fine, then I assume the rest of the machine is as it was before and send/hand it back to the customer.
    When it wasn't obviously fixed completely, like liquid damage, I'll check keyboard, trackpad, battery, webcam, wifi and audio. Do you go over every usb, sd card slot, audio jack and so on to make sure everything works on a repair like that, or skip certain things and hope for the best?

  • #2
    Depends. If it's something obvious like you said, I call it good. I typically run ASD or internal diagnostic after all repairs. On things like U8900 on 3332 or extensive liquid damage repairs, I typically stress test them.


    • #3
      I test everything of course. Boot OSX, test all keys, test iSight, check battery status, set clock correct, check BT, WiFi. On machines with GPU run "Heaven" for a few minutes.


      • #4
        I test everything, nothing worse than a returning customer because you forgot to plug shit in or keyboard is screwed. on off button not working. when a customer returns because of a fuck up they usually want it done on the spot, its not worth the hassle. good practice would be to have a standard checklist that consists of a 5 min check. document the check in the invoice as well to safeguard yourself.
        Read more........


        thread bottom ad