I also agree and see way too many of these types of requests. You
either know the product or you don't. It is one thing to ask support
on how to solve certain technical questions, but asking specifically
for "answers" to interview questions is just wrong.
When I hire people they have to go through 3 interview phases:
1. They have to take a written test
1a. I then review the answers
2. Then I conduct a verbal in-person interview and discuss the test as
part of it
3. Finally I end it with a hands-on test. This is the best because
some people who have "book knowledge" and just "study" for the
interview can get by the first two phases but people that don't have
real world experience can't fake the hands-on test. If you have real
experience then its easy. People get nervous and it can be a little
stressful, but the ones that can demonstrate that they know what they
are doing not only get the job but I normally cut them off on the
hands-on part as I don't need them to finish the script because I can
tell they know what they are doing.
If you really know what you are doing then don't "cheat" with
questions and answers, but simply practice automating things and
continue to learn. Make things up to automate and then develop a QTP
script to automate it. That's what employers want, is people that
truly know what they are doing and can be productive very quickly.
---
Shawn LoPorto
http://www.asi-test.com
--
You received this message because you are subscribed to the Google
"QTP - HP Quick Test Professional - Automated Software Testing"
group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/MercuryQTP?hl=en
