What is QTP ?

QuickTest is a graphical interface record-playback automation tool. It is able to work with any web, java or windows client application. Quick Test enables you to test standard web objects and ActiveX controls. In addition to these environments, QuickTest Professional also enables you to test Java applets and applications and multimedia objects on Applications as well as standard Windows applications, Visual Basic 6 applications and .NET framework applications…QTP is Mercury Interactive Functional Testing Tool. QTP stands for Quality Test Professional. Mercury QuickTest Professional: provides the industry’s best solution for functional test and regression test automation - addressing every major software application and environment. This next-generation automated testing solution deploys the concept of Keyword-driven testing to radically simplify test creation and maintenance. Unique to QuickTest Professional’s Keyword-driven approach, test automation experts have full access to the underlying test and object properties, via an integrated scripting and debugging environment that is round-trip synchronized with the Keyword View.QuickTest Professional enables you to test standard Windows applications, Web objects, ActiveX controls, and Visual Basic applications. You can also acquire additional QuickTest add-ins for a number of special environments (such as Java, Oracle, SAP Solutions, .NET Windows and Web Forms, Siebel, PeopleSoft, Web services, and terminal emulator applications).

What’s the basic concept of QTP?

QTP is based on two concept-* Recording* Playback

Which scripting language used by QTP?

Basic scripting language we are using in QTP is VB scripting.

How many types of recording facility are available in QTP?

QTP provides three types of recording methods-* Context Recording (Normal)* Analog Recording* Low Level Recording

How many types of Parameters are available in QTP?

QTP provides three types of Parameter-* Method * Data Driven * Dynamic

What’s the QTP testing process?

QTP testing process consist of seven steps-* Preparing to recoding* Recording* Enhancing your script* Debugging* Run* Analyze* Report Defects (more…)

How to Start recording using QTP?

Choose Test > Record or click the Record button.When the Record and Run Settings dialog box opens to do this;1. In the Web tab, select Open the following browser when a record or run session begins.2. In the Windows Applications tab, confirm that Record and run on these applications (opened on session start) is selected, and that there are no applications listed.

What’s QuickTest Window?

Before you begin creating tests, you should familiarize yourself with the main QuickTest window.

The QuickTest window contains the following key elements:.

