Can anyone give me the answers to these questions please ????
1. Test Director is a product of which company?
2. Write down the features of Test Director?
3. How do you create a new project in Test Director?
4. How can you add new fields to the DialogBox?
5. If at any time you need to restore the original database, What would be your approach?
6. Can a new Group be created in Test Director, if Yes How?
7. What is a Test Set.
8. What is the use of a Filter.
9. How to count the total no. of testcases designed for a specific subject?
10. What is Document Generator?
11. Can we export a Word Document to Test Director, If yes explain the process.
12. Can we change the permissions of a system group?
[ QUOTE ]
have been told these might be some interview questions..so thats why ...what do u mean by vendor website ???
[/ QUOTE ]
As a QA Manager I wouldn't ask any of these questions. I would ask about Test Director, but only if the person lists that on their resume. Most of the questions you posed wouldn't be in my list of things to ask as the answers can be obtained by sources like this and by reading the product manual.
As for the vendor, that is the person who makes/sells the application known as Test Director. Searching Google for "Test Director" yields the answer (the 2nd result).
[ QUOTE ]
have been told these might be some interview questions..so thats why
[/ QUOTE ]
As a hiring manager, I wouldn't even consider asking you questions along those lines unless you had put Test Director or Mercury Quality Center on your resume. Why would you think that someone would ask you questions about this specific product if you haven't mentioned it on your resume?
By the way, please don't forget that "I don't know" is a perfectly acceptable answer in an interview -- especially when you don't know the answer. Trying to cram and memorize a few answers is no substitute for having used the tool for a few years (or even months) and any competent interviewer can easily tell the difference between someone who's memorized a few answers versus someone who's used the product for a few years.
So saying you don't know is perfectly acceptable. Trying to misrepresent yourself (I'm not suggesting you're trying to do this, but I've been interviewing like mad lately and I'm getting pretty darned frustrated with this) is the easiest way to lose all hopes of getting hired regardless of what other skills you possess.
I'll go one step further -- I wouldn't ask these questions at all... Ten minutes with Google or the MQC user manual and you can answer all of these questions -- and the answers still don't tell me about your ability to test a software product or if you can use this particular tool effectively.