158 karma · joined August 10, 2011
I am not programmer, only Web App owner. I have people that code for me and now that the site is finished and about to release i would like to know what steps should i take.
Anyhow. I read your words and will code it later tonight. Thanks man.
I am doing QA for the last 13 years, so these are my tips: 1. Do not take anything as OBVIOUS. for example- People say the sun rise from the east. how do you know? did you see it? you should test it and confirm it is true. 2. To find many bugs doesn't mean you did a good job, you should try and find the quality ones. we call it 'Show Stopper' because they block the software from being shown to the public. 3. GUI bugs are as important as functionality ones. 4. Become a friend with the developers but let them eat shit with your bugs. it will be easier for them to handle a shit from a friend. 5. When you report a bug- be as much as informative as can be (screen captures, logs, debugging). the developer will appreciate it 6. Be the best in the company about the feature you are testing, make them feel you are the focalpoint of that feature.
good luck man
Bottom line- Unless you asked me to review- In real life i would not stayed their more then few seconds.
Good luck Guys