Most of the test managers are familiar with implementing 'Shift left' approaches in Test Strategy to deliver upfront quality. Typical ways of doing shift left is to apply inspection techniques in reviewing the requirements and design artifacts, doing white box testing along with development while the components are getting developed etc. Shift left approach brings in early time to market by pulling the test schedule to the left and so is the value addition by identifying defects as early as possible there by reducing the cost of quality.
Test Managers need to be conscious of what to test late in the game, it is 'Shifting Right'. In particular, when it comes to regression testing of certain common/shared components, it makes sense to test as late as possible to ensure the code that goes live is regressed against the latest merged code base. In case of non functional testing, its better to do the soak tests as late as possible. Striking the right balance on what to test early and what to test late elevates an ordinary test manager into a master test strategist.
Test Managers need to be conscious of what to test late in the game, it is 'Shifting Right'. In particular, when it comes to regression testing of certain common/shared components, it makes sense to test as late as possible to ensure the code that goes live is regressed against the latest merged code base. In case of non functional testing, its better to do the soak tests as late as possible. Striking the right balance on what to test early and what to test late elevates an ordinary test manager into a master test strategist.
No comments:
Post a Comment