Entries from March 2007 ↓

Should we go for Automtion testing of project?
This is really a difficult question as I understand.

If you are doing manual testing of your project and decide to go for Automation I think you will have to ask yourself some basic questions like:

Which is the best testing tool?
To which level should I automate project Testing?
Is it possible to Automate my complete application?

By asking these questions you can go to near the Automation testing decision. i.e To be or not to be?

Let’s have answers for these basic questions:

Which is the best testing tool?
A basic question asked often. Different people will give you different answers for this question.

It is important to evaluate the tool based on your project environment, your budget,skills level of individuals Some tools work better in specific
environments, while in another environment they can create compatibility issue.
Demonstrate the tool using your application under test.

You can go for some open source tools available in the market, but with
the study of indivisual tool and then finalising which is better suit for you.

Second question is:
To which level should I automate project Testing?
Or can I 100 percent Automate project?
- Automation testing can provide several benefits if implemented successfully.
Expectation to Automation comes alog with, but you may not have the results
as quick as you expect.
Test Engineer must evaluate the great potential and should be able to put these benifites into your application.

Keep in mind that 100 percent Automation of any project is difficult to achieve given the time and budget constraints.

So try to Automate as possible as you can, atleast 80 percent, which will greatly benefit to your organisation.

Feel free to ask me query on Software testing Automation. I will try my best to answer it!

Here is the list of some frequently asked Winrunner Interview questions with answers.

I will continue this series as I posted some winrunner Questions and answer.

How you used WinRunner in your project?
Yes, I have been using WinRunner for creating automated scripts for GUI, functional and regression testing of the AUT.

Explain WinRunner testing process?
WinRunner testing process involves six main stages
i. Create GUI Map File so that WinRunner can recognize the GUI objects in the application being tested
ii. Create test scripts by recording, programming, or a combination of both. While recording tests, insert checkpoints where you want to check the response of the application being tested.
iii. Debug Test: run tests in Debug mode to make sure they run smoothly
iv. Run Tests: run tests in Verify mode to test your application.
v. View Results: determines the success or failure of the tests.
vi. Report Defects: If a test run fails due to a defect in the application being tested, you can report information about the defect directly from the Test Results window.

What is contained in the GUI map?
- WinRunner stores information it learns about a window or object in a GUI Map. When WinRunner runs a test, it uses the GUI map to locate objects. It reads an object’s description in the GUI map and then looks for an object with the same properties in the application being tested. Each of these objects in the GUI Map file will be having a logical name and a physical description.

- There are 2 types of GUI Map files.
i. Global GUI Map file: a single GUI Map file for the entire application
ii. GUI Map File per Test: WinRunner automatically creates a GUI Map file for each test created.

How does WinRunner recognize objects on the application?
WinRunner uses the GUI Map file to recognize objects on the application. When WinRunner runs a test, it uses the GUI map to locate objects. It reads an object’s description in the GUI map and then looks for an object with the same properties in the application being tested.

Have you created test scripts and what is contained in the test scripts?
Yes I have created test scripts. It contains the statement in Mercury Interactive’s Test Script Language (TSL). These statements appear as a test script in a test window. You can then enhance your recorded test script, either by typing in additional TSL functions and programming elements or by using WinRunner’s visual programming tool, the Function Generator.

How does WinRunner evaluates test results?
Following each test run, WinRunner displays the results in a report. The report details all the major events that occurred during the run, such as checkpoints, error messages, system messages, or user messages. If mismatches are detected at checkpoints during the test run, you can view the expected results and the actual results from the Test Results window.

Have you performed debugging of the scripts?
Yes, I have performed debugging of scripts. We can debug the script by executing the script in the debug mode. We can also debug script using the Step, Step Into, Step out functionalities provided by the WinRunner.

How do you run your test scripts?
We run tests in Verify mode to test your application. Each time WinRunner encounters a checkpoint in the test script, it compares the current data of the application being tested to the expected data captured earlier. If any mismatches are found, WinRunner captures them as actual results.

Sometimes Tester need common sense to test a application!!!

I am saying this because most of the times it is not possible to test the whole application within the specified time. In such situations it’s better to find out the risk factors in the projects and concentrate on them.

