Please help this Tester.

A Request to you ALL !!!!!!!!!!!
Chandrasekhar B N is a 26 year old Software Tester working at Bangalore. He was detected with Blood cancer (Acute Lymphoblastic Leukemia - with Ph+ve) in October.
Chandrashekar is the sole bread earner in the family. His mother is a housewife and his 21 year old brother is a student, too. Doctors have prescribed chemotherapy and bone marrow transplant at a cost of Rs. 8 lacs for chemotherapy + Rs. 10 lacs for Bone Marrow Transplant. As he is now getting treatment, with no additional income in the family, family members and friends are trying to gather funds for his treatment and daily expenses but are at the end of their resources.

Some Test Management articles

Learn something on Test Management:

Job - Java Developer/Selenium Tester; Location: Eagan, MN; Duration: 6+ Months

Two positions available for the below position, if you are interested to apply for this position, please send your updated resume.
Role: Java Developer/Tester
Location: Eagan, MN
Duration: 6+ Months
  • -JAVA DEVELOPMENT EXP - this position is more testing than development but must have some java dev exp or background.
  • -AGILE EXP is a plus

Best answer to - Are you a Software Testing Expert?

Quick Update - Around one month back, we posted a Quiz - Are you a Software Testing Expert? Best and correct answer is given by Debajit Hazarika.

Checkout his answers at -  (in comment box)

Testing Challenge – Crack the logic of a Facebook Application

One of my friend has develop a small facebook application “Yo Baby”. the application is really very simple and contains a few lines of code. The application description is -

About Yo Baby: Want to Know who visit your profile frequently? Track Your profile visitors – by Yo baby.

Actually this application is not tracking facebook profile visitors. But It will display some of your friend names (there is a logic behind it). Challenge is to crack the logic behind this application.

Hint is given in the application itself - More you invite, more you get the accurate results.
Application URL -
Why this challenge? A: It will enable you to think out of the box. Give your answers in the below comment box.

Test Planning – Step by Step – Part 1

After finalization of possible test for current project, Test Lead category people concentration on test plan document preparation to define work allocation in terms of What, Who, When & How to test. To prepare test plan document, test plan order follows below approach.
Test Planning - Step by Step

1] Team Formation:
In general, Test planning process starts with testing team formation. To define a testing team, test plan author depends on below factors;
1. Availability of testers
2. Test duration
3. Availability of test environment resource

Loadrunner Introduction, How Loadrunner Works

We already discuss – Why performance Testing is Required and limitations of Manual Testing in Performance Testing. In this topic, we will discuss the process of Loadrunner Testing.
Read previous Article here:

Some Useful File System Scripts for QTP – Automation Testing

FSO stands for Files system object, during testing we need to do some basic task like add, move, copy, create and delete folders and files. We can also handle drives related things using File system object method. So It is very much important to learn File system object.

Below are some Useful QTP File System Scripts:

Guide to Useful Software Test Metrics

I) Introduction
When we can measure what we are speaking about and express it in numbers, we know something about it; but when we cannot measure, when we cannot express it in numbers, our knowledge is of a meager and unsatisfactory kind: it may be the beginning of knowledge, but we have scarcely, in your thoughts, advanced to the stage of science.

Why we need Metrics?

“We cannot improve what we cannot measure.”
“We cannot control what we cannot measure”

  • Take decision for next phase of activities
  • Evidence of the claim or prediction
  • Understand the type of improvement required
  • Take decision on process or technology change
II) Type of metrics
Base Metrics (Direct Measure)

Base metrics constitute the raw data gathered by a Test Analyst throughout the testing effort. These metrics are used to provide project status reports to the Test Lead and Project Manager; they also feed into the formulas used to derive Calculated Metrics.
Ex: # of Test Cases, # of Test Cases Executed

Calculated Metrics (Indirect Measure)

Calculated Metrics convert the Base Metrics data into more useful information. These types of metrics are generally the responsibility of the Test Lead and can be tracked at many different levels (by module, tester, or project).
Ex: % Complete, % Test Coverage

Are you a software testing expert?

Are you thinking that you are a Software Testing Expert? Answer below questions in comments and judge yourself. For answers, select only one option and explain why you choose this option.
By – Anaya Johri

Lets Make Software Testing Fun

Article by – -
I have been in software testing for quite some time, at times it sucked, because usually its boring and sometimes the testing activity is looked down as a menial job done by a less skilled person.
Lets make an attempt to overcome the above mentioned sucking factors. To implement them, apart from individual testers effort,a large and important part has to be played by the management.

i. Testers right attitude: First realize how important testing activity is.No matter how much developing effort has been spent on making a highly desirable product with state of the art technology, if it does not correctly do what it is supposed to do, then it is doomed to death.An improperly tested application reaching customers directly translates to loss of business.

Revolutionizing the Testing Process and Accuracy: The Decision Model [Testing Webinar]

The Relational Model changed the way we manage data. Today, the Decision Model organizes business rules and logic in a similarly rigorous manner.  This webinar with Barbara von Halle and Larry Goldberg discusses how the Decision Model enables innovation in the way we can generate test cases, minimize the testing needed, test the logic prior to coding, and assure completeness of testing procedures.

Testing without Requirements?

[Author - Surbhi Shridhar] Are you doing testing without requirements? Are you doing testing as per the instructions given by development team? In this post we will discuss – 1. Some common risks/issues that you might face while testing the software without requirements, 2. Ways to tackle those risks and 3. Alternative ways of testing.


(Just found an excellent article for testers.. via @ [A must read article for Test Leads, and testers]
Building trust may seem mysterious—something that just happens or grows through some unknowable process. The good news is there are concrete actions that tend to build trust (and concrete actions that are almost guaranteed to break down trust).

Dummies Guide to Performance Testing | Performance Testing Life Cycle

On Readers Request, we are starting the series of “Dummies Guide to Performance Testing”. This is the first post, where we will go through the basics of Performance Testing:
What is Performance Testing?
Why Performance Testing?
Tests carried out in Performance Testing
When to start Performance Testing?
Performance Test Process

Test progress Monitoring, Reporting & Control

Test progress monitoring
The purpose of test monitoring is to give feedback and visibility about test activities. Information to be monitored may be collected manually or automatically and may be used to measure exit criteria, such as coverage. Metrics may also be used to assess progress against the planned schedule and budget.

Launching Testing Application on Facebook

Dear Readers,

Finally we launched our blog application on facebook :). This application will help you track all the top stories, software testing tips and tutorials from the Software Testing Times right in your Facebook profile.
Link -
All you need to click on “Like” and then click “Go to Application”. Application will be activated.
Direct Link is given above. Other way is to:

Security Testing Fundamentals

Exposing systems to the internet increases the risk that security weaknesses in those systems will be leveraged to compromise the system or the underlying data. It is therefore necessary to examine the actual business risks this brings, understand the basic difficulties in implementing "secure systems", and adequately test internet applications for security, as well as functionality and load performance, before they are exposed to the net.

Click Here to Download the Whitepaper. ( via @ appLabs)
Security Testing Fundamentals -

Need for Security Testing

Need for Security testing
Five Principles Needing to Test -

Reducing test case documentation time

by - Ranjit Shewale
This article describes about the approach to reduce documentation and correction overhead of test cases for the test team so they can spend more time on creating
innovative test cases and actual testing. This also leads to a structured documentation approach of test case during the test case preparation phase.

Ask yourself
1. How much time does your team spend in documenting test case?
2. How much time do you spend in internal reviews?
3. How much time do you spend in correcting it?
4. How much time do you spend in correcting the test cases if the client sends across the review comments prior to signing it off?
If the answer to above is ‘most of the time’, then you need a structured approach to test documentation.
Why would you want to save the time?

Funny video on load testing with WebLOAD, Great QA humour

A Must Watch..
Funny video on load testing with WebLOAD,
Great QA humor. WebLOAD Professional is RadView's award winning software for performance testing and load testing of Internet applications.

Improving Test Effectiveness Using Fact-Based Test Prioritization

by – Impetus Knowledge Center (via Apeksha Bobde)
Testing is emerging as a very critical component in the product development life cycle and effective testing is being talked about as the key to better quality products, delivered on-time to the market.
Today, organizations spend several hours in testing their products for problems. The testing team creates hundreds of test cases to validate the requirements that are being developed. The test suites that are created often grow over time, requiring companies to conduct tests that need to run manually—a process that takes hours to execute. Many of the tests that get added to the test suites may be redundant, or simply non-productive. Often the tests target the areas..

Understanding QEngine’s Load Testing Process

Once you plan your load test, the next step is to perform the load testing process. Load testing is the process of identifying performance bottlenecks in your web application under normal and peak loads. This will help you to tune the resources (both the hardware and the software) of your web application and optimize the user experience for maximum performance.
Following are the steps involved in QEngine Load Testing process:

Basics of Test Effort Estimation

- By Murali Chemuturi
Why Testing is carried out? Why Software Testing is important? Testing is carried out primarily for unearthing any defects present in the system and to prevent a defective product reaching the customers. Secondarily, testing is also carried out to convince the customer that the product conforms to and fulfills the specifications and the functionality agreed to.

Software Testers | Guide to Answer some Toughest HR Interview Questions

Many times it happens that testers (or other professionals) crack the technical interview round, but they are not able to clear HR round successfully. So on readers request, we are posting some “General Guidelines in Answering Interview Questions”.

Webinar on Selenium – The most powerful Open source Test Automation tool

Free Webinars by -

About KavinSchool -
Kavin School offers low cost Selenium Automation Testing Tool training for the students who have no or prior experience in Selenium. If you have already have experience is Selenium. Look for various techniques provided during the training which will eliminate the number of hours you spent to figure out to solve a specific problem. The training is designed to meet both novice as well as advanced users to learn Selenium easily and get confident to attend the interviews.

QTP Unplugged book @ just Rs. 417 (INR)

Good News for Indian QTP lovers. Tradus Books is offering Quicktest Professional Unplugged book by Tarun Lalwani @ 417 INR + Free shipping
HP QuickTest Professional is a functional test automation tool. It supports a Record and Playback framework out of the box, where we can record and capture our interactions with the application under test and then replay those actions later. With this book you will learn - Basic concepts of QTP - Working without Object repository using Descriptive Programming - Advanced concepts of QTP - Working with external tools Microsoft Word, Outlook, Excel - Integrating QTP Scripts with Quality Center - Real life Automation problems and their solutions.
You can get the book here -
Read Book review here:

Software Testing Templates for download

On readers request, we are posting following software testing templates which use can use in your projects:
1. Sample Software Tester Resume Template
2. Software Test Plan Template
3. Software Test Report template
4. Use Case Template
5. Software Testing Checklist Template
6. Software Test Strategy Template
7. Requirements Traceability Matrix template
8. Test Case Template
You can download the templates from following links:

Testing Planning & Strategy – The Do’s and The Dont's

Neatly document the test plan and test strategy for the application under test. Test Plan serves as the basis for all testing activities throughout the testing life cycle. Being an umbrella activity this should reflect the customers needs in terms of milestones to be met, the test approach (test strategy), resources required etc. The plan and strategy should give a clear visibility of the testing process to the customer at any point of time.
Functional and Performance test plans if developed separately will give lot more lucidity for functional and performance testing. Performance test plan is optional if the application does not entail any performance requirements.

Below are some useful Do’s and Don'ts:

Test Case Review Process & Tips

The main reason of the reviewing test cases: increase test coverage and therefore product quality.

As we know testers are involved on the Requirements Specification review process to provide the SQA knowledge to the requirements written. As testers are involved on the process they become experts on the area and on the application functionality and many times their knowledge helps avoid introducing future defects into the functionality that later the developer will code (it’s the phase that we called: defect prevention).

Principles Behind the Agile Manifesto

The Agile Manifesto is a statement of the principles that underpin agile software development:

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

The QA team may want to add one more principle to the Agile Manifesto

Craftsmanship over Execution: This is meant to focus software developers on creating good code vs. simply writing code that barely works. Both craftsmanship and execution are good things, but taking care to create good code is viewed as more important from testers and customers point of view.

Difference between IBM Rational Functional Tester & Rational Robot

Difference between Rational Functional Tester & Rational Robot:

Rational Functional Tester is an automated functional testing and regression testing tool.
Provides testers with automated testing capabilities for functional testing, regression testing, GUI testing and data-driven testing.

Testers are brave? or Developers are brave?

