Entries Tagged 'Software Testing Templates' ↓

Software Testing Status Reporting:

“The agreement that a certain information, in a certain format, will be sent by a certain team/individual, at certain intervals of time, to certain members – is like a handshake- an acknowledgement that no matter what the outcome of a task at hand, you would be kept posted about it, sooner than later.”

This is the first section of an IT professional’s oath. Well, I’m kidding! There is no oath, but if there was one, this would surely top the list of items in it. Isn’t it?

Accountability and transparency (A & T) are essential to every IT project at various levels – Project level, team level, task level and also individual Continue reading →

I keep getting several requests to share a good Test Case Template. And I’m surprised that many testers are still documenting test cases with Word docs or Excel files. Most of them prefer excel spreadsheets because they can easily group test cases by test types and most importantly they can easily get test metrics with the Excel formulas. But I’m sure that as the volume of your tests goes on increasing, you will find it extremely difficult to manage.

If you are not using any test case management tool, then I would strongly recommend using an open source tool to manage and execute your test cases.  Continue reading →

A strategy plan for defining the testing approach, what you want to accomplish and how you are going to achieve it.

This document removes all uncertainty or vague requirement statements with a clear plan of approach for achieving the test objectives. Test strategy is one of the most important documents for QA team. Writing it effectively is a skill every tester should achieve in their career.  Continue reading →

Test Cases Writing Tips:

One of the most frequent and major activities of a Software Tester (SQA/SQC person) is to write Test Cases. First of all, kindly keep in mind that all this discussion is about ‘Writing Test Cases’ not about designing/defining/identifying TCs.

There are some important and critical factors related to this major activity.

Let us have a bird’s eye view of those factors first.  Continue reading →

Are you aware that “Most of the bugs in software are due to incomplete or inaccurate functional requirements?” However well its written, the software code does not matter and nothing can be done if there are any ambiguities in requirements. This article on Software Requirements Specification (SRS) states that Requirements must be clear, specific, measurable and complete without contradictions.

It’s better to catch the requirement ambiguities and fix them in the early development life cycle itself.  Continue reading →

This is the guest post from Vijay D (Coincidence with my name).

Below sample bug/defect report will give you an exact idea of how to report a bug in bug tracking tool.

Here is the example scenario that caused a bug:

Lets assume in your application under test you want to create a new user with user information, for that you need to login into the application and navigate to USERS menu > New User, then enter all the details in the ‘User form’ like, First Name, Last Name, Age, Address, Phone etc. Once you enter all these information, you need to click on ‘SAVE’ button in order to save the user. Now you can see a success message saying, “New User has been created successfully”.

Continue reading →

Test plan is in high demand. Ya it should be! Test plan reflects your entire project testing schedule and approach. This article is in response to those who have demanded sample test plan.

In my previous article I have outlined Test plan Index. In this article I will elaborate that index to what each point mean to do. So this Test plan will include the purpose of test plan i. e to prescribe the scope, approach, resources, and schedule of the testing activities. To identify the items being tested, the features to be tested, the testing tasks to be performed, the personnel responsible for each task, and the risks associated with this plan.

Find what actually you need to include in each index point.

Continue reading →

Writing effective test cases is a skill and that can be achieved by some experience and in-depth study of the application on which test cases are being written.

Here I will share some tips on how to write test cases, test case procedures, and some basic test case definitions.

What is a test case?
“A test case has components that describe an input, action or event and an expected response, to determine if a feature of an application is working correctly.” Definition by Glossary

Continue reading →

Writing effective status report is as important as the actual work you did! How to write an effective status report of your weekly work at the end of each week?

Here I am going to give some tips. The weekly report is important to track the important project issues, accomplishments of the projects, pending work and milestone analysis. Even using these reports you can track the team performance to some extent. From this report prepare future actionable items according to the priorities and make the list of next weeks actionable.

Continue reading →

From the last couple of days, I am getting more request on Sample test plan.
So for your reference, I am including one sample test plan template here.

Its an Index of Test plan only.
Each point will help you to elaborate your test plan step by step.
Take this as a guideline and develop a full Test plan for Your project.

Continue reading →