Here are some points to be considered when you are in such a situation:
1) Find out Important functionality is your project?
2) Find out High-risk module of the project?
3) Which functionality is most visible to the user?
4) Which functionality has the largest safety impact?
5) Which functionality has the largest financial impact on users?
6) Which aspects of the application are most important to the customer?
7) Which parts of the code are most complex, and thus most subject to errors?
Which parts of the application were developed in rush or panic mode?
9) What do the developers think are the highest-risk aspects of the application?
10) What kinds of problems would cause the worst publicity?
11) What kinds of problems would cause the most customer service complaints?
12) What kinds of tests could easily cover multiple functionalities?

Considering these points you can greatly reduce the risk of project releasing under less time constraint.

Feel free to ask me any testing query, resume tips or job help.

Software QA Engineer – Hyderabad

Positions based in Hyderabad, India.

We are looking for software engineers to work with the testing team and the development team to find, investigate, report and track defects. Focus on creating test plans, setting up test environments, developing automated tests, executing and maintaining automated test suites, the analysis of the results and leading manual test efforts.

You would be involved in black box testing following existing test plans and test plans that you write, designing new test cases, operating automated test suites, and analyzing defect reports.

If you love testing, are a quick learner, a great team player, and able to work independently, this is your chance to join us in our quest to provide software excellence.

Requirements:

Excellent knowledge of Internet/Web technologies, such as web browsers, http, and html.
Good knowledge of shell scripting.
Good knowledge of Perl or other scripting language.
Knowledge of C/C++, Java or Python a plus.
Working knowledge of Unix/Linux or Windows (admin).
Excellent analytical skills.
Excellent oral and written communication skills
At least 3 years of testing experience.
BE or BTech in Computer Science.

To apply please visit the following link
http://services.google.com/jobs/application/engeng?loc=in

If you are a tester, QA executive or want to come in testing field,
see in which of following qualities describes you.

What makes a good test engineer?

A good test engineer has :

. A ‘test to break’ attitude,
. An ability to take the point of view of the customer,
. A strong desire for quality, and an attention to detail.

. Tact and diplomacy are useful in maintaining a cooperative relationship with developers,
. An ability to communicate with both technical (developers) and non-technical (customers, management) people is useful.
. Previous software development experience can be helpful as it provides a deeper understanding of the software development process, gives the tester an appreciation for the developers’ point of view, and reduce the learning curve in automated test tool programming.
. Judgment skills are needed to assess high-risk areas of an application on which to focus testing efforts when time is limited.

What makes a good Software QA engineer?

The same qualities a good tester has are useful for a QA engineer.
Additionally :

. They must be able to understand the entire software development process and how it can fit into the business approach and goals of the organization.
. Communication skills and the ability to understand various sides of issues are important.
. In organizations in the early stages of implementing QA processes, patience and diplomacy are especially needed. An ability to find problems as well as to see ‘what’s missing’ is important for inspections and reviews.

Forwarded message:

WDC Is Hiring B.E / B.Tech / MCA Freshers for IBM

Having found its base in 1998 and headquartered in Kolkata, Web Development Company Limited (WDC)
offers a wide range of Internet solutions and recruitment related services in India, Asia Pacific
Region and major parts of Europe. With almost 450 dedicated professionals, the company today soars
high in terms of new and innovative service offerings and profitability.

We have invested in our internet and e-business capabilities and we are now in a position to drive
key elements of our enterprise solutions and services through e-Commerce initiatives, which will
further position WDC as a leader in the delivery of leading edge IT skills.

An excellent opportunity for Fresh Graduate Engineers willing to upgrade themselves and become a
Certified SIEBEL Programmer. WDC Ltd. with IBM India Pvt. Ltd. will be training the selected candidates
on Siebel Technology. The initial training will be provided in Bangalore only and not in any other locations.
On successful completion of the training, you will be absorbed into the payrolls of
WDC and would be deployed in world class projects with IBM India Pvt. Ltd.

Location of Training Bangalore

Eligibility :
1) Experience : Fresh College Hires (0 -12 months exp.)
2) Education Qualification : BE/ BTech/ MTech (Pref. CS/CE/IT), MCA with 65% compulsory
3) Excellent Communication Skills

Interview procedure: Written Test followed by Group Discussion.

If you are interested then please mail your resume to siebeljobs@wdc.in