Title bar—Displays the name of the currently open test.. Menu bar—Displays menus of QuickTest commands.. File toolbar—Contains buttons to assist you in managing your test.. Testing toolbar—Contains buttons to assist you in the testing process.. Debug toolbar—Contains buttons to assist you in debugging tests.. Test pane—Contains the Keyword View and Expert View tabs.. Active Screen—Provides a snapshot of your application as it appeared when you performed a certain step during the recording session.. Data Table—Assists you in parameterizing your test.. Debug Viewer pane—Assists you in debugging your test. The Debug Viewer pane contains the Watch Expressions, Variables, and Command tabs. (The Debug Viewer pane is not displayed when you open QuickTest for the first time. You can display the Debug Viewer by choosing View <>

How does QTP identifes the object in the application ?

QTP identifies the object in the application by LogicalName and Class.For example :The Edit box is identified byLogical Name : PSOPTIONS_BSE_TIME20Class: WebEdit

How many Add-ins comes by default with QTP?

There are 3 Add-ins comes with QTP: (1) ActiveX (2) Visual Basic (3) Web

What are the views available in QTP?

(1) Keyword View (2) Expert View

What is keyword view and Expert view in QTP?

QuickTest’s Keyword Driven approach, test automation experts have full access to the underlying test and object properties, via an integrated scripting and debugging environment that is round-trip synchronized with the Keyword View. Advanced testers can view and edit their tests in the Expert View, which reveals the underlying industry-standard VBScript that QuickTest Professional automatically generates. Any changes made in the Expert View are automatically synchronized with the Keyword View.

What is Active Screen?

The Active Screen provides a snapshot of your application as it appeared when you performed a certain step during a recording session.

How many tabs are available in Debug Viewer Pane?

The Debug Viewer pane contains three tabs to assist you in debugging your test or component—Watch Expressions, Variables, and Command. Watch Expressions The Watch Expressions tab enables you to view the current value of any variable or other VBScript expression. Variables The Variables tab enables you to view the current value of all variables that have been recognized up to the last step performed in the run session. Command The Command tab enables you to execute a line of script in order to set or modify the current value of a variable or VBScript object in your test or component. When you continue the run session, QuickTest uses the new value that was set in the command.

How many toolbars QTP has?

QuickTest has 4 built-in toolbars: 1. The File toolbar 2. The Testing toolbar 3. The Debug toolbar 4. Action toolbar The Action toolbar is available in the Keyword View and contains options that enable you to view all actions in the test flow or to view the details of a selected action. The Action toolbar is not available for components.

What is object Repository ?

Explain different types of Object Repositories?QuickTest identifies objects in your application based on a set of test object properties. It stores the object data it learns in the object repository. You can save your objects either in a shared object repository or in action object repository. In shared object repository mode, you can use one object repository file for multiple tests or components. In object repository peraction mode, QuickTest automatically creates an object repository file for each action in your test. Object repository per-action mode is not available for components

What is Object Spy in QTP?

Using the Object Spy, you can view the properties of any object in an open application. You use the Object Spy pointer to point to an object. The Object Spy displays the selected object’s hierarchy tree and its properties and values in the Properties tab of the Object Spy dialog box

Explain different recording modes ?

QuickTest’s normal recording mode records the objects in your application and the operations performed on them. This mode is the default and takes full advantage of QuickTest’s test object model, recognizing the objects in your application regardless of their location on the screen.Analog Recording - enables you to record the exact mouse and keyboard operations you perform in relation to either the screen or the application window. In this recording mode, QuickTest records and tracks every movement of the mouse as you drag the mouse around a screen or window. This mode is useful for recording operations that cannot be recorded at the level of an object, for example, recording a signature produced by dragging the mouse.Note: You cannot edit analog recording steps from within QuickTest. ?Low-Level Recording - enables you to record on any object in your application, whether or not QuickTest recognizes the specific object or the specific operation. This mode records at the object level and records all run-time objects as Window or WinObject test objects. Use low-level recording for recording tests in an environment or on an object not recognized by QuickTest. You can also use low-level recording if the exact coordinates of the object are important for your test. Note: Steps recorded using low-level mode may not run correctly on all objects.

Explain the need to use analog recording in qtp?

This mode records exact mouse and Key Board operations you perform in relation to the screen /Application Window. This mode is useful for the operation which you can record at Object Level, such as drawing a picture, recording signature. The steps recorded using Analog Mode is saved in separated data file, Quick Tests add to your Test a Run Analog File statement that calls the recorded analog File. This file is stored with your action in which these Analog Steps are created. The Step recorded in Analog mode can not be edited within QTP.

What is the extension of script and object repository files?

Object Repository : .tsr , Script : .mts, Excel : Default.xls

How to supress warnings from the “Test results page”?

From the Test results Viewer “Tools > Filters > Warnings”…must be “Unchecked”.

When we try to use test run option “Run from Step”, the browser is not launching automatically why?

This is default behaviour

In how many ways we can add check points to an application using QTP?

We can add checkpoints while recording the application or we can add after recording is completed using Active screen (Note : To perform the second one The Active screen must be enabled while recording).

How to Run a Test using QTP?

1 Start QuickTest and open your test.If QuickTest is not already open, choose Start > Programs > QuickTest Professional > QuickTest Professional.. If the Welcome window opens, click Open Existing.. If QuickTest opens without displaying the Welcome window, choose File > Open or click the Open button.In the Open Test dialog box, locate and select your test, then click Open.
2 Confirm that all images are saved to the test results.QuickTest allows you to determine when to save images to the test results.Choose Tools > Options and select the Run tab. In the Save step screen capture to test results option, select Always.Click OK to close the Options dialog box.3 Start running your test.Click Run or choose Test > Run. The Run dialog box opens.Select New run results folder. Accept the default results folder name.Click OK to close the Run dialog box.

How to Save your test using QTP?

Select File > Save or click the Save button. The Save dialog box opens to the Tests folder.Create a folder which you want to save to, select it, and click Open.Type your test name in the File name field.Confirm that Save Active Screen files is selected.Click Save. Your test name is displayed in the title bar of the main QuickTest window.

How to open a new test using QTP?

1. If QuickTest is not currently open, choose Start > Programs > QuickTest Professional > QuickTest Professional. If the Welcome window opens, click Blank Test. Otherwise, choose File > New, or click the New button. A blank test opens. 2. . If QuickTest is already open, check which add-ins are loaded by selecting Help > About QuickTest Professional. If the Web Add-in is not loaded, you must exit and restart QuickTest. When the Add-in Manager opens, select the Web Add-in, and clear all other add-ins. Choose File > New, or click the New button. A blank test opens.

How to do Laod testing for web based Application?

1. Recording a scenerio in QTP of my web based application.2. Make 100 copies of that scenerio and run the test (scenerio run for 100 times)3. In that case, do the load of application on server.4. The basic logic of running the copy 100 times is to create same scenerio as if 100 users were working

How to “Turn Off” QTP results after running a Script?

Goto “Tools > Options > Run Tab” and Deselect “View results when run session ends”. But this suppresses only the result window, but a og will be created and can viewed manulaly which cannot be restricted from getting created.

Explain about the Test Fusion Report of QTP ?

Once a tester has run a test, a TestFusion report displays all aspects of the test run: a high-level results overview, an expandable Tree View of the test specifying exactly where application failures occurred, the test data used, application screen shots for every step that highlight any discrepancies, and detailed explanations of each checkpoint pass and failure. By combining TestFusion reports with QuickTest Professional, you can share reports across an entire QA and development team.

What’s Checkpoints for QTP?

A checkpoint verifies that expected information is displayed in your application while the test is running.

QuickTest Professional offers the following types of checkpoints:

How to add a standard checkpoint in your test ?

1. Start QuickTest and open your test.In the Open Test dialog box, locate and select your test, then click Open.2. Save the test as Checkpoint.Select File > Save As. Save the test as Checkpoint.3. Confirm that the Active Screen option is enabled.If you do not see the Active Screen at the bottom of the QuickTest window, click the Active Screen button, or choose View > Active Screen.4. Locate the page where you want to add a standard checkpoint.5 Create a standard checkpoint.In the Active Screen, right-click element in your application and choose Insert Standard Checkpoint.6 Save the test.

How to add a page checkpoint to your test?

The page checkpoint checks that the number of links and images in the page when you run your test is the same as when you recorded your test.1 Locate the page where you want to add a page checkpoint.2 Create a page checkpoint.Right-click anywhere in the Active Screen, and choose Insert Standard Checkpoint. The Object Selection - Checkpoint Properties dialog box opens. Note that this dialog box may include different elements, depending on where you click in the Active Screen.3 Save the test.

what is the use of Text output value in Qtp?

Output values enable to view the values that the application talkes during run time.When paramaterised, the values change for each iteration.Thus by creating output values, we can capture the values that the application takes for each run and output them to the data table.

How to Creating an Output Value using QTP?

1 Start QuickTest and open the Parameter test.2 Save the test as Output.3 Confirm that the Active Screen option is enabled.4 Select the text you want to use as an output value.5 Set the output value settings.6 Modify the table checkpoint.7 Save the test.

What’s the difference between a checkpoint and output value?

Checkpoint only checks for the specific attribute of an object in AUT while Output value can output those attributes value to a column in data table

Explain QTP Testing process ?

The QuickTest testing process consists of 6 main phases:

1. Create your test planPrior to automating there should be a detailed description of the test including the exact steps to follow, data to be input, and all items to be verified by the test. The verification information should include both data validations and existence or state verifications of objects in the application.2. Recording a session on your applicationAs you navigate through your application, QuickTest graphically displays each step you perform in the form of a collapsible icon-based test tree. A step is any user action that causes or makes a change in your site, such as clicking a link or image, or entering data in a form.
2. Enhancing your testo Inserting checkpoints into your test lets you search for a specific value of a page, object or text string, which helps you identify whether or not your application is functioning correctly.NOTE: Checkpoints can be added to a test as you record it or after the fact via the Active Screen. It is much easier and faster to add the checkpoints during the recording process.o Broadening the scope of your test by replacing fixed values with parameters lets you check how your application performs the same operations with multiple sets of data.o Adding logic and conditional statements to your test enables you to add sophisticated checks to your test.
3. Debugging your testIf changes were made to the script, you need to debug it to check that it operates smoothly and without interruption.
4. Running your test on a new version of your applicationYou run a test to check the behavior of your application. While running, QuickTest connects to your application and performs each step in your test.
5. Analyzing the test resultsYou examine the test results to pinpoint defects in your application.
6. Reporting defectsAs you encounter failures in the application when analyzing test results, you will create defect reports in Defect Reporting Tool.

1. What are the Features & Benefits of Quick Test Pro (QTP 8.0)?

- Operates stand-alone, or integrated into Mercury Business Process Testing and Mercury Quality Center. Introduces next-generation zero-configuration Keyword Driven testing technology in Quick Test Professional 8.0 allowing for fast test creation, easier maintenance, and more powerful data-driving capability. Identifies objects with Unique Smart Object Recognition, even if they change from build to build, enabling reliable unattended script execution. Collapses test documentation and test creation to a single step with Auto-documentation technology. Enables thorough validation of applications through a full complement of checkpoints.

How many types of Actions are there in QTP?

There are three kinds of actions:non-reusable action—an action that can be called only in the test with which it is stored, and can be called only once. reusable action—an action that can be called multiple times by the test with which it is stored (the local test) as well as by other tests.external action—a reusable action stored with another test. External actions are read-only in the calling test, but you can choose to use a local, editable copy of the Data Table information for the external action.

What is the difference between Call to Action and Copy Action.?

Call to Action : The changes made in Call to Action , will be reflected in the orginal action( from where the script is called).But where as in Copy Action , the changes made in the script ,will not effect the original script Action.

Syntact for how to call one script from another?

and Syntax to call one “Action” in another?RunAction ActionName, [IterationMode , IterationRange , Parameters]Here the actions becomes reusable on making this call to any Action.IterationRange String Not always required. Indicates the rows for which action iterations will be performed. Valid only when the IterationMode is rngIterations. Enter the row range (i.e. “1-7″), or enter rngAll to run iterations on all rows.If the action called by the RunAction statement includes an ExitAction statement, the RunAction statement can return the value of the ExitAction’s RetVal argument.

Inserting a Call to Action is not Importing all columns in Datatable of globalsheet. Why?

Inserting a call to action will only Import the columns of the Action called

How to execute a WinRunner Script in QTP?

(a) TSLTest.RunTest TestPath, TestSet [, Parameters ] –> Used in QTP 6.0 used for backward compatibility Parameters : The test set within Quality Center, in which test runs are stored. Note that this argument is relevant only when working with a test in a Quality Center project. When the test is not saved in Quality Center, this parameter is ignored.e.g : TSLTest.RunTest “D:\test1″, “”(b)TSLTest.RunTestEx TestPath, RunMinimized, CloseApp [, Parameters ] TSLTest.RunTestEx “C:\WinRunner\Tests\basic_flight”, TRUE, FALSE, “MyValue” CloseApp : Indicates whether to close the WinRunner application when the WinRunner test run ends. Parameters : Up to 15 WinRunner function argument

Why divide a test into three action calls?

When you create a new test, it contains a call to one action. By dividing your tests into calls to multiple actions, you can design more modular and efficient tests.

What is parameter?

A parameter is a variable that is assigned a value from an external data source or generator. If you wish to parameterize the same value in several steps in your test or component, you may want to consider using the Data Driver rather than adding parameters manually.

How many ways we can parameterize data in QTP ?

There are four types of parameters:Test, action or component parameters enable you to use values passed from your test or component, or values from other actions in your test.Data Table parameters enable you to create a data-driven test (or action) that runs several times using the data you supply. In each repetition, or iteration, QuickTest uses a different value from the Data Table.Environment variable parameters enable you to use variable values from other sources during the run session. These may be values you supply, or values that QuickTest generates for you based on conditions and options you choose.Random number parameters enable you to insert random numbers as values in your test or component. For example, to check how your application handles small and large ticket orders, you can have QuickTest generate a random number and insert it in a number of tickets edit field.

How Does Run time data (Parameterization) is handled in QTP?

You can then enter test data into the Data Table, an integrated spreadsheet with the full functionality of Excel, to manipulate data sets and create multiple test iterations, without programming, to expand test case coverage. Data can be typed in or imported from databases, spreadsheets, or text files.

How to Defining a Data Table Parameter for QTP?

1 Start QuickTest and open the Checkpoint test.2 Save the test as Parameter.3 Confirm that the Active Screen option is enabled.4 Confirm that the Data Table option is enabled.5 Select the text to parameterize.6 Set the parameterization properties.

How to add a runtime parameter to a datasheet?

DataTable.LocalSheetThe following example uses the LocalSheet property to return the local sheet of the run-time Data Table in order to add a parameter (column) to it.MyParam=DataTable.LocalSheet.AddParameter(”Time”, “5:45″)

Automation Tools

Mercury offers a suite of solutions that automate testing and quality
assurance for client/server software and systems, e-business applications, and enterprise resource planning applications.

1. QuickTest ProfessionalTM - E-business functional testing
2. LoadRunner® - Enterprise load testing
3. TestDirectorTM - Integrated test management
4. WinRunner® - Test automation for the enterprise



Segue Software delivers the industry's premier e-business reliability products and solutions to help you address the risks and complexities that can affect the performance and quality of your e-business systemSilkTest - Automated functional and regression testing

1. SilkPerformer - Automated load and performance testing
2. SilkMonitor - 24x7 monitoring and reporting of Web, application and database servers
3. SilkPilot - Unit testing of CORBA objects
4. SilkObserver - End-to-end transaction management and monitoring for CORBA applications
5. SilkMeter - Access control and usage metering
6. SilkRealizer - Scenario testing and system monitoring
7. SilkRadar - Automated defect tracking

Test Strategy

What is a strategy? Why does testing need one?

A strategy outlines what to plan, and how to plan it. A successful strategy is your guide through change, and provides a firm foundation for ongoing improvement. Unlike a plan, which is obsolete from the point of creation, a strategy reflects the values of an organization - and remains current and useful.
When an organization tests its products or its tools, it tries to compare them against its expectations and values. By its nature, testing introduces change as problems are identified and resolved. A test strategy is necessary to allow these two impulses to work together. Furthermore, testing can never be said to be 'complete', and a core skill in testing is the justified management of conflicting demands; without a strategy, these judgments will be inconsistent to the point of failure.
Software development is a creative process. A test strategy is a vital enabler to this process - keeping focus on core values and consistent decision-making to help achieve desired goals with best use of resource. A good strategy stands as a clear counter to reactive, counter-productive test approaches.

Examples and Templates:

A test strategy is not a document. It is a framework for making decisions about value, and has strong links to the unique values of an organization. It is part of the creative process. Although templates exist, most organizations and projects are poorly served by a one-size-fits-all approach to their specific goals. You may find templates useful on projects where the product to be tested can be created and marketed simply by following templates - but on other projects, they're dangerous.
Workroom Productions avoids using such templates, and will create a strategy tailored to your particular needs. If you have an existing, problematic strategy, we will suggest areas where it could be slimmed down, and identify aspects that have been missed. Whether you've got documents or not, we'll help you with your strategy.
Test strategies can cover a wide range of testing and business issues. While not a checklist, you might expect to see some of the following in your own strategy:
1. values and decision-making framework
2. approaches to risk assessment, costs and quality through the organization
3. test techniques, test data, test scope and test planning
4. completion criteria and analysis
5. test management, metrics and improvement
6. skills, staffing, team structure and training
7. test environment, change control and release strategy
8. defect control, tracking and the approach to fixes
9. re-tests and regression tests
10. profiling and analysis for non-functional testing
11. test automation and test tool assessment

Testing as a genuinely strategic part of software development:

A strategic decision is one that opens up opportunities which are otherwise unapproachable - a strategic resource is the mechanism by which these opportunities are exploited.
Design, coding, and testing are the three key parts of software development. These are activities, not phases; they operate in parallel and are closely coupled. On a not-too-turbulent project, testing and defect resolution typically account for 25-35% of the final cost of development. Information produced by software testing is clearly an input to the overall organization’s strategic decisions about marketability and release - but testing can provide much more than this for the significant spends it absorbs.

Bug Report Template

A sample Bug Report Template :

Test Case Templates

It depends and vary company to company that what Test Case template it has has adopted or designed but few of them are given below :

1.















2.

Software Testing Basics

What is Software Quality Assurance?
The other technical terminology for Software Quality Assurance is Verification and Validation. To put in simple words, Verification speaks on "Are we building the right system?" and Validation speaks on "Are we building the system right?". SQA is an umbrella activity that is applied throughout the software process. Quality as the American Heritage Dictionary defines is, "A Characteristic or attribute of something..."

What is Software Testing by the way?
In general, testing is finding out how well something works. In terms of human beings, testing tells what level of knowledge or skill has been acquired. In computer hardware and software development, testing is used at key checkpoints in the overall process to determine whether objectives are being met. For example, in software development, product objectives are sometimes tested by product user representatives. When the design is complete, coding follows and the finished code is then tested at the unit or module level by each programmer; at the component level by the group of programmers involved; and at the system level when all components are combined together. At early or late stages, a product or service may also be tested for usability. At the system level, the manufacturer or independent reviewer may subject a product or service to one or more performance tests, possibly using one or more benchmarks. Whether viewed as a product or a service or both, a Web site can also be tested in various ways - by observing user experiences, by asking questions of users, by timing the flow through specific usage scenarios, and by comparing it with other sites.
The answer to the primary role of software testing is two fold:Determine whether the system meets specifications (Producer View), andDetermine whether the system meets business and user needs (Customer View)

Testing encompasses three concepts:
The demonstration of the validity of the software at each stage in the system development life cycle.Determination of the validity of the final system with respect to user needs and requirements. Examination of the behavior of a system by executing the system on sample test data.

Goal of Testing:
The primary Goal of Testing is to uncover requirement, design or coding errors in the programs. Let us look at some fundamental concepts of Software Testing. "Verification" is the process of determining whether or not the products of a given phase of software development fulfill the specifications established during the previous phase. The verification activities include proving, testing and reviews.
"Validation" is the process of evaluating the software at the end of the software development to ensure compliance with the software requirements. Testing is a common method of validation.
For high reliability we need to perform both activities. Together they are called the "V & V" activities.

Software Testing is an Art. A good tester can always be a good programmer, but a good programmer need not be a good tester.

Test Objectives:
The following can be described as test objectives as per Glen Mayer:Testing is a process of executing a program with the intent of finding an error.A good test case is one that has a high probability of finding an as-yet-undiscovered error.A successful test is one that uncovers an as-yet-undiscovered error.

Testing Principles:
The following can be described as testing principles: All tests should be traceable to customer requirements.Tests should be planned long before testing begins.The Pareto principle applies to testing. Testing should begin “in small” and progress toward testing “in large”. Exhaustive testing is not possible.To be most effective, testing should be conducted by an independent third party.

Verification Strategies:
The following can be categorized into Verification Strategies: Requirements Reviews.Design Reviews. Code Walkthrough. Code Inspection.
Validation StrategiesThe following can be described as the basic Validation Test strategies. 1. Unit Testing.2. Integration Testing.3. System Testing.4. Performance Testing.5. Alpha Testing.6. User Acceptance Testing (UAT)7. Installation Testing.8. Beta Testing.

SDLC

The stages of SDLC can be characterized and divided up in different ways, including the following:

· Project planning, feasibility study: Establishes a high-level view of the intended project and determines its goals.

· Systems analysis, requirements definition: Refines project goals into defined functions and operation of the intended application. Analyzes end-user information needs.

· Systems design: Describes desired features and operations in detail, including screen layouts, business rules, process diagrams, pseudocode and other documentation.

· Implementation: The real code is written here.

· Integration and testing: Brings all the pieces together into a special testing environment, then checks for errors, bugs and interoperability.

· Acceptance, installation, deployment: The final stage of initial development, where the software is put into production and runs actual business.

· Maintenance: What happens during the rest of the software's life: changes, correction, additions, moves to a different computing platform and more. This, the least glamorous and perhaps most important step of all, goes on seemingly forever.

SDLC - VModel

A software development life cycle is the process followed when developing information systems, from the initial stage of information gathering, all the way through to maintenance and support of the system.
UKSH believes firmly in user-involvement at every stage of the process - we feel this is integral to ensuring that the system is delivered 100% to the requirements of the user, and any decisions that may be required during the system building process can be resolved efficiently.
We develop using a process known as the "V" model of systems development. At each testing stage (see diagram, below), the corresponding planning stage is referred to, ensuring the system accurately meets the goals specified in the analysis and design stages.

How to get job in Software Testing quickly?

In recent days this is the most asked question to me by readers. How to get software testing job? How to come in software testing field? or Can I get job in testing?

All these questions are similar and I want to give also similar answer for this. I have written post on choosing software testing as your career where you can analyze your abilities and know which are the most important skills required for software testing.

I will continue mentioning that “know your interest before going into any career field”. Just going to software testing career or any other hot career is wrong and which may result into loss of your job interest as well as your job.

Now you know your abilities, skills, interests right? and you have made decision to go for software testing career as it is your favorite career and you suit most in this career. So here is a guideline for how to get a good job in software testing field.

If you are a fresher and just passed out from your college or passing out in coming months then you need to prepare well for some software testing methodologies. Prepare all the manual testing concepts. If possible have some hands-on on some automation and bug tracking tools like winrunner and test director. It is always a good idea to join any software testing institute or class which will provide you a good start and direction of preparation. You can join any 4 months duration software testing course or can do diploma in software testing which is typically of 6 months to 1 year. Keep the preparation going on in your course duration. This will help you to start giving interviews right after getting over your course.

If you have some sort of previous IT experience and want to switch to software testing then it’s somewhat simple for you. Show your previous IT experience in your resume while applying for software testing jobs. If possible do some crash course to get idea of software testing concepts like I mentioned for freshers above. Keep in mind that you have some kind of IT experience so be prepared for some tough interview questions here.

As companies always prefer some kind of relevant experience for any software job, its better if you have relevant experience in software testing and QA. It may be any kind of software testing tools hands-on or some testing course from reputed institutes.

Please always keep in mind- Do not add fake experience of any kind. This can ruin your career forever. Wait and try for some more days to get the job by your abilities instead of getting into trap of fake experience.

Last important words, Software testing is not ‘anyone can do career!’ Remove this attitude from your mind if someone has told such kind of foolish thing to you. Testing requires in depth knowledge of SDLF, out of box thinking, analytical skill and some programming language skill apart from software testing basics.

So best luck and start preparation for your rocking career! I will continue writing this career series and what you actually need to prepare for software testing interview.

How to be a good tester?

It’s a every testers question. How to be a good tester?
Apart from the technical knowledge, testing skills, tester should have some personal level skills which will help them to build a good rapport in the testing team.

What are these abilities , skills which make a tester as a good tester?
Well, I was reading Dave Whalen’s article “Ugly Baby Syndrome!” and found it very interesting. Dave compared software developers with the parents who deliver a baby (software) with countless efforts. Naturally the product managers, architectures, developers spent their countless time on developing application for the customer. Then they show it to us (testers) and asks: “ How is the baby (Application)? “ And testers tell them often that they have and ugly baby. (Application with Bugs!)

Testers don’t want to tell them that they have ugly baby, but unfortunately its our job. So effectively tester can convey the message to the developers without hurting them. How can be this done? Ya that is the skill of a good tester!

Here are the tips sated by Dave to handle such a delicate situation:
Be honest and Responsive:Tell developers what are your plans to attack their application.
Be open and available:If any dev ask you to have a look at the application developed by him before the release, then politely give feedback on it and report any extra efforts needed. Don’t log the bug’s for these notes.

Let them review your tests:
If you have designed or wrote some test cases from the requirement specifications then just show them those test cases. Let them know your stuff as you are going to critic on developers work!

Use of Bug tracker:
Some testers have habit to report each and everything publicly. This attitude hurts the developers. So if you have logged any bug then let the bug tracking system report it to respective developers and managers. Also don’t each time rely on bug tracker, talk personally to developers what you logged and why you logged?

Finally some good personal points:
Don’t take it personally:Do the job of messenger. You could be a close target always. So build a thick skin!

Be prepared:
A good message in the end, Be prepared for everything! If worst things might not happened till now but they can happen at any moment in your career. So be ready to face them.