Asking all of these questions could take a bit of time, so you might pick and choose which ones would fit, based on how advanced the position is that you are hiring. I tried ordering the questions so there isn't much time wasted if it becomes apparent the applicant doesn't have the skillset.
Background:
Q: How did you get into testing?
A: It would be good to see if the candidate is happy in this career path; and if testing is the applicant's focus and dedication for current and future.
Q: Explain in detail some projects where you used test automation, and/or Robot?
A: Look for experience, and over the applicant's resume.
Q: How much of your automation efforts deal with Recording and Playback?
A: This helps determine if the applicant employs Datapooling, Error Handling, Synchronization, and Verification.
Q: When scripts break, what do you do to fix them?
A: An answer such as 'start over' or 're-record the script' may indicate a red flag, especially when a project requires some inginuity for architecture, maintenance and reuse.
Q: What programming languages are you familiar with?
A: If the applicant mentions any relationship between VB & Robot, this is a plus in skill and knowledge because Robot is somewhat based on VB4.
Skills:
Q: If you were given free reigns to design and control the test automation effort on a new project, how would you go about it?
A: Look for strengths, efficiency, and experience in test automation development.
Q: List 3 types of difficulties and techinical challenges have you had with Robot, and how did get around those issues?
A: Look for specific examples that indicate Robot related problem solving skills.
Q: In Robot, choosing between the tasks of Synchronization, Navigation, DataPooling, Verification, Error Handling, or another function, which is your weakest skill and why?
A: Everyone has a weakness in certain areas. A good candidate would reveal this.
Q: If this weakest area is the most critical to the automation project, what would you do?
A: This should provide some indicator to the applicant's positive nature towards a challenge.
Basic Knowledge:
Q: When is it the right time to automate?
A: The interviewee should mention something about the nature of automation, and doing things that boost productivity at the right time.
Q: How long does it take to create 10 Robot Test Scripts?
A: There is no answer to this. It depends on the nature of the script.
Q: What is the goal of automation?
A: Boost Productivity.
Q: What is the common SQABasic command to get a single property from an object?
A: SQAGetProperty
Q: How do you verify functionality?
A: Look for types of methods, such as Verification Points/Check Points, SQAGetProperty, etc.
Q: What is the SQABasic command to log an error with Robot?
A: SQALogMessage sqaFail, "", ""
Advanced knowledge:
Q: Can you explain when it is proper to incorporate error handling?
A: Anytime you create functions that have parameters, you should encorporate error handling to prevent script runtime failures.
Q:Have you written any SQABasic libraries, if so, could you explain the purpose of a few of them?
A: Details provided here would supply evidence of advanced experience.
Q: What other kinds of tasks have you used automation to boost daily work productivity?
A: Details provided here would reveal any productive and creative traits of the applicant.
Q: Can you explain your idea of a code generator and how it might apply with Robot development to boost productivity?
A: Again to identify traits of the applicant's desire for automation
Q: Can you explain data driven testing?
A: The key idea for an answer is the use of dynamic input values and verification of outputs. In addition, the applicant may mention any of the following kinds of resources to support the activity: Datapools, TestManager, Flat files, .csv, database connections, SQL.
Regards
Ranganathan.P
|
