{"id":843,"date":"2015-11-20T10:42:38","date_gmt":"2015-11-20T10:42:38","guid":{"rendered":"http:\/\/www.gallop.net\/blog\/?p=843"},"modified":"2018-10-12T12:06:25","modified_gmt":"2018-10-12T06:36:25","slug":"test-management-managing-large-scale-projects","status":"publish","type":"post","link":"https:\/\/www.cigniti.com\/blog\/test-management-managing-large-scale-projects\/","title":{"rendered":"Test Management \u2013 Managing Large Scale Projects"},"content":{"rendered":"

The need for continuous improvement and sustenance of quality in a software development is one that cannot be ignored. Apps, products, tools et al \u2013 all use software that is always at the risk of having one or the other bug or issue. The availability of a plethora of configurations, mobiles, browsers, etc. further adds on to the complexity of the situation.<\/p>\n

Therefore, it is but obvious how critical is the need and importance of an end-to-end process of software validation and testing to be able to attain the desired quality. This, in turn, necessitates the understanding of what Test Management is all about.<\/p>\n

This article briefly covers what Test Management entails, some of the challenges faced during implementation of the framework, and some best practices that might be followed to overcome the obstacles and emerge as a market leader.<\/p>\n

What is Test Management and what does it entail?<\/h2>\n

Per Wiki, \u201cTest management most commonly refers to the activity of managing the computer software testing process.\u201d<\/p>\n

In more generalized terms, test management is the name given to the process used to successfully drive and control an organizations testing activities.<\/p>\n

The basic underlying process of a test management framework<\/a> requires a testing team to plan, develop, execute, and assess all test assets, artifacts, and activities that fall within the purview of Software Testing Lifecycle (STLC). The success of this flow depends on how well the efforts for all the activities were coordinated \u2013 even if the teams are collocated.<\/p>\n

Different Phases of STLC<\/strong><\/p>\n

The different phases of the STLC are described briefly below:<\/p>\n

    \n
  1. Managing Test assets\/artifacts: This refers to the proper maintenance of items to be tested, along with the tools required for performing the actual tests. Test assets may be in the form of software, scripts, data, or hardware.<\/li>\n
  2. Planning addresses the following questions: what test cases to test, where to manage the documentation related to the tests, and when to perform the test iterations.<\/li>\n
  3. Development\/Authoring refers to capturing the specific requirements for successfully completing the given tests.<\/li>\n
  4. Execution covers the process of sequentially running the assembled scripts for generating the desired result.<\/li>\n
  5. Assessing\/Reporting entails the process of analyzing the test results and then sharing the reports. These reports form the basis of determining the current status of the tests conducted along with the overall quality of the product being tested.<\/li>\n<\/ol>\n

    The overall effort generates a huge amount of data based on which metrics are collected that help measure and track the quality goals of the project.<\/p>\n

    Test Management Challenges & Issues<\/strong><\/p>\n

    There are many challenges that an organization faces while implementing and following STLC. A few of these challenges are mentioned below in brief.<\/p>\n