Testers are brave? or Developers are brave?
Today, I got two images from the web..

Regression Testing and its best practices

Regression Testing: "What" to test and "When"

Regression testing is often seen as an area in which companies hesitate to allocate resources. We often hear statements such as: "The developer said the defect is fixed. Do we need to test it again?" And the answer should be: "Well, the developer probably said the product had no defects to begin with." The truth of the matter is, in today's world of extremely complex devices and software applications, the quantity and quality of regression testing performed on a product are directly proportional to the commitment vendors have to their customer base. This does not mean that the more regression testing, the better. It simply means that we must make sure that regression testing is done in the right amount and with the right approach.

Some Performance Testing Mistakes & their solutions

Changed the Title of this post from " Top 10 Performance Testing Mistakes &  their solutions" to "Some Performance Testing Mistakes &  their solutions". Refer comments for this.

1 Incorrect Load Levels
Fix: Improve and focus communications by conducting a one-on-one interview to determine expected “real world” load levels. If the application is already in production, obtain live usage data.

2 Performance Tester Identifying Key Business Processes
Fix: Conduct a one-on-one interview to identify key business processes: mission critical, heavy throughput, dynamic content, and any other business process that causes concern.

Exploratory Testing (Public) Workshop in Noida (June 19, 2010) by Pradeep Soundararajan

Here is an opportunity for you to meet Pradeep in Noida (India- Delhi, NCR). Pradeep is delivering a public workshop on Exploratory testing. I am waiting for his workshop from a long time. [I already registered :) and I am very excited to meet him :)]. It is a great opportunity for me to judge myself and learn new things.
For those who don't know about Pradeep – Pradeep has played a pivotal role in inspiring testers to better their skills. He is among one of the most demanding Test Consultant.

I personally suggest that testers should attend his workshop. You can contact him through his blog for the workshop details and payment details.

QTP GetTOProperty, GetToProperties, SetTOProperty & GetROProperty Simplified

Retrieving and Setting Test Object Property Values - Following are the pre-defined ways to retrieve and set values of test objects:
The GetTOProperty returns the value of the property from the test object's description, i.e., the value used by QTP to identify the object. It returns the value of a property for a test object which QTP recorded to identify during the recording (run time).
The GetTOProperty command will retrieve the value as it was originally recorded (or created via DP). It does not matter if the corresponding runtime object exists, or if that value was updated in "the real world" since the object was recorded.

Responsibilities & Qualities of a Lead Automation Test Engineer

Responsibilities & Qualities of a Lead Automation Test Engineer are:
The Senior Test Automation Engineer will lead the effort to build new test frameworks and or extend existing frameworks. The tool/s accommodates both functional and load testing. These frameworks allow us to perform end-to-end testing in multi-component environments. He will working with the test engineers to design and develop a reusable architecture for the test automation. The Framework or Automation Architecture should consists the following:

Responsibilities & Qualities of an Automation Test Engineer

Responsibilities for Automation Test Consultants may include:
* Establish an automated test environment for UI and non-UI testing
* Review test cases and automate whenever possible
* Educate team members on test automation and drive adoption
* Integrate automated test cases into nightly build system
* Design, document, manage and execute test cases, sets, and suites
* Work in cross-functional project teams that include Development, Marketing, Usability, Software Quality Assurance, Customer Learning, and Support.

Challenging Test Automation Questions – Judge Yourself

1. Our software designers use UML for modelling applications. Based on their use cases, we would like to plan a test strategy. Do you agree with this approach or would this mean more effort for the testers?

Load/Performance Testing Limitations with Manual Testing

Have you ever tried to test performance testing manually? or Are you performing load testing manually? Do you know its drawbacks? If you doing load/performance testing manually then it might let costly failures of Mission-critical applications.

LoadRunner Tips

Note – These tips are very helpful. most of them are taken from

1. To get the password of an auto-generated lr_decrypt() function:
char * password;
web_set_user("2testuser", lr_decrypt("41754c8245221983220368db"),"");

2. Problem Description: How to capture the total bytes of a request/response from the server

Solution: Use the web_get_int_property function
In VuGen 8.1, there are additional options available for the web_get_int_property function like HTTP_INFO_TOTAL_REQUEST_STAT and HTTP_INFO_TOTAL_RESPONSE_STAT. These options return the accumulative size (including header and body) of requests and responses.
Related articles that may be of interest:
Problem ID 29810 - How to verify the size of the last download in bytes
Problem ID 23220 - How to capture HTTP return code information

Record on LoadRunner’s VuGen using a QTP script - Automation testing Tip

1. Bring up VuGen. Create a New script selecting Web (HTTP/HTML) protocol.

2. Start record button.

3. Then, bring up QTP and make sure the option on “Record and Run Settings” dialog be with– Record and Run test on any Open web browser, radio button.

4. Start ‘Record’ on QTP and perform the user activities on the browser invoked by the VuGen.

5. Both VuGen and QTP would record the actions on their interfaces.

This way we can make sure the VuGen to record the same sequence of user actions/events by ‘Replaying’ the QTP recorded script, after a browser is initiated by the VuGen’s recording engine.

Tester’s Mental Life

 Software Tester Mental Life
Boris Beizer, identified five phases of a tester’s mental life:
Phase 0: There’s no difference between testing and debugging. Other than in support of debugging, testing has no purpose.
Phase 0 Thinking: Testing = Debugging.

Automation Testing LifeCycle/Process Simplified

Automation Testing LifeCycle
Phase Activities Outcome
Planning Create high level test plan Test plan, Refined Specification
Analysis Create detailed test plan, Functional Validation Matrix, test cases Revised Test Plan, Functional validation matrix, test cases
Design test cases are revised; select which test cases to automate revised test cases, test data sets, sets, risk assessment sheet
Construction scripting of test cases to automate, test procedures/Scripts, Drivers, test results, Bug Reports.
Testing cycles complete testing cycles Test results, Bug Reports
Final testing execute remaining stress and performance tests, complete documentation Test results and different metrics on test efforts
Post implementation (See Post Project Reviews in testing) Evaluate testing processes Plan for improvement of testing process

Guidelines/Best Practices for effective Software Test Planning – Part 2

Test Plan First

Following are the guidelines/best practices for effective test planning:
  • Identify the requirements to be tested. All test cases shall be derived using the current Design Specification.

