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

Are you looking for the best books on software testing methods? Here are 4 books that should be on your reading list! The Way of the Web Tester: A Beginner’s Guide to Automating Tests By Jonathan Rasmusson Whether you’re a traditional software tester, a developer, or a team lead, this is the book for you! It ...
Introduction All too often, senior management judges Software Testing success through the lens of potential cost savings. Test Automation and outsourcing are looked at as simple methods to reduce the costs of Software Testing; but, the sad truth is that simply automating or offshoring for the sake of automating or offshoring will only yield poor ...
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 ...
Plan your Test Cases with these Seven Simple Steps What is a mind map? A mind map is a diagram used to visually organize information. It can be called a visual thinking tool. A mind map allows complex information to be presented in a simplified visual format. A mind map is created around a single ...
As I write this article I am sitting at a table at StarEast, one of the major testing conferences. As you can expect from a testing conference, a lot of talk and discussion is about bugs and how to find them. What I have noticed in some of these discussions, however, is a lack of ...
The V-Model for Software Development specifies 4 kinds of testing: Unit Testing Integration Testing System Testing Acceptance Testing You can find more information here (Wikipedia): http://en.wikipedia.org/wiki/V-Model_%28software_development%29#Validation_Phases What I’m finding is that of those only the Unit Testing is clear to me. The other kinds maybe good phases in a project, but for test design it ...
LogiGear Magazine – July 2011 – The Test Methods & Strategies Issue
The Testing Domain Workbook is the most extensive and exhaustive work you will ever find on a specific testing technique (or related techniques if you include equivalence class analysis and boundary testing as the book does). What I like best is the combination of academic background and roots combined with practical experience and industrial practice. All the concepts are ...
“Combinatorial testing can detect hard-to-find software faults more efficiently than manual test case selection methods.” Developers of large data-intensive software often notice an interesting—though not surprising—phenomenon: When usage of an application jumps dramatically, components that have operated for months without trouble suddenly develop previously undetected errors. For example, newly added customers may have account records ...
Internet-based per-use service models are turning things upside down in the software development industry, prompting rapid expansion in the development of some products and measurable reduction in others. (Gartner, August 2008) This global transition toward computing “in the Cloud” introduces a whole new level of challenge when it comes to software testing.
Introduction Many companies have come to realize that software testing is much more than a task that happens at the end of a software development cycle. They have come to understand that software testing is a strategic imperative and a discipline that can have a substantial impact on the success of an organization that develops ...
March Issue 2020: Smarter Testing Strategies for The Modern SDLC

Leave a Reply

Your email address will not be published. Required fields are marked *

Stay in the loop with the lastest
software testing news

Subscribe