Entries Tagged 'Automation Testing' ↓

Screening questions: Interviewer can Reject the candidate if he /she is not able to answer 2 questions out of following 4 questions:

1. Where did you learn WinRunner and TestDirector?

If they say it was in a mercury class, ask if they can show you their
certificate of completion. If they say no, let them know you will verify it
with Mercury.

2. Have you ever created a start-up script?

If they answer “yes”, ask them
what was in it and how they got WR to execute the start-up script when WR is
invoked.

They should answer something like this, “In the start-up script, we loaded all
the gui maps for the application, any library files we needed, and any custom
gui object mapping we have to do. We also loaded global variables and system
variables here. The startup script location is added to the WR .ini file,
wrun.ini located under the windows or winnt directory as wrun.ini”

3. What is the difference between writing a function and writing a script?

They should mention some of these things:
1. A function goes into a “compiled module”, a script does not.
2. A function follows strict “c” syntax. For instance, you have to declare
all variables created and used in the function. In a script you do not.

4. What is the difference between “set_window” and “win_activate”.?
When would you use “set_window” and when would you use “win_activate”?
win_activate has the format win_activate(window);. The win_activate function
makes the specified window the active window by bringing it into focus and
raising it to the top of the display. (It is the equivalent to clicking on the
window banner)

Set_window has the following format: set_window(window,[time]);
The set_window function directs input to the correct application window. This
directs the GUI map to this window. It also sets the scope for object
identification in the GUI map.

The most important difference is that set_window has a timing option.
WinRunner will wait a maximum of the number used in the function, PLUS the
system set timeout, to wait for the window to appear. Win_activate assumes the
window is already on the desktop and has no timing option.

These are some simple questions that should be very easy for a WR user who has
at least 6 months of good experience to answer.

Basics of WinRunner: 

Difference between WinRunner and Test Director?
“WinRunner handles automation test scripts
TestDirector manages test scripts, defects and test plan”

What is TSL? What 4GL is it similar too?
“Test Script Language, TSL C++”

Intermediate Que

What databases can Test Director reside on?
Oracle, Access, Sybase, MsSQL

Name a couple of standard web function found in the function generator? And explain their purpose.
Web_****

Advance que

Explain data parameterization in WinRunner.
Data is written multiple times, while WinRunner has a repeated loop to process the data.

Explain the project tree in Test Director.
Used to coordinate and manage test cases.

Expert Que

Have you completed the CPS exam? Which one?
TestSuite 6.0, LoadRunner, etc.

Write a short compiled module which selects random numbers; and what function is used to call your customized compiled module? Load or Reload function

What’s the purpose of the wrun.ini file?
Configuration set up for WinRunner

Hope you will enjoy this series of testing interview questions. For more interview questions please visit the posts on software testing interview questions.

I have posted one article on ‘To start with Automation’, now i think i should also
mention some ins and outs of Automation.

· Possibly. For small projects, the time needed to learn and implement them may not be worth it. For larger projects, or on-going long-term projects they can be valuable.

· Test automation can add a lot of complexity and cost to a test team’s effort. In addition problems like including unrealistic expectations, poor testing practices, a false sense of security, maintenance costs, and other technical and organizational problems might arise. But it can also provide some valuable assistance if its done by the right people, in the right environment and done where it makes sense to do so.

· Automated testing is an expensive process. Studies show that it can take between 3 to 10 times longer to develop automated Test Suite than to create and execute manual test cases. Costs of test automation include personnel to support test automation for the long term, dedicated test environment as well as the costs for the purchase, development and maintenance of tools.

· A common type of automated tool is the ‘record/playback’ type. For example, a tester could click through all combinations of menu choices, dialog box choices, buttons, etc. in an application GUI and have them ‘recorded’ and the results logged by a tool. The ‘recording’ is typically in the form of text based on a scripting language that is interpretable by the testing tool. If new buttons are added, or some underlying code in the application is changed, etc. the application can then be retested by just ‘playing back’ the ‘recorded’ actions, and comparing the logging results to check effects of the changes. The problem with such tools is that if there are continual changes to the system being tested, the ‘recordings’ may have to be changed so much that it becomes very time-consuming to continuously update the scripts. Additionally, interpretation of results (screens, data, logs, etc.) can be a difficult task. Note that there are record/playback tools for text-based interfaces also, and for all types of platforms.

Be sure to think these points before going for your project Automation.
So after taking decision for Automation you will not be in trouble.

Automation Checklist

If you answer yes to any of these questions, then your test should be seriously considered for automation.

Can the test sequence of actions be defined?

Is it useful to repeat the sequence of actions many times? Examples of this would be Acceptance tests, Compatibility tests, Performance tests, and regression tests.

Is it possible to automate the sequence of actions?
This may determine that automation is not suitable for this sequence of actions.

Is it possible to “semi-automate” a test?
Automating portions of a test can speed up test execution time.

Is the behavior of the software under test the same with automation as without?
This is an important concern for performance testing.

Are you testing non-UI aspects of the program?
Almost all non-UI functions can and should be automated tests.

Do you need to run the same tests on multiple hardware configurations?
Run ad hoc tests (Note: Ideally every bug should have an associated test case. Ad hoc tests are best done manually. You should try to imagine yourself in real world situations and use your software as your customer would. As bugs are found during ad hoc testing, new test cases should be created so that they can be reproduced easily and so that regression tests can be performed when you get to the Zero Bug Build phase.) An ad hoc test is a test that is performed manually where the tester attempts to simulate real world use of the software product. It is when running ad hoc testing that the most bugs will be found. It should be stressed that automation cannot ever be a substitute for manual testing.

I am working on Search engine project for last 6 months and now I understood most of the functionality and search engine strategies.

When you work as a Manual tester then somewhere you feel to automate your work. Sometimes doing routine manual work bores you. So here comes the need of Automation.
So Automation is very helpful for the regression type of work, to avoid repeated manual work. Now I understood the need of Automation and I want to start with it, but from where shall I start is the big question.

Before starting the Automation of your project work you need to remember following points:

1. What is the type of my project? Is it a stand-alone project or a client – server project?
2. What is the size of my project? You can find size on various metrics like kilo line of code. 3. Is there repeated work in my project?
4. Time taken for My current Manual project testing
5. Error rate by Manual testing.

In next some posts I will discuss about the Advantage – Disadvantages of Manual and Automation testing, also the step-by-step process to automate your project work.