Purpose & Advantages of Test Plan

 Test Plan First



  • The test plan keeps track of possible tests that will be run on the system after coding.
  • The test plan is a document that develops as the project is being developed.
  • Record tests as they come up
  • Test error prone parts of software development.
  • The initial test plan is abstract and the final test plan is concrete.
  • The initial test plan contains high level ideas about testing the system without getting into the details of exact test cases.
  • The most important test cases come from the requirements of the system.
  • When the system is in the design stage, the initial tests can be refined a little.
  • During the detailed design or coding phase, exact test cases start to materialize.
  • After coding, the test points are all identified and the entire test plan is exercised on the software.

Purpose of Software Test Plan:

  • Test Plan Ensures all Functional and Design Requirements are implemented as specified in the documentation.
  • To provide a procedure for Unit and System Testing.
  • To identify the documentation process for Unit and System Testing.
  • To identify the test methods for Unit and System Testing.

Advantages of test plan

  • Serves as a guide to testing throughout the development.
  • We only need to define test points during the testing phase.
  • Serves as a valuable record of what testing was done.
  • The entire test plan can be reused if regression testing is done later on.
  • The test plan itself could have defects just like software!
In software testing, a test plan gives detailed testing information regarding an upcoming testing effort, including
  • Scope of testing
  • Schedule
  • Test Deliverables
  • Release Criteria
  • Risks and Contingencies

Test Plan Preparation Guidelines – Part 1

The software test plan is the primary means by which software testers communicate to the product development team what they intend to do. The purpose of the software test plan is to prescribe the scope, approach, resource, and schedule of the testing activities. To identify the items being tested, the features to be tested, the testing tasks to be preformed, the personnel responsible for each task, and the risks associated with the plan.
The test plan is simply a by-product of the detailed planning process that’s undertaken to create it. It’s the planning that matters, not the resulting documents. The ultimate goal of the test planning process is communicating the software test team’s intent, its expectations, and its understanding of the testing that’s to be performed.

Classic Test Automation Mistakes

There are many good reasons to start automation. But sometimes – Companies start automation testing with enthusiasm but end up with manual testing only. Below are 5 mistakes that management might do while implementing automation:

QTP Automation Object Model Simplified | QTP AOM

We received couple of queries on QTP AOM. In this post we simplified the QTP AOM, so that a newbie in QTP can also understand what is Automation Object Model and how it works.

Rate Yourself in Software Testing | Skills of a Professional Tester | Lets become Test Professional from Test Dummies.

Today employers want test professionals – not test dummies. There are unique skills of testers that are highly desired by employers to make the testing process more efficient and effective. See the checklist for a cross-section of the desirable skills of a test professional

Effective Practical Test Reporting Tips & Techniques | Software Testing Summary Reports Generation

Testing is very important phase in the Life Cycle of Software Development so whatever the work testers and test lead are doing in this Phase it should be properly documented and testers should be able to provide the needful information in proper Reports. Here are some important documents, their frequency and the reason for those documents have a look at it:

Tips to Prioritizing the tests | A way to achieve Time-boxing in testing

A common problem is faced in testing phases (especially when UAT/release is near) - There are so many tests for testing/execution but there is so less time. In 2004, Johanna Rothman gives a recipe in her article "So Many Tests, So Little Time
| TimeBox the testing". From Johanna’s article, I conclude that Prioritizing the tests is one important step to achieve time-boxing in testing.

For those who don’t know what is time-boxing:
Time-boxing is a well-established project management (time management technique) used to limit project scope in a fixed duration by forcing tradeoffs. Time-boxing is a valuable technique for testing as well. For example you need to test the application before UAT and there are only 4 weeks left.

Choosing right scripting technique/Framework for Automation Testing

While planning for automation testing for any project, a tough question for Testing automation engineers are – “Which automation scripting techniques or framework should be chosen?”

Selenium for Functional testing of web applications

Functional testing and black box is a methodology used to test the behavior that has an application from the viewpoint of their functions, validated for this purpose various aspects ranging from the aesthetics of the front end, the navigation within your pages between pages within the forms, the compliance of technical specifications associated with fields, buttons, bars, among other pages, entry permits and access to consultations and modifications, management of parameters, the management of the modules that constitute , and other conditions that make up the various "features" expected to provide the system to operate the end user as a normal and correct.

Types of Software errors and bugs | Most Common Software bugs

by Padmini C (Author of Beginners guide to Software Testing)

Following are the most common software errors that aid you in software testing. This helps you to identify errors systematically and increases the efficiency and productivity of software testing. This topic surely helps in finding more bugs more effectively :) . Also, you can use this as a checklist while preparing test cases and while performing testing.

Measuring Software test effectiveness

The main objectives of testing are to establish confidence and to find defects. This article describes some measures for test effectiveness.
Defect Detection Percentage (DDP)
DPP = Defects known by testing/Total Known Defects

HP WinRunner exam HP0-M12 sample questions

HP WinRunner exam HP0-M12 sample questions. These questions will definitely help you is passing the exam with good score.

Step by Step guide to Test Case Development

 .. Continuing the Beginners Guide to Software Testing series
est Case is a commonly used term for a specific test. This is usually the smallest unit of testing. A Test Case will consist of information such as requirements testing, test steps, verification steps, prerequisites, outputs, test environment, etc.

A Test Case is:
- A set of inputs, execution preconditions, and expected outcomes developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement.

- A detailed procedure that fully tests a feature or an aspect of a feature. Whereas the test plan describes what to test, a test case describes how to perform a particular test. You need to develop a test case for each test listed in the test plan.
Test cases should be written by a team member who understands the function or technology being tested, and each test case should be submitted for peer review.

Organizations take a variety of approaches to documenting test cases; these range from developing detailed, recipe-like steps to writing general descriptions. In detailed test cases, the steps describe exactly how to perform the test. In descriptive test cases, the tester decides at the time of the test how to perform the test and what data to use.

Software Testing Techniques

Test Design Techniques

The purpose of test design techniques is to identify test conditions and test scenarios through which effective and efficient test cases can be written.Using test design techniques is a best approach rather the test cases picking out of the air. Test design techniques help in achieving high test coverage. In this post, we will discuss the following:
1. Black Box Test Design Techniques
  • Specification Based
  • Experience Based
2. White-box or Structural Test design techniques

