Is a test strategy really becoming an obsolete artifact?
Until a few years ago, I vividly remember a separate phase in the
software test life cycle that used to be dedicated to the development of
a master test plan or the so called holy test strategy which served as
the guiding document outlining the software testing process specific to
the product under test. It was usually drafted by the test director or
the test manager and was representative of the test team’s intelligence
in helping them making the product sign off call. Such was the
importance of this document; it also served as a reusable artifact often
carried across releases, products and teams. Given the relative
stability in the development environment such cross sharing and
reusability were feasible.
To read more, visit our blog: http://www.qainfotech.com/blog/2012/04/is-a-test-strategy-really-becoming-an-obsolete-artifact/
