The 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)

Comments

Focus on Verification (V&V) to Transform Your Organization

When I was a quality manager in my earlier job in an MNC (Multi-National Company), a lot of my team members were quite misinformed about the “Power of Verification” in a software development process. I went through a lot of reflection around my own experience working on multiple projects related to doing “software verification” exercises. I gained profound understanding of how organizations can gain immense benefit just by understanding the true power of this activity (if done correctly). For the uninitiated, let me give a brief understanding about what “Verification” means. As part of ensuring quality of any software, the whole development process can be split into 2 simple parts – Verification & Validation To put this simply, “Verification” is always done before software code is developed & “Validation” is always done post development of software code. A “Verification” activity means, doing detailed analysis and reviews for – Customer Requirements Software Architectur...

Understanding "Emotional Intelligence" (or EQ) to Build Great Teams

Let me tell you… This has been my favourite subject of all! Not that I may want to do research in psychology but understanding people and how they behave so differently in different situations - just puts me in awe! So… What is EQ? A very nicely written post from psychcentral ( Psych Central Link ) aptly explains EQ as well as its 5 categories (or components), which are – Self-awareness Self-regulation Motivation Empathy Social Skills With even more detail, positivepsychologyprogram ( Positive Psychology Program Link ) provides even more details with the 4 dimensions of EQ, which for ‘emotions’ are – Perceiving Using Understanding Managing For further exploration on EQ, starting with Wikipedia ( Wikipedia Link ) is a great idea, since it also talks about the 3 models of Emotional Intelligence (or also referred to as EQ). The above 5 categories are coming from the “Mixed Model”. I am quite influenced by the ‘Mixed Model’ than other models. It is much more comprehensive and connect...

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 ...

SupraDigit Solutions

Search This Blog