Difference between Test Plan and Test Strategy | Do we really need Test Plan documents?

In this post we will discuss:
  • Difference between Test Plan and Test Strategy (by both theoretically as per IEEE829 and practically, i.e. what actually happens in testing projects) in brief and simple manner.
  • Do we really need Test Plan documents?

Tricky Software testing Terms

What is Ramp Testing? - Continuously raising an input signal until the system breaks down.
What is Depth Testing? - A test that exercises a feature of a product in full detail.
What is Quality Policy? - The overall intentions and direction of an organization as regards quality as formally expressed by top management.
What is Race Condition? - A cause of concurrency problems. Multiple accesses to a shared resource, at least one of which is a write, with no mechanism used by either to moderate simultaneous access.

SQL For Testers – Part 2

After reading part 1, now you are aware of –
  • Why database testing is necessary?
  • Differences between backend testing and front end testing
  • Backend testing phases / Database Testing Phases
  • Backend test methodology / Database Testing methodology
  • Basics of SQL
Now lets put more focus on SQL Statements -

V Model to W Model | W Model in SDLC Simplified

We already discuss that V-model is the basis of structured testing. However there are few problem with V Model. V Model Represents one-to-one relationship between the documents on the left hand side and the test activities on the right. This is not always correct. System testing not only depends on Function requirements but also depends on technical design, architecture also. Couple of testing activities are not explained in V model. This is a major exception and the V-Model does not support the broader view of testing as a continuously major activity throughout the Software development life-cycle.

Selenium Interview Questions

Posting the Interview questions of Selenium - Automated Software Testing Tool..

Software Testing Checklist - Major Areas of Testing - What to Look at?

In this post we will discuss the points to take care while testing following applications:
  • PRINTERS AND DRIVERS – Interface software

CSTE Sample Papers | CSTE Sample Questions

On Readers request, I am posting CSTE Certification practice questions.

CSTE Certification Essay based questions:
1. What fields would you include in creating a new defect tracking program (used by QA, developers, etc)? (25 points)
a. Draw a pictorial diagram of a report you would create for developers to determine project status.
b. Draw a pictorial diagram of a report you would create for users and management to show project status.
2. What 3 tools would you purchase for your company for use in testing and justify why you would want them? (this question is in both essay parts, only rephrased. I think 10 points each time)

Asnwers to advanced software Testing Interview Questions

Ans 1: Advantages of path coverage metric of software testing:
Path coverage requires extremely thorough testing.
Disadvantages of path coverage metric of software testing:
1) Since loops introduce an unbounded number of paths, this metric considers only a limited number of looping possibilities.
2) The number of paths is exponential to the number of branches. For example, a function containing 10 if-statements has 1024 paths to test. Adding just one
more if-statement doubles the count to 2048.
3) Many paths are impossible to exercise due to relationships of data.

Advanced Software Testing Interview Questions – Part 1 (Advanced Level)

Below are some advanced level/ Test lead level Software Testing Questions. Answer now and Judge yourself.

Tips for Software Testing Resume

The purpose of this article to show you how to write a Software Testing Resume which get the most out of your qualifications.  A good software tester resume helps you articulate your skills and opens the door for a job interview. 
Lets Check the Sample Software Testing Resume below:

Bug triage Meeting Process

.. Continuing the Test Management Series
Bug Triage Meeting -
A meeting held by the CFT**, QA Group, Test Manager, Quality Manager, Project Manager; Product Manager and Testing Leads for any project. The objective of the meeting is to prioritize and track the defects to be addressed, ensuring timely and accurate resolution. During iterative Quality Assurance testing, the QA department logs defects. In Bug Triage, the bugs are prioritized to determine when bug fixes are to be releases, the difficulty of the fix and the difficulty of retest.
[**CFT - Cross Functional Team - An inter-departmental team comprising a Cross-Functional Team Leader and team members representing a network of experienced and knowledgeable staff members. The Cross-Functional Team concept allows staffing levels for each development discipline to increase and decrease at the proper times during the development cycle.]

How and When Testing Starts

.. Continuing the Beginners Guide to Software Testing series
For the betterment, reliability and performance of an Information System, it is always better to involve the Testing team right from the beginning of the Requirement Analysis phase. The active involvement of the testing team will give the testers a clear vision of the functionality of the system by which we can expect a better quality and error-free product.

Once the Development Team-lead analyzes the requirements, he will prepare the System Requirement Specification, Requirement Traceability Matrix. After that he will schedule a meeting with the Testing Team (Test Lead and Tester chosen for that project). The Development Team-lead will explain regarding the Project, the total schedule of modules, Deliverable and Versions.

The involvement of Testing team will start from here. Test Lead will prepare the Test Strategy and Test Plan, which is the scheduler for entire testing process. Here he will plan when each phase of testing such as Unit Testing, Integration Testing, System Testing, User Acceptance Testing. Generally Organizations follow the V – Model for their development and testing.

Requirement Specification document Review Guidelines and Checklists

To prepare effective test cases, testers and QA engineers should review the software specs documents carefully and raise as much queries as they can.
The purpose of Software Requirement Specification Review is to uncover problems that are hidden within the specification document. This is a part of defect prevention. These problems always lead the software to incorrect implementation. So following guidelines for a detailed specification review is suggested:

Role of a tester in defect prevention and defect detection

Some Testers (especially beginners) often get confused with this Question - “What is the role of a tester in Defect Prevention and Defect Detection?”. In this post we will discuss the role of a tester in these phases and how to testers can prevent more defects in Defect Prevention phase and how testers can detect more bugs in Defect Detection phase

HP QTP Certification HP0-M016 Exam Sample Question Bank

Question Bank:
1. QTP workflow Phases
2. what are the conditional statements provided in QTP?
3. Break point is used to :
4. What is the first step to change the logical name of the object recorded by Quick test?
5. Where can you find the result of an output parameter?
6. Where do you set action iterations for a specified action?
7. which of the following is created by default with new action?
8. What are the default addins provided by QTP?
9. Which source property specifies that data is retrieved from database?
10. Local object Repository is used for Single action tests.
11. shared object Repository is created in Object Repository Manager.
12. which tool is used to merge two shared object repositories.
13. Low level Recording is used to record:
14. virtual objects are stored in : dat folder…
15. bitmap checkpoint takes into consideration:
16. When using recovery scenario wizard ,the first phase is to specify : Trigger
17. Trigger events : popup window,object state, test run error,application crash

