How to QC a Task
- Validate
- Run updated pages through W3C Validator
- Inspect
- Read the QC email and compare against the live site to ensure the request was done completely and correctly
- Spell check the text added by the developer (for unrelated spelling errors developers should be notified but not dinged)
- Test
- Test links & buttons (links to external sites must open in new tab)
- View the page(s) in Internet Explorer 7/8/9, Firefox and Google Chrome
- Notify
- Strip out any unnecessary information and send the email back to the original requester with the text "done." and any other pertinent information
- Make sure you have the Reply-To set as updates@atomic8ball.com
Recap (Things that are Dings)
- Broken links
- Invalid pages
- Spelling errors
- Page elements visually broken
- Parts of customer request missing
- External links and documents not opening in new tab
Final Note
If you received a ding, it is your responsibility to notify the client as outlined above once you have fixed the error.