blog.gurock.com Open in urlscan Pro
2606:4700:10::ac43:505  Public Scan

Form analysis
2 forms found in the DOM

GET https://www.gurock.com/testrail/search

<form role="search" method="get" id="searchform" class="search-form" action="https://www.gurock.com/testrail/search">
  <label class="screen-reader-text" for="q">Search for</label>
  <div class="search-input-wrapper">
    <input type="text" class="search-input" value="" name="q" id="q" placeholder="Search TestRail">
    <button class="search-button" id="searchsubmit">
      <i class="material-icons" id="search_icon">search</i>
    </button>
  </div>
</form>

GET https://blog.gurock.com/

<form role="search" method="get" id="searchform" class="searchform" action="https://blog.gurock.com/">
  <div>
    <label class="screen-reader-text" for="s">Search for:</label>
    <input type="text" value="" name="s" id="s">
    <input type="submit" id="searchsubmit" value="Search">
  </div>
</form>

Text Content

TestRail
Community
Search for
search
My Account account_circle
Blog


6 WAYS TO COME UP WITH A SOLID TEST STRATEGY

by Shanu Mandot | Aug 24, 2021 | Agile, General

This is a guest post by Raj Subrameyer.

The testing phase is a critical step in the software development lifecycle.
Companies of different sizes, from large enterprises to startup companies,
invest heavily in this phase. They want the features to match customer
expectations so that more people will want to use their products. As a result,
the company gets more revenue for the effort it put into delivering high-quality
software.

Like other phases of the development process, effective test planning needs a
lot of attention so that defects can be caught as early as possible. A good way
to develop a test plan is to get clarity on different aspects of the testing
phase.

Here are six ways to come up with a solid test strategy and flush out
ambiguities in the testing process.




1. GET CLEAR ON THE MODULES TO BE TESTED

One of the biggest causes of confusion during the testing process is teams not
having a common understanding of what modules to test. Each one has different
interpretations of how a feature works and what modules are critical to the
application. This is a recipe for disaster.

To prevent conflict and confusion from happening, teams should collaboratively
identify different features of the application that need to be tested during the
planning phase. This shared understanding prevents gaps in communication during
the testing process.




2. IDENTIFY ASSOCIATED RISKS

In addition to the happy path flows, teams must think of various failure
scenarios in the application. One way to do this is for the business
representative, a developer, and a tester to collaboratively come up with
different risks associated with each module. Based on the risks, teams can then
develop a test strategy to effectively analyze the system in various states.




3. GAIN CLARITY ON THE TIMELINE AND RESOURCE AVAILABILITY

Teams are under pressure to develop and test features at a rapid pace to meet
growing customer demands. They often work under tight timelines and do not have
time to waste. This being the case, planning testing within the available time
frame is always going to be a challenge, but the strategy should shift based on
the time available. For example, the testing strategy will vastly differ between
a release that happens within two weeks and one that happens in two months.

The availability of resources to perform testing also makes a huge impact on the
amount of work that can be completed within a given time frame. If there are
more resources, there could be more opportunities to perform different types of
testing and use various tools to get more information about the product.




4. STANDARDIZE PROCESSES AND TOOLS

Before testing starts, the team must agree on a common set of processes and
tools. This includes the story testing process, defect templates, test planning
templates, automation tools, frameworks, artifact repository systems, and
communication tools. Having a common understanding helps for more effective
collaboration and testing.




5. DEFINE CLEAR ROLES AND RESPONSIBILITIES

Every testing activity should have a point person — a person for automation,
manual testing, test planning, and the overall testing effort, as well as
someone who will serve as a liaison among different teams, often the test lead.
Having distinct responsibilities prevents unnecessary confusion in completing
tasks on time and prevents gaps in communication.




6. COME UP WITH THE DEFINITION OF DONE

One of the biggest reasons there are unnecessary defects and rework is not
having clear requirements and a definition of done for user stories. When is a
story deemed complete? If we cannot answer this question, it is a sign that
there is a big problem. 

