Jaideep Khanduja: Progressive Software Testing Approach by Acquiring Soft Skills

In software testing, we need to devise an approach that features a gradual progression from the simplest criteria of testing to more sophisticated criteria. We do this via many planned and structured steps, each of which brings incremental benefits to the project as a whole. By this means, as a tester masters each skill or area of testing, there is always something worthwhile to try next. Important aspects are:

 

Trust

Testing and development teams must build a trusting relationship with each other especially within the process of product development.

Constructive Communication

Initial communication between testing and development teams must be quite open, transparent, constructive and encouraging. This is the phase that determines the course of action for testing, as well as any alternatives. The future of the software, its accuracy, and its subsequent successful implementation, depend on good communication. But don’t make this communication too formal.

Documentation

Ensure that testers have sufficient documents in hand before starting the analysis and testing the product. Appropriate analysis of these documents is very important to remove any ambiguity/confusion/loop-holes in understanding the customer’s requirements. Test cases and scenarios will emerge from these requirements.

Open Mindedness

A tester has to go in with an open mind in all discussions. Only then will they be able to understand developers, the development process and customer requirements. Then they will plan the testing requirements accordingly.

Variables

Keep all important variables in the loop is important to testing and successful product development. Different variables could result in developers working on different modules, documents, testers, etc.

Learn from the Past

Keep learning from past experiences and try not to get caught with mistakes that have been made before. A common saying is – “Never repeat the same mistake twice”. It’s a mistake to test a product in a crude or unstructured manner. Learning from the past is perhaps the most potent means of improving your testing model over time.

Identify Shortfalls in Advance

Be clear about what is in the scope of testing and what is not. Clearly define what is not going to be covered in testing and understand what impact such omissions could potentially have on the product. Foresee any uncertainties or delays. It is important to understand the benefits you will derive well in advance rather than getting no benefits at the end of an exercise.

Keep Interacting

It is important that a tester continuously interact with developers throughout the entire testing process. Ultimately, the goal is to create a better product. To achieve this, both sides must work hand-in-hand to surmount all barriers, conflicts, bugs, faults and defects.

 

Jaideep Khanduja
Jaideep Khanduja has over 20 years of IT experience. Jaideep is currently working in the India Regional Office of a large versatile International group as Head of Quality Assurance and Project Management. Jaideep believes that innovation, team management, time management, skills enhancement, learning, knowledge management and mentoring are the best tools to grow.

 

Hans Buwalda
Hans Buwalda, CTO of LogiGear, is a pioneer of the Action Based and Soap Opera methodologies of testing and automation, and lead developer of TestArchitect, LogiGear’s keyword-based toolset for software test design, automation and management. He is co-author of Integrated Test Design and Automation, and a frequent speaker at test conferences.

The Related Post

LogiGear Magazine March Issue 2021: Metrics & Measurements: LogiGear’s Guide to QA Reporting and ROI
Regardless of the method you choose, simply spending some time thinking about good test design before writing the first test case will have a very high payback down the line, both in the quality and the efficiency of the tests. Test design is the single biggest contributor to success in software testing and its also ...
Companies generally consider the software they own, whether it is created in-house or acquired, as an asset (something that could appear on the balance sheet). The production of software impacts the profit and loss accounts for the year it is produced: The resources used to produce the software result in costs, and methods, tools, or ...
This article was developed from concepts in the book Global Software Test Automation: Discussion of Software Testing for Executives. Introduction Metrics are the means by which the software quality can be measured; they give you confidence in the product. You may consider these product management indicators, which can be either quantitative or qualitative. They are ...
With this edition of LogiGear Magazine, we introduce a new feature, Mind Map. A mind map is a diagram, usually devoted to a single concept, used to visually organize related information, often in a hierarchical or interconnected, web-like fashion. This edition’s mind map, created by Sudhamshu Rao, focuses on tools that are available to help ...
This article was adapted from a presentation titled “How to Turn Your Testing Team Into a High-Performance Organization” to be presented by Michael Hackett, LogiGear Vice President, Business Strategy and Operations, at the Software Test & Performance Conference 2006 at the Hyatt Regency Cambridge, Massachusetts (November 7 – 9, 2006). Introduction Testing is often looked ...
This article first appeared in BETTER SOFTWARE, May/June 2005. Executives and managers, get your performance testing teams out of the pit and ahead of the pack Introduction As an activity, performance testing is widely misunderstood, particularly by executives and managers. This misunderstanding can cause a variety of difficulties-including outright project failure. This article details the ...
LogiGear Magazine March Issue 2018: Under Construction: Test Methods & Strategy
From cross-device testing, to regression testing, to load testing, to data-driven testing, check out the types of testing that are suitable for Test Automation. Scene: Interior QA Department. Engineering is preparing for a final product launch with a deadline that is 12 weeks away. In 6 weeks, there will be a 1 week quality gate, ...
The 12 Do’s and Don’ts of Test Automation When I started my career as a Software Tester a decade ago, Test Automation was viewed with some skepticism.
Do testers have to write code? For years, whenever someone asked me if I thought testers had to know how to write code, I’ve responded: “Of course not.” The way I see it, test automation is inherently a programming activity. Anyone tasked with automating tests should know how to program. But not all testers are ...
LogiGear Magazine – May 2011 – The Test Process Improvement Issue

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe