Continue # Infosys Whitepaper 
 looked at what is ailing SAP based  organisations, setting up a Test Factory can  be the most definitive solution available  in the market currently. Test Factory is  a centralised testing model that brings  together people and infrastructure into  a shared services function adopting  standardising processes, effective usage of  tools, high reuse and optimising resource  utilisation in order to generate required  benefits for the organisation.<|endoftext|>Let us broadly explore the solution that a  Test Factory can provide –  a. Test Factory acts as an independent  function in the SDLC and resolves the  very first ailment by having a clear  delineation between the Build and Test  functions of an organisation.<|endoftext|>b. Test Factory is setup as a centralised  QA function which brings in uniform  process adoption and an enterprise  wide QA approach with easier  governance. Test Factory is also  setup with the attributes of a more  agile, efficient and repeatable set of  processes.  Test Factory can also be operated in the  new engagement model (NEM) format  which helps in measuring the business  value linked to the services offered,  example; pricing is based on the work  performed instead of traditional Time &  Material models.<|endoftext|>Implementing a Test Factory The entire process of implementing a Test  Factory involves 3 major phases – Solution  Definition Solution  Design Solution  Implementation 3 Solution Definition Phase “Building the Case for Organisational Buy- in” One of the most essential starting points  of the entire Test Factory setup involves  assessing the existing organisational  test processes, determining the maturity  level of the processes and deriving the  gaps observed. The solution definition  phase involves arranging for one-on-one  or group interview sessions with various  stakeholders, in the existing ecosystem,  and understanding the various pros and  cons of the existing processes. Alternatively  or additionally, a questionnaire pertaining  to the respective areas of the stakeholders  can be used to help document the same.  For assessing the maturity, organisations  are spoilt for choices with widely known  Test Maturity models such as the TMMi,  TMAP, TPI or the ITMM (Infosys Test  Maturity Model).<|endoftext|>The ITMM is a well-blended model which  builds upon the standard Test Maturity  models and also adds further dimensions  to its fabric in being able to evolve  constantly to the changing business  context.  The assessment results show the current  level of maturity of the organisation’s  processes. It is of utmost importance at  this stage to bring together the leadership  team of the organisation and showcase  the various process improvements and  benefits of moving the organisation to the  higher levels of maturity. On the basis of  the agreed level of maturity to be targeted,  the ITMM model allows for a continuous  improvement process to be imbibed into  the organisation. Once an agreement  is reached, a roadmap is devised on  how the solution is to be designed and  implemented.  Solution Design Phase “Structuring A Winning Solution” The Solution design phase is a core  component in the Test Factory setup  process and involves designing processes  on three dimensions of the ITMM model – • Test Engineering Dimension, covering  the focus areas of Requirements  Gathering, Test Strategy, Testing tools,  Test Data and Environment • Test Management dimension, covering  the focus areas of Estimation, Test  Planning, Communications, Defect  Management and Knowledge  Management  • Test Governance dimension, covering  the focus areas of Test Methodology,  Test policy, Organisational structure  and Test Metrics The most important key areas to focus  would be to design the processes for -  • Test Methodology  Defining various types of testing to  External Document © 2018 Infosys Limited 

---

  Page: 5 / 8  

---

 be performed, estimation techniques,  entry and exit criteria for each testing  phase, testing environment set-up,  operating model and various input and  output artifacts • Test Governance  Defining the governance structure  and chalking out clear test roles and  responsibilities • Test Factory Structure  Defining the various communication  paths within and outside the Test  Factory • Metrics, KPIs and SLAs  Defining the various testing related  metrics and ensuring agreement on the  various SLAs and KPIs for each role and  processes in the Test Factory • Knowledge Management Framework  Defining a centralised service to allow  effortless and effective sharing of  knowledge between teams, across  knowledge assets   In addition, teams may create, test data  management processes, a catalogue of  the testing services, non-functional test  services methodology, Guidelines for  various Testing tools and Testing Policies.  The solution design phase is a highly  collaborative process in which the design  and delivery teams play equal roles.  It involves both, fine tuning some of  the current processes and completely  revamping the rest. The implementation  of the solution in the right manner, and  with the right amount of calibration, can  bring about bountiful benefits to the  organisation in having a sound testing  process.<|endoftext|>Solution Implementation Phase “Walk the Talk” Depending on the level of maturity  that organisations choose to attain, this  phase needs a good deal of time to be  invested. The time taken to nurture the  processes and imbibe them could range  anywhere from six months up to two years,  depending on the organisational buy-in  and focus in implementing the same.   Having a good amount of time on hand,  organisations also have the option of  choosing to implement the processes in  either a staggered manner or with a big  bang approach. In general, it is advisable  that a staggered approach be chosen.<|endoftext|>In a staggered approach, the  implementation team collaborates with  the champion or manager of the Test  factory prioritising the areas lacking basic  maturity and identifying a pilot release in  which the updated processes can be put  to test. This allows the implementation  team to lay out checkpoints where any  anomalies can be corrected. At the end  of the pilot implementation, a survey can  be conducted with the stakeholders in  determining the success and failures in the  implementation. The lessons learnt at the  pilot implementation stage are a crucial  input to the next phase of implementation.<|endoftext|>It is important to look at some of the  frequently encountered challenges  associated with the solution  implementation phase -  • Aversion to change  This often is a sticky issue with teams  unwilling to adapt to new processes  as it involves moving away from the  comfort zone • Poorly adapted processes and  communications  This is an indication that the impacted  teams are not aware of new processes  and are not well trained • Handing over testing to Test Factory  Traditional approach of testing by  business users due to lack of business  knowledge by testing team is one  of the most challenging change  management aspects to deal with It is therefore a task for both the  implementation team and the Leadership  team of the organisation in addressing  these challenges / change management.  The task of the implementation team lies  in devising a thorough training plan for  the various teams involved, designing user  manuals and guidelines for any reference  required to the new processes.<|endoftext|>On the other hand, the task of the  leadership team is to put together a strong  communication plan, listing the benefits  that accrue to, both the impacted teams  and the business benefit in adapting  the changes. In certain situations,  grievance redressal efforts and holding  communication forums is a good way to  engage with the teams.<|endoftext|>External Document © 2018 Infosys Limited 

---

  Page: 6 / 8  

---

 Figure: Test Maturity Model External Document © 2018 Infosys Limited 

---

  Page: 7 / 8  

---

 Benefits of a Test Factory We have managed to explore the story  of the Test Factory setup with the sound  process framework forming the base, but  the real icing on the cake is to see the  benefits that accrue post setting up of the  Test Factory.<|endoftext|>Test Factory brings about a set of both  Qualitative and Quantitative benefits.  Some of the Qualitative and hard hitting  benefits include  • Ensures high levels of repeatability,  predictability and test coverage • Delivers on business requirements  driven end-to-end testing  This helps in identification of critical  defects and requirement gaps which  would have been typically identified  only during UAT phase • Definition of key metrics  Assists in tracking enabling effective  governance at every stage of the  programme  • A reusable set of artifacts and test  design, helping crash test planning and  design timelines • Reduce the UAT phase saving on  delivery timelines • Understanding of core business  processes & building the core  regression library • Effective usage of tools enabling  complete traceability from  requirements to test cases and defects  during various phases of the project • Accelerated test automation helping in  reduction of cycle time and execution  costs • Providing platform to have more  frequent releases annually – This will  benefit the business and end users in  moving away from the erstwhile lower  frequency, which meant having to wait  long for the release of the important  Business/IT changes • One