Software Tester's Guide to Release-to-Web testing

Instructions:
Perform the following test case to determine the functionality of the piece of software to be released. Use the timer provided and please stay focused.

Important:
If you are a certified QA engineer/Tester, skip to step 5.
If you are the developer, go to Step 1, just for fun.

Step 1. Verify authenticity. Did you write this software? If yes, go to step 2. If no, go to step 5.
Step 2. Verify functionality. Does it work mostly? If yes, go to step 3. If no, go to step 5.
Step 3. Verify usability. Does it make sense to you, generally? If yes, go to step 4. If no, go to step 5.
Step 4. Verify visibility. Do you remember where you put it? Generally? If yes, go to step 5. If no, stop here. You are not a real developer, and should not be conducting this test. See, "would you like fries with that?"
Step 5. Testing complete. Test validated. We're pretty sure it works (if you were a "real" developer you would know that already). Proceed to step 6.
Step 6. Release to public. And call it something that has to do with a view of the world from inside something else. And then deny its a copy of something else from another fruity company.