QTP Sample paper - Part 14 - **** Mostly asked questing in QTP Certification - 5...

1) You cannot expand ...... actions from the test flow
A) reusable
B) non-reusable
C) both A & B
D) None

2) You can associate shared object repositories with
...... actions simultaneously, using the Associate
Repositories dialog box
A) seven
B) Two
C) Three
D) Multiple

QTP Sample paper - Part 13 - **** Mostly asked questing in QTP Cerification - 4...

1. When a procedure is created in the Function Library editor, what is the extension on the file?


2. What are the categories in the Step Generator?

A. Object, Operation, Value
B. Library, Built-in, Local Script
C. Operation, Arguments, Return Value
D. Test Objects, Utility Objects, Functions

QTP Sample paper - Part 12 - **** Mostly asked questing in QTP Cerification - 3...

1) You can import and export object repositories from
and to .... files.

2) In general, the ....... object repository is
easiest to use when you are creating simple record and
run tests.
A) Shared
B) Local
C) Both
D) None

3) The Object Repository automation object model
enables you to manipulate QuickTest ....... object
repositories and their contents from outside of
A) Shared
B) Local
C) Both
D) None

QTP Certification HP0-M16 Practice Questions - Set 10

91) An ........ assigns a numerical value to a test object that indicates its order or location relative to other objects with an otherwise identical description (objects that have the same values for all properties)
A) Index identifier.
B) ordinal identifier.
C) SMART ID identifier.
D) original identifier.

92) You can add an object to the local object repository only if that object does not already exist in a shared object repository that is associated with the action. If an object already exists in an associated shared object repository, you can add it to the local object repository using the ........ option.
A) Copy from Shared Repository
B) Copy from Shared Object Repository
C) Copy to Local
D) Copy to Local repository

QTP Certification HP0-M16 Practice Questions - Set 9

81) In the Object Repository window:.
A) Local objects are editable (black)
B) Shared objects are in read-only format (gray)
C) Local objects are in read-only format (gray)
D) Shared objects are editable (black)

82) Mark true statement(s):.
A) You can delete objects from a shared object repository using the Object Repository window.
B) You can delete objects from the local object repository using the Object Repository Manager
C) You can delete objects from the local object repository using the Object Repository window
D) You can delete objects from a shared object repository using the Object Repository Manager

QTP Certification HP0-M16 Practice Questions - Set 8

71) QuickTest processes a comments when it runs a test.

A) True
B) False

72) Press ..... to add a new step below the currently selected step.

A) F8
B) Shift + A
C) F0
D) Shift + A + Q

73) While working with the Keyword View, you can ...... steps to move
them to a different location in a test or in an action

A) Copy and Paste
B) Cut and Paste
C) Drag and drop
D) Both A) and C)

QTP Certification HP0-M16 Practice Questions - Set 7

Read QTP Certification sample Questions – Part 6
61) You can use the Keyword View to add a step your test.

A) at the end
B) below the currently selected step
C) at the beginning
D) at anypoint

62) The Documentation cell is .............

A) Read-only
B) Write-only
C) Read and Write
D) Read, write & execute

QTP Certification HP0-M16 Practice Questions - Set 6

Read QTP Certification sample Questions – Part 5
51) Using the Object Spy, you can view

A) the run-time or test object properties and methods of any object in
an open application.
B) the run-time or test object properties of any object in an open
C) the test object properties and methods of any object in an open
D) the run-time object properties and methods of any object in an open

52) There are .........object type filters in Object spy dialog box.

A) Two
C) Four
D) Five

QTP Certification HP0-M16 Practice Questions - Set 5

Read QTP Certification sample Questions – Part 4
41) Object Spy can be found in

A) Tool
B) Tools
C) Task
D) Tasks

42) ............ displays the open documents side-by-side.

A) Tile Vertically
B) Tile Horizontally
C) Cascade
D) Tile Cascade

43) For opening the QuickTest Professional Help we can use.......

A) F3
B) F5
C) F1
D) F2

QTP Certification Practice Questions - Set 4

31) You can manage the test actions and the test or function library
steps using the ... menu commands

A) File
B) Edit
C) Automation
D) Tools

32) To expand all the steps in the keyword view which option you would
use from the View menu.

A) Expand
B) Expand All
C) Expand Items
D) Expand Rows

QTP Certification Practice Questions - Set 3

21) Panes in QTP can have one of the following states—docked or floating.

A) True
B) False

22) Which of the following statement is True:

A) QuickTest enables you to open and work on one test at a time
B) QuickTest enables you to open and work on two tests at a time
C) QuickTest enables you to open and work on predefined number of tests
at a time
D) QuickTest enables you to open and work on nine test at a time

23) Which of the following statement is True:

A) You can open and work on two function libraries simultaneously
B) You can open and work on multiple function libraries simultaneously
C) You can open and work on nine function libraries simultaneously
D) You can open and work on one function library at a time

QTP Certification Practice Questions - Set 2

Read QTP Certification sample Questions – Part 1
11) The Information pane provides a list of............. in the test:

A) Semantic errors
B) Syntax errors
C) Common errors
D) Logic errors

12) When we switch from Expert view to the Keyword view, QTP
automatically checks for syntax errors in the test and shows them in the
information pane.

A) True
B) False

13) If the information pane is not open, QTP automatically opens it in
case a syntax error is detected.

A) True
B) False

QTP Certification Practice Questions - Set 1

QTP Questions 1

1) 'Browser navigation timeout' is in which tab of Test Settings
(File Settings) window.

A) Properties
B) Resources
C) Web
D) Web Settings

2) How many tabs are there in Test Settings (File->Settings) window

A) 7
B) 6
C) 5
D) 8

3) Identify the tabs in the Test Settings (File->Settings) window

A) Properties, Run, Resources, Parameters, Environment, Web, Recovery
B) Properties, Run, Resources, Parameters, Environment, Web
C) Properties, Run Options, Resources, Parameters, Environment, Web,
D) Properties, Run, Resources, Input Parameters, Environment, Web, Recovery

When to Stop Testing | Testing Completion Criteria