The team has to collaboratively discuss what things have to be completed to earn
points from a story. In other words, when do we decide a story is fully
complete? These items to be completed may include having the Three Amigos
meeting or each story having unit tests, automated tests, and QA testing done.
Finally, demoing the story to the product owner or business representative
ensures features were implemented according to expectations.

As the saying goes, a goal without a plan is just a wish. The same concept
applies to testing as well. There should be a solid test strategy before teams
even start the development and testing process. The more clarity in the initial
phases, the better the overall testing effort will be.

Raj Subrameyer is an international keynote speaker, writer, and tech career
coach with a rich technical background. In his blog, rajsubra.com/blog/, he
posts inspirational news, resources, and updates to help his readers lead a
better life.


Search for:

RECENT POSTS

 * What Metrics Should You Be Using?
 * 5 Common Mistakes Teams Make During CI/CD Implementation
 * 6 Ways to Come Up with a Solid Test Strategy
 * Are Your Test Cases Really Effective?
 * Prediction Magic


TAGS

 * Agile (119)
 * Announcement (27)
 * Automation (14)
 * Books (2)
 * Business (42)
 * Continuous Delivery (26)
 * General (418)
 * Gurock Software (188)
 * Interviews (4)
 * Performance (17)
 * Programming (68)
 * Security (14)
 * SmartInspect (136)
 * Software Quality (196)
 * TestRail (130)
 * Uncategorized (13)
 * Virtualization (12)
 * Webinar (22)
 * Websites (24)

Contact
Security
Privacy Policy
Terms

© 2003-2021 Gurock Software GmbH


We use cookies on our website to give you the most relevant experience by
remembering your preferences and repeat visits. By clicking “Accept”, you
consent to the use of ALL the cookies.

Do not sell my personal information.
Cookie SettingsAccept
Manage consent
Close

PRIVACY OVERVIEW

This website uses cookies to improve your experience while you navigate through
the website. Out of these, the cookies that are categorized as necessary are
stored on your browser as they are essential for the working of basic
functionalities of the ...
Necessary
Necessary
Always Enabled

Necessary cookies are absolutely essential for the website to function properly.
These cookies ensure basic functionalities and security features of the website,
anonymously.

CookieDurationDescriptioncookielawinfo-checkbox-analytics11 monthsThis cookie is
set by GDPR Cookie Consent plugin. The cookie is used to store the user consent
for the cookies in the category "Analytics".cookielawinfo-checkbox-functional11
monthsThe cookie is set by GDPR cookie consent to record the user consent for
the cookies in the category "Functional".cookielawinfo-checkbox-necessary11
monthsThis cookie is set by GDPR Cookie Consent plugin. The cookies is used to
store the user consent for the cookies in the category
"Necessary".cookielawinfo-checkbox-others11 monthsThis cookie is set by GDPR
Cookie Consent plugin. The cookie is used to store the user consent for the
cookies in the category "Other.cookielawinfo-checkbox-performance11 monthsThis
cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the
user consent for the cookies in the category
"Performance".viewed_cookie_policy11 monthsThe cookie is set by the GDPR Cookie
Consent plugin and is used to store whether or not user has consented to the use
of cookies. It does not store any personal data.



Functional
Functional

Functional cookies help to perform certain functionalities like sharing the
content of the website on social media platforms, collect feedbacks, and other
third-party features.

Performance
Performance

Performance cookies are used to understand and analyze the key performance
indexes of the website which helps in delivering a better user experience for
the visitors.

Analytics
Analytics

Analytical cookies are used to understand how visitors interact with the
website. These cookies help provide information on metrics the number of
visitors, bounce rate, traffic source, etc.

Advertisement
Advertisement

Advertisement cookies are used to provide visitors with relevant ads and
marketing campaigns. These cookies track visitors across websites and collect
information to provide customized ads.

Others
Others

Other uncategorized cookies are those that are being analyzed and have not been
classified into a category as yet.

SAVE & ACCEPT