Skip to main content

The Top 4-Ways to Build the Right Test Strategy

Top 4 ways to build the right test strategy


A Test Strategy is created to guide all teams on steps to achieve software quality objectives. With software companies adopting agile practices in a big way, an effective Test Strategy becomes even more important with iterative / sprint-based application development.

A test strategy being a live document, should ideally plan to integrate the business, development, testing, and management teams, define the quality objectives for the intended application and chart-out a path on how all the teams can help achieve these.

The test owner and the team can build an effective test strategy with these 4 best-practices:

A)   Focus on Prevention – Helps avoid major issues and rework on projects.

ü Prioritize requirements and business rules.

ü  Communicate changes in priorities immediately and effectively to important project stakeholders.

ü Strictly review and implement common requirements that ensure a consistent product.

ü Review product designs with an architect that can help implement future requirements with ease and optimization.


B)  Design the Right Metrics – To iteratively “measure quality” for the project.

ü Application go-live metrics should cover the base metrics for requirements, design components and development progress along with the test output.

ü To pick the right metric, consider ease of collecting data regularly and generating reports.


C)  Make an efficient Test Design – Provides high-coverage and build a scalable test architecture for complex applications.

ü Understand, why “test design” is important. For example, having basic UI checks as part of a checklist helps to start defining and building a simple “test design”.

ü An efficient test design provides a basis to automate redundant user activities.

ü Define “test scenarios” instead of “test cases”. Reuse documented requirements and business rules to build your test scenarios.


D)   Build Cross-Functional and Cross-Technical Testing Teams.

ü Build cross-functional and cross-technical testing teams. Allow and educate team members to delve deeper into the application architecture and core design to unravel design bottlenecks and limitations.

ü Testing team should interact with the business team to gather deep domain expertise to identify preventive measures.

- Written by Anand Nanavati (SupraDigit Solutions)

Labels:
Location: Mumbai, Maharashtra, India

Comments

Post a Comment

Popular posts from this blog

Reduce Your App Development Costs by More than 50% by "Simply Preventing Bugs"!

"Be a yardstick of quality. Some people aren’t used to an environment where excellence is expected.”— Steve Jobs Everybody loves to avoid a disaster, but there is a “proactive” effort to do activities that can prevent a disaster from happening. Most of the executives do not want to “get involved” in such “proactive” efforts, simply due to the love of fixing urgencies Or having a mindset that it’s not important.   I remember, when once I was working with the Quality Assurance team on a product. The development team simply refused to spend efforts on the most essential “unit testing” for their developed components! The intent was to release the software to the QA team as soon as possible and focus more on so-called “core development”. Over the years, looking at multitude of projects failing in-spite of highly experienced resources, reasonable time and the intent, I have uncovered that, prevention is the “Most Important” and “Ignored” part of software development. Why should we
Post a Comment
Read more

What is Software Quality?

“Why do we never have the time to do it right the first time, but always have time to do it over and over after the first time?” – Anonymous  Quality is something that happens at every stage of Software Development! When I talk about Software Quality, almost everyone in the Information Technology world thinks about “Software Testing”. Unfortunately, this is a myopic view of Quality as a specific team effort and not as something, that should be embedded and part of the complete Software Development Life Cycle! Quality can be defined and need not be an “ambiguous term” for an organization. For any software, quality is more aptly seen from a view of what the customers considers as ‘Quality’. Although, this is not the only way to consider ‘Quality’. Quality must be seen from the viewpoint of ALL stakeholders involved with the product. Apart from this, ‘Quality’ should be considered as everybody’s res
Post a Comment
Read more