.. Continuing the Beginners Guide to Software Testing series
Testing should be stopped when it meets the completion criteria. Now how to find the completion criteria? Completion criteria can be derived from test plan and test strategy document. Also, re-check your test coverage.
Completion criteria should be based on Risks. Testing should be stopped when -
  • Test cases completed with certain percentage passed and test coverage is achieved.
  • There are no known critical bugs
  • Coverage of code, functionality, or requirements reaches a specified point;
  • Bug rate falls below a certain level, now testers are not getting any priority 1, 2, or 3 bugs.
As testing is a never ending process we can never assume that 100 % testing has been done, we can only minimize the risk of shipping the product to client with X testing done. The risk can be measured by Risk analysis but for small duration / low budget / low resources project, risk can be deduced by simply: -
  • Measuring Test Coverage.
  • Number of test cycles.
  • Number of high priority bugs.

Game Testing Tips and Considerations

Author - unknown. [If you know the author, or if you are the author please contact us, we will update the  post]

Video games are also considered as software that needs sufficient testing before releasing in the market. In fact, many software developers want to become game developers.
Game testing is the process of verifying game environment and behaviour. Its occurrence in game development depends on its budget. High-budgeted projects test their products when the draft version is finished. On the other hand, low-budgeted games might only support testing of the probable final version. Other types like public betas and stress tests are also used in actual game industry, but it less systematic and scientific because testing is being done by simply playing the game from the start to finish and reporting random bugs that occur and detected accidentally. Scientific and methodological approaches in testing have the following purposes:

QTP Descriptive Programming - How to get number of objects

In this article, Dmitri Motevich explains QTP Descriptive Programming (DP) through Google Sets site:
The goal of the present QTP tutorial is to describe:
How to get number of controls (Links, Edits, Images, etc) with QTP DP.

Let's investigate Descriptive Programming on examples.First of all, we should understand what Descriptive Programming means:


QTP DP is a run-time processing of objects which are not located in QTP Object Repository.
I've created new QTP script which starts with page.

Tutorial Database Testing using SQL | SQL for Testers

The demand for "all round" testers, i.e. being able to test the system's functionality through traditional testing methods and being able to show some technical knowledge is growing.

Basics of Database testing contains the following:
1. How to connect to the database?
2. Ability to write simple queries to retrieve data and manipulate the data using DML operations.
3. Functional flow should be very well known!
4. Good knowledge on table level, column level constraints, ability to understand and execute complex queries related to joins is added advantage.
Contents of this tutorial:

Concept of Complete Testing | Exhaustive testing is impossible

.. Continuing the Beginners Guide to Software Testing series

It is not unusual to find people making claims such as “I have exhaustively tested the program.” Complete, or exhaustive, testing means there are no undiscovered faults at the end of the test phase. All problems must be known at the end of complete testing. For most of the systems, complete testing is near impossible because of the following reasons:
  • The domain of possible inputs of a program is too large to be completely used in testing a system. There are both valid inputs and invalid inputs.
    The program may have a large number of states. There may be timing constraints on the inputs, that is, an input may be valid at a certain time and invalid at other times. An input value which is valid but is not properly timed is called an inopportune input. The input domain of a system can be very large to be completely used in testing a program.
  • The design issues may be too complex to completely test. The design may have included implicit design decisions and assumptions. For example, a programmer may use a global variable or a static variable to control program execution.
  • It may not be possible to create all possible execution environments of the system. This becomes more significant when the behaviour of the software system depends on the real, outside world, such as weather, temperature, altitude, pressure, and so on.
[From book - Software testing and quality assurance: theory and practice By Kshirasagar Naik, Priyadarshi Tripathy]

Must Read: Testing Limitations
The Impossibility of Complete Testing by Dr. Cem Kaner

Testing Limitations

.. Continuing the Beginners Guide to Software Testing series
Testing Limitations
  • You cannot test a program completely
  • We can only test against system requirements
- May not detect errors in the requirements.
- Incomplete or ambiguous requirements may lead to inadequate or incorrect testing.
  • Exhaustive (total) testing is impossible in present scenario.
  • Time and budget constraints normally require very careful planning of the testing effort.
  • Compromise between thoroughness and budget.
  • Test results are used to make business decisions for release dates.
  • Even if you do find the last bug, you’ll never know it
  • You will run out of time before you run out of test cases
  • You cannot test every path
  • You cannot test every valid input
  • You cannot test every invalid input
Must ReadThe Impossibility of Complete Testing by Dr. Cem Kaner

Practical interview questions on Software Testing - Part 1

.. Continuing the Beginners Guide to Software Testing series
1. On which basis we give priority and severity for a bug and give one example for high priority and low severity and high severity and low priority?
Always the priority is given by team leader or Business Analyst. Severity is given by the reporter of bug. For example, High severity: hardware bugs application crash. Low severity: User interface bugs. High priority: Error message is not coming on time, calculation bugs etc. Low priority: Wrong alignment, etc
2. What do you mean by reproducing the bug? If the bug was not reproducible, what is the next step?
If you find a defect, for example click the button and the corresponding action didn’t happen, it is a bug. If the developer is unable to find this behaviour he will ask us to reproduce the bug. In another scenario, if the client complaints a defect in the production we will have to reproduce it in test environment.
If the bug was not reproducible by developer, then bug is assigned back to reporter or goto meeting or informal meeting (like walkthrough) is arranged in order to reproduce the bug. Sometimes the bugs are inconsistent, so that that case we can mark the bugs as inconsistent and temporarily close the bug with status working fine now.

Descriptive Programming in QTP

Descriptive Programming:

When we start recoding on any application with QTP, QTP learns the object by adding some of its properties in Object Repository. QTP uses default Object Identification properties: mandatory and assistive to learn objects. For more information on how QTP learn objects, read this article. and QTP Object Identification tutorial.
Whenever QTP records any action on any object of an application, it adds some description on how to recognize that object to a repository of objects called object repository. QTP cannot take action on an object until unless its object description is in the Object Repository.

But descriptive programming provides a way to perform action on objects which are not in Object repository.

Download the Descriptive Programming Tutorials for QTP.
Document 1: Download - Basics of Descriptive Programming in QTP. [Note - This is writtern by Tarun Lalwani using QTP 8.2. It is atill applicable to all QTP versions.. A must read]

Document 2: Converting OR (Object Repository) Based scripts to Descriptive Programming
Document 3: Descriptive Programming Dummy Properties
Document 4: General issues people face while using Descriptive Programming (DP) in QTP.

Author - Tarun Lalwani (

Related posts - Book Review QuickTest Professional Unplugged.

QTP: Object Repository, Descriptive Programming and Beyond

This excellent and self explained presentation is prepared by Prepared by: Igor Gershovich.
  • This presentation explains the following:
  • Object Repository vs. Descriptive Programming –what to use?
  • OR Pros and Cons
  • DP Pros and Cons
  • QTP Scripting Using Object Repository
  • QTP Scripting Using Descriptive Programming
  • Descriptive programming – when and why?
  • Different ways to work with objects
  • ChildObjects method – using Collection Object
  • Regular Expressions in Object Repository
  • TO, RO and .Object methods in QTP
  • Run-Time “Native” Object Properties/Methods  from AUT
  • Object Smart Identification

Equivalence Class Partitioning Simplified

.. Continuing the Beginners Guide to Software Testing series
Concepts:   Equivalence partitioning is a method for deriving test cases.  In this method, classes of input conditions called equivalence classes are identified such that each member of the class causes the same kind of processing and output to occur.
In this method, the tester identifies various equivalence classes for partitioning.  A class is a set of input conditions that are is likely to be handled the same way by the system.  If the system were to handle one case in the class erroneously, it would handle all cases erroneously.
Equivalence partitioning significantly reduces the number of test cases required to test a system reasonably.  It is an attempt to get a good 'hit rate', to find the most errors with the smallest number of test cases.
To use equivalence partitioning, you will need to perform two steps
1. Identify the equivalence classes
2. Design test cases

Gray Box Testing

.. Continuing the Beginners Guide to Software Testing series
Gray Box Testing -
  • It is just a combination of both Black box & white box testing.
  • It is platform independent and language independent.
  • Used to test embedded systems.
  • Functionality and behavioral parts are tested.
  • Tester should have the knowledge of both the internals and externals of the function
  • If you know something about how the product works on the inside, you can test it better from the outside.
Gray box testing is especially important with Web and Internet applications, because the Internet is built around loosely integrated components that connect via relatively well-defined interfaces. Unless you understand the architecture of the Net, your testing will be skin deep.
Go back to Test Design Techniques

White Box Testing

.. Continuing the Beginners Guide to Software Testing series
White Box Testing
  • Testing the Internal program logic
  • White box testing is also called as Structural testing.
  • User does require the knowledge of software code.
  • Testing all loops
  • Testing Basis paths
  • Testing conditional statements
  • Testing data structures
  • Testing Logic Errors
  • Testing Incorrect assumptions
Structure = 1 Entry + 1 Exit with certain Constraints, Conditions and Loops.
Logic Errors and incorrect assumptions most are likely to be made while coding for “special cases”. Need to ensure these execution paths are tested.

Test Design Techniques

Methods of Black box Testing

.. Continuing the Beginners Guide to Software Testing series
The following basic techniques are employed during black box testing:
  • Equivalence Class
  • Boundary Value Analysis
  • Error Guessing

Black Box Testing

.. Continuing the Beginners Guide to Software Testing series
What is Black Box Testing?
  • Test the correctness of the functionality with the help of Inputs and Outputs.
  • User doesn’t require the knowledge of software code.
  • Black box testing is also called as Functionality Testing.
  • Testers make sure that software is working as per the requirements.
It attempts to find errors in the following categories:
  • Incorrect or missing functions.
  • Interface errors.
  • Errors in data structures or external data base access.
  • Behavior or performance based errors.
  • Initialization or termination errors.
Read – Approaches used in Black Box Testing

Fault, Error and Failure

.. Continuing the Beginners Guide to Software Testing series
Fault : It is a condition that causes the software to fail to perform its required function.
Error : Refers to difference between Actual Output and Expected output.
Failure : It is the inability of a system or component to perform required function according to its specification.
IEEE Definitions
  • Failure: External behavior is incorrect
  • Fault: Discrepancy in code that causes a failure.
  • Error: Human mistake that caused fault
  • Error is terminology of Developer.
  • Bug is terminology of Tester

What Is Software Testing?

.. Continuing the Beginners Guide to Software Testing series
Definitions of Software Testing -
  • It is the process of Creating, Implementing and Evaluating tests.
  • Testing measures software quality
  • Testing can find faults. When they are removed, software quality is improved.
  • Testing is executing a program with an indent of finding Error/Fault and Failure.
  • IEEE Terminology : An examination of the behavior of the program by executing on sample data sets.

Why is Software Testing Important?

.. Continuing the Beginners Guide to Software Testing series
1. To discover defects.
2. To avoid user detecting problems
3. To prove that the software has no faults
4. To learn about the reliability of the software.
5. To avoid being sued by customers
6. To ensure that product works as user expected.
7. To stay in business
8. To detect defects early, which helps in reducing the cost of defect fixing?

Read – Why start testing early?

Defect Density

Defect Density
What are various ways of calculating defect density?
The formula itself is simple: Density = Total Defects Found / Size
if we see defect density at granular level say Codesize of a particular functionality X in a application Y along with number of files, then we may draw some good observations like -

Mercury Quality Center Interview Questions

1. What is meant by test lab in Quality Centre?
Test lab is a part of Quality Centre where we can execute our test on different cycles creating test tree for each one of them. We need to add test to these test trees from the tests, which are placed under test plan in the project. Internally Quality Centre will refer to this test while running then in the test lab.
2. Can you map the defects directly to the requirements(Not through the test cases) in the Quality Centre?
In the following methods is most likely to used in this case:
  • Create your Req.Structure
  • Create the test case structure and the test cases
  • Map the test cases to the App.Req
  • Run and report bugs from your test cases in the test lab module.
The database structure in Quality Centre is mapping test cases to defects, only if you have created the bug from Application. test case may be we can update the mapping by using some code in the bug script module(from the customize project function), as per as i know, it is not possible to map defects directly to an requirements.

HP0 M15 Quality Center Certification Questions

HP0 M15 Quality Center Certification sample Preparation Questions:
1) Quality Center is
- an ERP
- a standalone software
- a web based (client/server) tool
- a script
2) Traceability Alert is depicted with "@" Mark against a Test
- Yes
- No