Continue # Infosys POV
 innovation at  scale New, customer-friendly insurance products are  easy to design on paper, but legacy systems  and processes might hinder their realization.  Set up an innovation pipeline with  industrialized approach for each of the stages  from idea incubation to prototyping, market  testing, market launch and scaling. Product  portfolio requirements will increase  substantially from modularization,  disaggregation, parametrization, and  personalization. Define requirements for  technology and data to realize the new  products.<|endoftext|>6 Design the to-be processes and  operating model Powered with the new technology, design the  to-be processes to realize the target customer  experience. Focus providing near-immediate  turn-around time for all customer-facing  activities through process elimination,  simplification, automation, and parallelization.  Support the own and 3rd party manual  processes, e.g., with AI image analysis, next- best action, recommendation engines, and  price calculators. Define the new capabilities  and roles needed, set training paths, and  recalibrate staffing needed to operate the new  processes.<|endoftext|>Thriving in the Post-Covid Insurance Growth © 2023 Infosys Consulting 24

---

  Page: 25 / 28

---

 1.<|endoftext|>https://www.imf.org/en/Publications/WEO/weo-database/2022/October 2. https://www.imf.org/en/Blogs/Articles/2022/10/13/asia-sails-into-headwinds-from-rate-hikes- war-and-china-slowdown 3.<|endoftext|>https://stats.oecd.org/Index.aspx?QueryId=25444 4. https://www.insurance.gov.ph/ 5. https://www.bakermckenzie.com/-/media/files/locations/thailand/insurance-outlook-14th- edition.pdf 6. https://www.lexology.com/library/detail.aspx?g=7ce23ebe-600e-482d-aeb8-fe8e386c498c 7.<|endoftext|>https://mof.gov.vn/webcenter/portal/btcvn 8. https://www.febis.org/2022/04/01/vietnam-s-insurance-market-to-see-double-digit-growth-in- 2022/  9. https://equityhealthj.biomedcentral.com/articles/10.1186/s12939-021-01578-0  10. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6008596/ 11. https://www.globaldata.com/media/insurance/general-insurance-industry-vietnam-reach-3- 5bn-2026-forecasts-globaldata/  12. https://pubmed.ncbi.nlm.nih.gov/33853361/  13. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC9532955/#:~:text=Results%3A%20The%20pre valence%20of%20health,the%20Indonesian%20population%20is%2062.3%25.  14. https://services.google.com/fh/files/misc/e_conomy_sea_2022_report.pdf 15. https://www.swissre.com/reinsurance/life-and-health/l-h-risk-trends/consumers-embrace- digitalisation-points-better-protected-future.html  16. https://www.mckinsey.com/industries/financial-services/our-insights/emerging-markets-leap- forward-in-digital-banking-innovation-and-adoption  17. https://www.ey.com/en_ph/insurance/why-insurers-must-adapt-to-meet-the-changing- philippine-landscap 18. https://www.swissre.com/dam/jcr:f5cfd028-b7c9-4958-a5c3-06f7d2e720fc/ep_en_digital- adoption-in-personal-pc-insurance-in-southern-asia-webb.pdf 19. https://www2.deloitte.com/content/dam/Deloitte/sg/Documents/consumer-business/sea-cb- gacs-study-perspective.pdf 20. https://www.bain.com/insights/how-insurance-customers-are-responding-to-COVID/  21. https://insuranceblog.accenture.com/reimagining-end-to-end-customer-experience-drive- growth  REFERENCES Thriving in the Post-Covid Insurance Growth © 2023 Infosys Consulting 25

---

  Page: 26 / 28

---

 REFERENCES 22. https://www.aia.com/content/dam/group/en/docs/annual-report/Annual Report  2021_E.pdf.coredownload.inline.pdf 23. https://www.aia.com.hk/en/about-aia/about-us/media-centre/press-releases/2022/aia-press- release-20221014 24. https://www.the-digital-insurer.com/award-application/aia-thailand-alive-powered-by-aia/ 25. https://www.bangkokpost.com/business/2286146/aia-aiming-to-help-1bn-people-across-asia- to-live-healthier-longer-better-lives-by-2030 26. https://www.fwd.com.ph/-/media/pdf/documents/fwd-ph-annual-report-2021- 2.pdf?rev=20b476bd356540fe93fb6a0b02ccb947 27. https://www.allianz.com.my/content/dam/onemarketing/azmb/wwwallianzcommy/pdf/financia l-reports/annual-reports/AllianzAnnualReport2021.pdffwd-ph-annual-report-2021-2.pdf 28. https://www.allianz.com.my/content/dam/onemarketing/azmb/wwwallianzcommy/personal/ca mpaigns/allianz-ceo-programme/AllianzCEOProgrammeBrochure_EN.pdf Thriving in the Post-Covid Insurance Growth © 2023 Infosys Consulting 26

---

  Page: 27 / 28

---

 JITIN SHARMA Associate Partner Singapore +65 8849 7197 Jitin.Sharma@infosysconsulting.com SAGAR ROONGTA Consultant Singapore +65 8264 6036 Sagar.Roongta@infosysconsulting.com MEET THE EXPERTS AARO KAUPPINEN Principal Singapore +65 8870 2590 Aaro.Kauppinen@infosysconsulting.com Thriving in the Post-Covid Insurance Growth © 2023 Infosys Consulting 27

---

  Page: 28 / 28

---

 consulting@Infosys.com InfosysConsultingInsights.com LinkedIn: /company/infosysconsulting Twitter: @infosysconsltng About Infosys Consulting  Infosys Consulting is a global management consulting firm helping some of the world’s most recognizable  brands transform and innovate. Our consultants are industry experts that lead complex change agendas  driven by disruptive technology. With offices in 20 countries and backed by the power of the global Infosys  brand, our teams help the C-suite navigate today’s digital landscape to win market share and create  shareholder value for lasting competitive advantage. To see our ideas in action, or to join a new type of  consulting firm, visit us at www.InfosysConsultingInsights.com.  For more information, contact consulting@infosys.com  © 2023 Infosys Limited, Bengaluru, India. All Rights Reserved. Infosys believes the information in this  document is accurate as of its publication date; such information is subject to change without notice. Infosys  acknowledges the proprietary rights of other companies to the trademarks, product names, and other such  intellectual property rights mentioned in this document. Except as expressly permitted, neither this document  nor any part of it may be reproduced, stored in a retrieval system, or transmitted in any form or


Continue # Infosys POV
 by any means,  electronic, mechanical, printed, photocopied, recorded or otherwise, without the prior permission of Infosys  Limited and/or any named intellectual property rights holders under this document.

***


# Infosys Whitepaper
Title: Transforming Quality Assurance Organizations by Enabling Dev”T”Ops
Author: Infosys Limited
Format: PDF 1.7

---

  Page: 1 / 4

---

 VIEW POINT Abstract Despite the rising popularity of DevOps in enabling agile  development, its potential to transform the testing lifecycle is  largely untapped. This paper examines the importance of DevOps in  today’s business landscape and explains why it should play a greater  role in testing/QA organizations (Dev”T”Ops). It also focuses on  implementation view of DevOps along with its measurable benefits.<|endoftext|>TRANSFORMING QUALITY  ASSURANCE ORGANIZATIONS BY  ENABLING DEV”T”OPS

---

  Page: 2 / 4

---

 Development Repository Validations Environment   Provisioning Integration DevOps DevOps – The ‘agile’ catalyst  The rapid pace of change in the present  economy requires organizations to find  new ways to quickly overcome business  and technology challenges. The winning  organizations are those that possess the will  to transform and discover smarter ways of  working. Today, there is an ever-increasing  demand for quality software, which places  greater focus on optimizing all stages  of the software delivery lifecycle (SDLC).  Thus, many players are adopting agile  methodologies to stay relevant and achieve  reliable and predictable business outcomes.  In such a competitive landscape, DevOps  has already become a vital catalyst as the  preferred solution to address technical  challenges such as:  •  Digital Transformation : Omni Channel  Experience, End to End business process  workflow implementation, IOT devices  integrations  •  Cloud Deployment:  •  Rapid applications development  - code publishing, security keys  container/stack/queue creations, full /  half / partial deployments •  On demand virtual machines - auto  scaling, machine images •  Tracking of real time usage – data,  volume, and transactions •  Data : Data Replications, Data  Provisioning, Data Deployment •  APIs: Micro Services Integrations, Service  Virtualizations More importantly, DevOps is expanding  beyond technology and is significantly  impacting people as well as processes.<|endoftext|>DevTOps – Implementing  DevOps in testing DevOps is a set of practices and processes  that foster better collaboration and  communication between developers and  other professionals involved in operations.  Despite its importance in enabling agility  in development lifecycles, DevOps is often  considered as an add-on capability. Many  organizations are unable to tap its full  potential to transform testing lifecycles  that typically consume nearly 30% of their  budgets or schedules.  Principally, DevOps is about building  a collaborative culture, adopting agile  methodologies, exploiting automation  to accelerate innovation, and providing  rapid feedback to achieve common  goals. As such, DevOps mandates a close  involvement with the QA organization.  DevOps in QA is essential for many reasons,  the key among which are Enabling rapid  testing cycles, Ensuring reliable finished  products, Providing predictable business  outcomes, Reducing cost or Improving  SLAs.<|endoftext|>The time has come for enterprises to  introduce DevOps in testing. Enabling  DevTOps will help QA organizations  promote DevOps across the SDLC for  superior benefits. To tap the objectives  such as speed & agility, many choices of  tool sets and point solutions (Open Source  / COTS) are available.<|endoftext|>External Document © 2018 Infosys Limited

---

  Page: 3 / 4

---

 Over the past 15 years, test automation  has come a long way. Techniques such  as behavior-driven development (BDD)  and acceptance test-driven development  (ATDD) are enabling the much-needed  shift-left in QA. Further, automation  tools are being deployed intelligently  across the software test lifecycle (STLC),  thereby improving automation coverage  beyond user interfaces (UIs), irrespective  of disparate technologies. This increased  automation coverage provides a great  platform to practice DevTOps.  In a continuous integration (CI) and  continuous delivery (CD) pipeline end  to end automation is a key. Pipe line  consists of build automation, continuous  integration; test automation; and  deployment automation. The pipeline  starts by building the binaries by cloning &  caching of the repository, hooking / polling  the changes, merging the code branches  to create the deliverables. This ensures that  newly developed features are continuously  integrated with the central code base.<|endoftext|>Each time build is done and code is unit  tested. The health of checked-in codes  are informed to the developer’s real time  basis and in case of failure checked-ins are  prohibited. Once the build is successful it  is automatically deployed for the testing to  ensure that it meets all desired exit criteria.  The test automation are extended beyond  the functional to several non-functional  such as security, performance, user  experience or compliance etc. The defects  are automatically reported in the defect  management tools.<|endoftext|>Once the application is verified for the  quality gates it moves for deployment  pipeline. The deployment pipeline is  supported by platform provisioning,  environment validations and system  configuration management & verifications.  The deployment on premise or a hosted  environment such as Amazon Web  Services (AWS) are automated and allows  provisioning or tearing down environments  automatically. The deployment in staged  / production environment happens in  controlled manners where changes get  deployed partial or full. The deployment is  fully automated and executes just in few  minutes Deployment automation ensures  the applications quality and reliability as  well as its future scalability. The deployed  applications are continuously monitored  preventive basis such as applications /  system logs are scanned regularly and  alerts are sent in case of issues. The  infrastructure such as memory / space are  controlled automatically and scaling ups /  downs happens real time.<|endoftext|>Failed Failed Code  Branches Environment Validation Code Compilations Unit Testing Test Cluster / Buckets Test Automation Cloning/  Caching Control  Hooking /  Polling  Control  Build Automation Defect  Automation Deployment Automation Application  Deployment  & Monitoring Functional Test Automation Security Test Automation Performance Test Automation UX Test Automation Repository Management Change Control Failure Reporting  Continuous Integration Pipeline Continuous Delivery Pipeline Platform Provisioning Environment Validations Confgurations Mgmt.<|endoftext|>Apps Log  Monitoring System Log  Monitoring Scaling up / Down Full / partial deployment Version Management Code collections Branch Merging Machine Images External Document © 2018 Infosys Limited

---

  Page: 4 / 4

---

 Benefits of DevTOps  Mature IT services organizations are  already reaping the benefits of DevTOps  investments across people, processes  and technologies. In these organizations,  developers and testers collaborate better  to achieve common goals and deliver  top-quality products. DevTOps helps QA  organizations prevent defects rather than  detect them later. In doing so, DevTOps  delivers measurable success and tangible  benefits such as shorter timeframes to  verify and implement changes, reduced  average time taken to recover from  production incidents, reduced failure rates  during production changes and greater  bandwidth for innovation.<|endoftext|>Further, the return on investment in  DevTOps is faster and more significant  compared to other investments made  by QA organizations. The key areas of  improved ROI include lower cost due to  reduced downtime/wait-time, faster time- to-market when launching new features,  improved customer satisfaction and more  opportunities to innovate.<|endoftext|>Conclusion  Top quality and greater speed in  development and operations are the main  drivers for adopting DevOps. DevOps helps  organizations accurately track changes to  source code, manage development, testing  and operational complexities and ensure  self-healing. As new tools and techniques  enable higher testing automation coverage,  there is a need to enable DevOps in testing  as well. However, this can be challenging  for traditional testers as they must shift to  the center of development and operations  activities and contribute to overall product  vision and strategy. Such a change is critical  to improving the cadence of production  releases. QA organizations must focus on  making strategic investments in their own  operations by implementing DevTOps to  enable software development engineers in  test (SDETs) and focus on defect prevention  rather than detection. By adopting DevTOps,  QA teams can reduce production failures,  recover quickly from production incidents,  launch new features faster, and improve  customer satisfaction – all of which improve  ROI. Investing in DevTOps in QA drives  innovation in testing that will continue to  generate returns for the organization.<|endoftext|>
Author  Manish Kumar Pandey ManishK_Pandey@Infosys.com Delivery Manager, IVS Consulting © 2018 Infosys Limited, Bengaluru, India. All Rights Reserved. Infosys believes the information in this document is accurate as of its publication date; such information is subject to change without notice. Infosys  acknowledges the proprietary rights of other companies to the trademarks, product names and such other intellectual property rights mentioned in this document. Except as expressly permitted, neither this  documentation nor any part


Continue # Infosys Whitepaper
 of it may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, printing, photocopying, recording or otherwise, without the  prior permission of Infosys Limited and/ or any named intellectual property rights holders under this document.  For more information, contact askus@infosys.com Infosys.com | NYSE: INFY Stay Connected

***


# Infosys Whitepaper
Title: Leveraging Database Virtualization for Test Data Management
Author: infosys Limited
Format: PDF 1.7

---

  Page: 1 / 8

---

 WHITE PAPER LEVERAGING DATABASE  VIRTUALIZATION FOR TEST DATA  MANAGEMENT Vikas Dewangan, Senior Technology Architect,  Infosys Abstract Database virtualization is an emerging trend in test data  management (TDM) and is all set to bring about a revolution in  the provisioning of non-production data. These tools offer efficient  virtual cloning of production databases for software application  development and testing, without having to physically replicate the  entire database. Coupled with powerful features like taking point-in- time snapshots, write backs to the source database, and rolling back  changes; these tools have the potential to bring in significant cost  savings and efficiency improvements. In this paper, we explore the  concept of database virtualization, industry tool features, and how  these tools can be leveraged to improve TDM.<|endoftext|>

---

  Page: 2 / 8

---

 Introduction Virtualization technologies have been  around for a while and were first  introduced in the era of mainframe  systems. However, it is only in the recent  past, due to advances in technology,  that virtualization has been gaining  popularity. The term ‘virtualization’ refers  to encapsulating a particular hardware  or software resource so that multiple  systems can make use of it. By means of  virtualization, hardware resources can  be utilized more effectively through  consolidation, resulting in significant cost  savings. Further, virtualization leads to  savings in hardware costs; thus resulting  in decreased energy consumption and  increased green technology. Given these  advantages, virtualization will continue  to see a trend of increasing adoption in  the years to come. There are a number  of popular virtualization technologies  today, such as server, storage, database  and desktop virtualization. Out of these,  database virtualization  is the focus of this  paper.<|endoftext|>The field of test data management (TDM)  concerns itself with provisioning of  production-like data in non-production  environments, such as those used for  application development and testing  and is thus a related area. Database  virtualization is an emerging trend in TDM,  with the potential of offering significant  cost advantages. In this paper we will  explore how database virtualization can  be optimally leveraged to increase TDM  effectiveness.<|endoftext|>External Document © 2018 Infosys Limited

---

  Page: 3 / 8

---

 Traditional approach  The common approach taken by most  enterprises today is to have physical copies  of the production database in each non- production environment. Non-production  environments include environments for  software development, testing, and training.<|endoftext|>It is not uncommon to find even 10 – 12  such production copies in most enterprises.  These physical copies may contain  either an entire copy or a subset of the  production database. With each additional  environment needed there is an increase  in physical storage requirements, database  administration needs and the time required  to setup these databases. Refreshing these  non-production databases is a time- consuming and costly exercise. Often, due to  contentions, the availability of development  and test environments becomes a  bottleneck in the software development  life cycle and can lead to increased overall  turnaround times. In summary, the  traditional approach is complex and costly.<|endoftext|>Database virtualization – a  better approach With the coming of age of database  virtualization, a gamut of opportunities  for optimization of non-production  environments has opened up. Several  enterprises have started taking cognizance  of this trend and are actively exploring how  best they can leverage this technology for  deriving maximum business value.  So what exactly is database virtualization  and how does it work? In the case of a  database virtualization-based approach,  the virtualization engine creates multiple  virtual clones of the production database.  These virtual copies of the database can  be utilized in the same way as the actual  physical copies. They will be transparent  to the applications in these environments  and will continue to function with these  virtual database instances in exactly the  same manner as they did with the physical  non-production databases. There is no need  to create subsets of production data and  entire datasets can be made available to the  relevant applications.<|endoftext|>Presented below is a simplified view of the  traditional data refresh process for non- production environments compared with a  database virtualization-based approach. It  should be noted that in some cases there  may be an intermediate database between  the production and non-production  environments, which may be used for  masking or sub-setting purposes.<|endoftext|>Test Environment 2  Test Environment 3 Dev Environment 1 Production  Database Virtual Clone 2 Virtual Clone 3 Virtual Clone 1 Traditional ETL approach for non-production environments Database virtualization approach for non-production environments Database ETL / sub-settingutility Involves creating physical copies of the production database Production Database Database virtualization engine Involves creating virtual clones of the production database Key features of database  virtualization tools Today, there are a number of vendors  offering products in the database  virtualization space. Let us take a look at  some of the important features and benefits  that these products (though not all) provide: 1.  Provision database clones: The  functionality of rapidly provisioning  virtual database clones is at the heart of  all database virtualization tools. These  virtual clones can typically be created in  a matter of hours, as opposed to physical  databases, which may take up to several  days to setup and load data  2.  Resource segregation: Each virtual  database instance is a private copy and  is unaffected by changes made to other  virtual clones (‘Ring fencing’)  3.  Lower resource utilization: Database  virtualization tools implement highly- optimized compression algorithms to  minimize the in-memory footprint of  each cloned database instance. Usually  data that is duplicate across clones is  maintained as a common block across  instances, while modified data is stored  privately for each clone, leading to  optimization of the memory footprint 4.  Ease of refresh: Unlike refreshing  physical databases, refreshing an  existing virtual database clone with  the latest production data is relatively  simple and straightforward. The clones  being in-memory instances, the refresh  process is much faster and efficient  as there are no physical writes. Most  database virtualization engines will  refresh the virtual instance with changes  only, rather than purging and refreshing  the entire database  5.  Point-in-time snapshots: Often, in  test environments, there is a need to  take snapshots of multiple databases  at the same point in time to ensure  consistency of the test data. In the  traditional approach, extracting data  from multiple databases seldom  happens simultaneously and there  is some time difference between  data extraction processes. This leads  to referential integrity issues across  databases (as several transactions  may have taken place during this time  difference), which have to be fixed in  non-production environments. With  database virtualization engines, it  is possible to obtain a virtual clone  of each source database against a  specific point-in-time. This results in  maintaining the referential integrity  and consistency of data across the  provisioned virtual database instances.<|endoftext|>External Document © 2018 Infosys Limited

---

  Page: 4 / 8

---

 6.  Synchronization with source  database: The updates made to the  virtual database clones can be written  back to the intermediate database  if required. For example, this might  be required if the data in the virtual  clone has been augmented for testing  purposes and a need arises to replicate  this to other test environments. This  feature can also be used to help  maintain a ‘gold copy’ of the database.<|endoftext|>7.  Self-service: Virtualization tools,  once setup, are easy to use and can  reduce the dependency on database  administrators (DBAs) when compared  to the traditional approach where the  physical copy of the database needs  to be refreshed. Further, the TDM team  as well as developers and testers, can  be provided the facility to obtain, via  self-service, virtual copies of the given  source databases.<|endoftext|>8.  Roll back to a previous state:  Most database virtualization tools  provide a feature for rolling back the  database state to a previous date. This  is especially useful for testing teams.  Often, test data gets corrupted or  changed after a test cycle. By using the  roll back feature, the test data can be  restored to a previous consistent state  to enable another round of testing.<|endoftext|>9.  Roll forward: After rolling back, some  database virtualization tools provide  the facility to roll forward, if required,  to a specified date in the database  timeline.<|endoftext|>10.  Ease of administration: Database  virtualization products offer  centralization of all administrative tasks  leading to ease of administration. There  is no need to account for differences  in environment configurations in each  non-production environment where  the target database is to be deployed.


Continue # Infosys Whitepaper
  These features have the potential to bring  significant cost savings and efficiency  improvements from a TDM perspective.<|endoftext|>TDM use cases TDM processes can be broadly divided  into data refresh and data provisioning  processes. The data refresh process involves  refreshing a non-production database with  required datasets. The data provisioning  process is concerned with mining this data  and allocation of identified records to end  users. Database virtualization is applicable  External Document © 2018 Infosys Limited

---

  Page: 5 / 8

---

 to the former process viz. data refresh. Let  us look at some relevant cases of how it can  be leveraged for TDM: a) Database virtualization in non- production environments As we have seen, in the traditional  approach, each non-production database is  a physical copy or subset of the production  copy. With a database virtualization  tool, the non-production environments  are virtual database clones. An added  advantage here is that if the data in any  environment is corrupted –- let’s say after  a round of testing –- it is very easy to  revert the data back to its original state.  Some database virtualization tools provide  support for data masking, which is a key  requirement of most TDM implementations.  A simplified depiction of this scenario is  shown below: Production  Database Non-production environment setupby  virtual cloning of production database Virtual Clone 1 Virtual Clone 2 Virtual Clone 3 Database  virtualization  engine[+ Data  masking] b) Database virtualization with data  masking Data masking is often a key TDM  requirement and not all database  virtualization tools support it. In this case,  an intermediate database can be setup,  which will store the masked data and serve  as the source database for the database  virtualization engine. The intermediate  database might be a full or partial copy of  the production database. Data masking can  be achieved by either using industry  standard TDM tools or custom scripts.<|endoftext|>Virtual Clone 2 Virtual Clone 3 Virtual Clone 1 Mask Non-production environment setup  with data masking and virtual cloning Production Database Data extraction/ sub-setting Intermediate Database Data masking  utility Database  virtualization  engine c) Database virtualization with data  masking and synthetic data creation In practice, there may be several data  requirements from data consumers that  cannot be fulfilled from production  databases, as the data is unavailable. This  may be the case, for example, in new  development programs that may require  data for testing. In this case, a synthetic  data creation tool can be used to generate  data, which in turn can be inserted into the  intermediate database. As the intermediate  database is being used as the source for the  database virtualization engine, it will  ensure that the virtual database clones  reflect the generated data, in addition to  the production data.<|endoftext|>Virtual Clone 2 Virtual Clone 3 Virtual Clone 1 Mask Non-production environment setup with  synthetic data generation and virtual cloning Production Database Data extraction/ sub-setting Intermediate Database Data masking  utility Database  virtualization  engine Data  generation Benefits for TDM The key benefits that database  virtualization can provide for TDM are: 1.  Faster test data setup and refresh:  Database virtualization can be  leveraged for rapidly provisioning a  database clone from a source database;  for example, production, disaster  recovery, a gold copy etc. Similarly,  refreshing a virtual database clone can  be executed quite quickly.<|endoftext|>2.  Cost savings: Test databases,  being virtual clones, do not require  physical storage space. Also, database  virtualization tools do not maintain full  copies of the data — only the changes  in data are tracked and logged.  This results in significant savings in  hardware costs.<|endoftext|>3.  Increased reuse:  Most database  virtualization tools provide point- in-time snapshots. Thus, if there is a  need, for example, to repeat a round  of testing or a specific test case, it is  easy to roll back the database to a  previous state.  External Document © 2018 Infosys Limited

---

  Page: 6 / 8

---

 4.  Increased test environment  availability: As virtual database clones  have a significantly lower resource  utilization as compared to physical  databases, it is feasible to have larger  number of test databases at any given  point in time. This can significantly  eliminate environment contentions  and increase productivity.<|endoftext|>5.  Enable TDM for DevOps: DevOps  teams can rapidly provision data for  dev and test environments using  self-service features, thus enabling  continuous integration.<|endoftext|>Best practices While considering database virtualization  for TDM, the following best practices  should be followed: 1.  Conduct product fitment: There are  several robust database virtualization  products available in the market today,  with significantly varying feature- sets and technology compatibility.  Hence, it is an imperative to carry out  a comprehensive product fitment  analysis before selecting the right  product, keeping in mind the current  and long term needs.<|endoftext|>2.  Protect sensitive data: Production  databases often contain sensitive  information that if exposed can  result in serious data breaches. It is  imperative to have a mechanism in  place to mask sensitive information  so that the virtual database clones  provisioned for development and  testing are properly desensitized.  One strategy could be to leverage a  database virtualization product that  inherently supports data masking or  even setting up a staging database that  has desensitized data as the source  database for the virtualization engine  (instead of using the production  database directly as the source).  3.  Plan for data reusability: As database  states can be easily rolled back and  rolled forward, a data reuse strategy  should be put in place to effectively  utilize this feature for relevant scenarios  (for example, regression testing cycles).   4.  Enable self-service: Relevant  development / testing team members  should be provided access to create  virtual database clones to decrease the  dependency on DBAs.  5.  Monitor performance metrics: Key  database performance metrics, such  as SQL query response time, need  to be monitored before and after  virtualization, so that corrective action  may be taken accordingly.<|endoftext|>Database virtualization  product examples Listed below are a few database  virtualization tools available in the market  today, which can create virtual database  clones. As this technology is still maturing  and evolving, the databases supported by  these vendors are likely to increase soon: # Tool Databases  supported 1 Delphix DaaS Oracle, SQL  Server,  Sybase, DB2,  PostGres, MySQL 2 Actifio  Copy Data  Virtualization Oracle, MS SQL  Server 3 NetApp  FlexClone Oracle 4 EMC XtremIO Oracle, MS SQL  Server 5 VMware  vFabric Data  Director Oracle, SQL  Server,  MySQL External Document © 2018 Infosys Limited

---

  Page: 7 / 8

---

 Conclusion As compared to the traditional approach,  database virtualization offers significant  opportunities in terms of cost optimization  and efficiency improvements in non- production environments. The features  offered by these tools are specifically  useful for databases used for development  and testing purposes. The key benefits of  leveraging database virtualization for TDM  are faster test data setup, cost savings in  disk space and increased reusability of  test data. Moreover, the ability to provide  self-service, coupled with features like ease  of refresh, taking point-in-time snapshots,  write backs to the source database and  ability to roll back any changes made  can be a game-changer in the effective  management of test data. Enterprises  would be well advised to take a serious  look at database virtualization tools,  irrespective of whether they have a formal  TDM implementation in place.<|endoftext|>External Document © 2018 Infosys Limited

---

  Page: 8 / 8

---

 © 2018 Infosys Limited, Bengaluru, India. All Rights Reserved. Infosys believes the information in this document is accurate as of its publication date; such information is subject to change without notice. Infosys  acknowledges the proprietary rights of other companies to the trademarks, product names and such other intellectual property rights mentioned in this document. Except as expressly permitted, neither this  documentation nor any part of it may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, printing, photocopying, recording or otherwise, without the  prior permission of Infosys Limited and/ or any named intellectual property rights holders under this document.  For more information, contact askus@infosys.com Infosys.com | NYSE: INFY Stay Connected

***


# Infosys Whitepaper
Title: Today, the most popular form of evaluating an individual capabilities and competency level in any organization is done by Appr
Author: Infosys Technologies
Format: PDF 1.4

---

  Page: 1 / 12

---

   Presented at the 3rd International Software Testing Conference, India  The When & How of Test Automation  Vivek Motwani  Programmer Analyst  Product Competency Center  Infosys Technologies Limited, Bangalore    Abstract  Test automation has always been looked upon as a magic formula to improve the quality  processes of products/applications right from the day when first commercial product/application  was made. But when one actually starts automating the testing, the ground realities are realised.  More often than not, the teething troubles of deciding the right time to go for automation,  defining the scope of automation and selection of right tool for automation are over-whelming in  the first place. And even if these teething troubles are overcome, the automation tool developed is  usually inefficient as lots of important considerations are over-looked. This paper aims to suggest  the solution of these issues, and suggest best practices to be followed while doing the automation  so as to maximise the efficiency of the automation tool developed.  Introduction  Automation is the only long-term solution for reduced costs in software testing and better quality  products. But these aims are achieved only when certain best practices are followed before and  while developing the automation suite.  Howard Fear has aptly stated, "Take care with test automation. When done well, it can bring  many benefits. When not, it can be a very expensive exercise, resulting in frustration”. [3]  More often that not, after automating the testing of a product, the automation team finds the  automation tool more of a headache because of the unplanned and thoughtless approach adopted  while developing the tool. Generally, lots of effort is spent in developing the tool, only to  discover that the tool is limited in scope, lacks user-friendliness and requires frequent re-work  every now and then.  © QAI India Ltd, 3rd Annual International Software Testing Conference, 2001. No use for profit permitted.

---

  Page: 2 / 12

---

   Presented at the 3rd International Software Testing Conference, India  And if sufficient care is exercised and proper practices are followed before and while automating  the same product/application, the resulting automation tool not only saves time and effort, but is  also a sheer beauty in itself because of the amount of user-friendliness, flexibility, reusability and  extensibility it ensures.  Let us, therefore, discuss what all needs to be taken care of before going for test automation and  also while actually doing the automation.  Automation when?  (The Desiderata)  Lots of effort has to be spent even before you actually start with automation. It needs to be  ensured that following things have been taken care of: -  Stability of the product/application is ensured: The first thing that needs to be ensured is that  the product/application is fairly stable in terms of functionality. Even if it is slated to incorporate  new features, the new features should not disturb the existing functionality. There is no sense in  automation the testing of a product that is supposed to change functionality-wise.  Besides, the error messages generated by the product/application should remain consistent across  different releases. If the testing is GUI-based, then it needs to be ascertained that the future  releases of the product would not be undergoing GUI changes which might prove critical for the  automation suite.  Interface to be tested has been identified: Three different interfaces a product might have are  command line interfaces (CLIs), application-programming interfaces (APIs), and graphical user  interfaces (GUIs). Some may have all three, but many will have only one or two. These are the  interfaces that are available to you for your testing. By their nature, APIs and command line  interfaces are easier to automate than GUIs. Find out if your product has either one; sometimes  these are hidden or meant for internal use only. After this, you need to decide which interface’s  testing has to be automated. Some relevant points are: -  © QAI India Ltd, 3rd Annual International Software Testing Conference, 2001. No use for profit permitted.

---

  Page: 3 / 12

---

   Presented at the 3rd International Software Testing Conference, India  � GUI test automation is more difficult than test automation of the other two interfaces.  This is because firstly, GUI test automation will invariably require some manual script  writing. Secondly, there will always be some amount of technical challenge of getting the  tool to work with your product. Thirdly, GUI test automation involves keeping up with  design changes made to a GUI. GUIs are notorious for being modified and redesigned  throughout the development process.  � Despite the reasons for not depending on GUI test automation as the basis for testing  your product functionality, the GUI still needs to be tested, of course, and you may  choose to automate these tests. But you should have additional tests you can depend on to  test core product functionality that will not break when the GUI is redesigned. These tests  will need to work through a different interface: a command line or API.  � In order to simplify the testing of an API, you may want to bind it to an interpreter, such  as TCL or Perl or even Python. This enables interactive testing and should also speed up  the development cycle for your automated tests. Working with API’s may also allow you  to automate unit tests for individual product components.  Scope of automation has been defined: Before setting out to automate the testing of your  application/product, it is essential to define the scope/intended coverage of the automation tool.  The scope may encompass functionality testing, regression testing or simply acceptance testing.  You can even select to automate the testing of certain particular features or certain selective  testcases of different features.   Individual testcases to be automated have been identified: Automation suite should be looked  upon as a baseline test suite to be used in conjunction with manual testing, rather than as a  replacement for it. It should aim at reducing the manual testing effort gradually, but not doing  away with manual testing altogether. It needs to be understood that automation can aid manual  testing effort but cannot replace manual testing. What machines are good at and humans are slow  at should be chosen for automation. Setting realistic goals in early stages of test automation is  © QAI India Ltd, 3rd Annual International Software Testing Conference, 2001. No use for profit permitted.

---

  Page: 4 / 12

---

   Presented at the 3rd International Software Testing Conference, India  important for achieving long-term success. So, even after defining the scope of the automation  tool in terms of acceptance/regression testing, etc, it needs be made sure that following kinds of  testcases are eliminated from the scope of automation: -  � Testcases that are long and complicated and require manual inspection/intervention in  between.  � Testcases that take tremendous amount of time in automation and it is difficult to ensure  re-usability even if they are automated.  � Testcases pertaining to usability testing. Usability testing means testing in a true end-user  environment in order to check whether the system is able to operate properly in  accordance with the exact set of processes and steps applied by the end-user, including  user's interface and system convenience estimation.  It’s very important to include the right testcases in the suite. If the selection of testcases for the  automation suite is not meticulous, you might end up discovering nothing really important about  the software you are testing even if you develop a highly robust and reliable test suite.  Testcases have been fine-tuned: The testcases need to be fine-tuned for automation. The  expectation level from the testcases for automating is widely different from the expectation from  manual testing point-of-view. The salient features that need to be taken care of include: -  � Manual regression tests are usually documented so that each test picks up after the  preceding test, taking advantage of any objects or records that may already have been  created. Manual testers can usually figure out what is going on. A common mistake is to  use the same approach with automated tests. But because of this approach, a failure in  one test will topple successive tests. Moreover, these tests also cannot be run  individually. This makes it difficult to use the automated test to help analyze legitimate  failures. So, it is advised to revamp the testcases so as to make them independent. Each  testcase should setup its test environment.  © QAI India Ltd, 3rd Annual International Software Testing Conference, 2001. No use for profit permitted.

---

  Page: 5 / 12

---

   Presented at the 3rd International Software Testing Conference, India  � The testcases need to be equipped with proper test-data. E.g. –


Continue # Infosys Whitepaper
 If there is a testcase for  uploading of a file, then it should explicitly tell which file to upload. If there is a testcase  for creating a folder with invalid characters, then it should state which characters to use  for creating the folder.  Such fine-tuning of the testcases before starting automation ensures reduction in the actual time  for developing the tool. It also guarantees that the tool actually executes the testcases in a way  that checks the desired functionality.  The right tool has to be decided: There are hundreds of automation tools available in the  market. A careful effort has to go into deciding which tool would be most suitable for automating  the testing of your product/application. Following criteria would be useful in making the decision:  � Is the automation suite required to work on different platforms? If platform-  independence is required, the demands on the automation suite will be very high. E.g. – If  the suite has to support different flavors of Unix, it might be suitable to go for platform- independent things like perl, etc.  � If the testing to be automated is GUI-based, it might be preferable to use a tool like  SilkTest, WinRunner, Rational Robot, etc. But every tool will have its own technical  limitations that prevent efficient automation. So, it is necessary to evaluate testing tools  for critical interfaces of the application that need to be automated.  � Sometimes, it might be best to develop a scripting tool using a suitable scripting language  instead of going for the ready-made tools available in the market. This is especially  preferable when the testing is on the server side.    The right mode (script recording/script development) has been decided: Most of the GUI  automation tools have a feature called ‘record and playback’ or, ‘capture replay’. Using this  feature, you execute the test manually while the test tool sits in the background and remembers  what you do. It then generates a script that you can run to re-execute the test. Script development,  on the other hand, implies writing the scripts for running the testcases in the language used by the  tool. Script development is akin to programming in a language like C or C++, but the purpose is  to execute the testcases in an automated style.   © QAI India Ltd, 3rd Annual International Software Testing Conference, 2001. No use for profit permitted.

---

  Page: 6 / 12

---

   Presented at the 3rd International Software Testing Conference, India  If you are going for GUI test automation, then points worth-considering while making a sane  decision are:  � Record and Playback approach to creation of test scripts and test suites is easy to develop  but difficult to maintain.  � Error recovery cannot be incorporated by just recording a test script.  � In data driven tests, achieving reusability of test scripts will be very limited. Creation of  test data and integration of the same with test scripts is the time consuming part. When a  function is coded for the same purpose with data input file, maximum re-usability and  ease is ensured.  More often than not, it will be required to strike a careful balance between the two modes, instead  of using one of the two modes. Using the recording mode alone will render the automation suite  non-reusable and using the scripting mode alone will require more investment of effort and time.  Though a middle path will be suggested generally, it might be worthwhile spending some time to  decide the right mode or right mix of modes as per the application/product under consideration.  Most of the further discussion will be useful only when the right mix is adopted or scripting is  followed altogether.  All in all, the suggested steps to be followed before starting with automation can be depicted in  the figure below: -  \            Fig.1: The pre-automation stage cycle      Check the stability  of the product /  application Decide the  interface to be  tested Define the scope  of automation  Identify  individual  testcases Fine-tune the test  case documents  Decide the right  tool  Decide the right mode/ right mix  of modes © QAI India Ltd, 3rd Annual International Software Testing Conference, 2001. No use for profit permitted.

---

  Page: 7 / 12

---

   Presented at the 3rd International Software Testing Conference, India  Automation how?  (The Regimen)  After taking care of the above stipulations, the right direction has been identified and now the  stage is all set to go for automation full-fledged. But in order to reach the destination, lots more  needs to be paid attention to. So, here we go: -  Following proper test scripting standards: Automated testing involves a mini-development  cycle. So, proper coding standards for test scripts should be prepared. Checklists should be  developed for review of test scripts. On the whole, all the software practices followed in the  development of an application or a product, which are applicable to the development of the  automation suite, should be put in place. Whatever tool is chosen, ultimately, a tool will be only  as good as the process being used to implement the tool.  Identifying common steps and converting them into functions: At the outset, the steps  common amongst different testcases should be identified and converted in the form of functions.  Such functions can be placed in a common file, from where they can be called by different  testcases by passing suitable parameters as per the need. This will encourages re-usability of code  and save effort and time. Besides, these functions can be used again when newer testcases are  added to the automation suite at a later stage.  Identifying other peripheral functions: After the functions as stated above have been identified,  it is advisable to identify the peripheral functions that will be required by all the testcases in  general. E.g. – A separate function for writing into log files can be written. This function can take  the error message, severity level of the error message and the path and name of the log file as the  input parameters. Depending on the requirements, more of such reusable functions can be  identified. Such functions will simplify and streamline the process of test script development in  the long run.  Providing room for extensibility: The automation suite should be written in a manner such that  additional testcases can be added to it. The additional testcases may cater to testing enhanced  © QAI India Ltd, 3rd Annual International Software Testing Conference, 2001. No use for profit permitted.

---

  Page: 8 / 12

---

   Presented at the 3rd International Software Testing Conference, India  functionality of an existing feature as well as testing new features incorporated in the  application/product. The suite should have such an architecture that it is extensible both in terms  of being able to add more functions and also in terms of being able to add more testcases by  calling the existing/new functions.  Generating proper logs: A common problem is what to do when automated tests fail. Failure  analysis is often difficult. Was this a false alarm or not? Did the test fail because of a flaw in the  test suite, a mistake in setting up for the tests, or an actual defect in the product? Hence, it is  required that the suite should generates logs of its own. But a good automation suite with  ambiguous logging messages is worse than manual testing. Few points that need to be taken care  of from logging point-of-view are: -  � An ideal automation suite should explicitly check for common setup mistakes before  running tests and generating detailed logs of its own. And logging needs to be as user- friendly as possible.  �  The logging should be done in a manner that facilitates statistical analysis of the results.  This implies that the log file should have the results in such a format such that can be  processed by parsing, and useful statistics can be generated.  Independence of selective execution: The scripts should be written/arranged in such a manner  that they provide the independence of executing individual testcases or at least testcases  belonging to the same module. This is important when the need is not to execute the entire suite,  but to verify particular bugs.  Signal-handling and clean exit on abrupt termination: It needs to be ensured that the suite  does all the clean up when terminated abruptly, consciously or unconsciously, by the user. It may  be required by the script to handle the termination/kill signal for a while so as to get the time for  clean up (and may be, complete the currently executing testcase, if the suite desires). Such signal  handling is extremely important in some particular cases. E.g. - When an automation suite is run  © QAI India Ltd, 3rd Annual International Software Testing Conference, 2001. No use for profit permitted.

---

  Page: 9 / 12

---

   Presented at the 3rd International Software Testing Conference, India  through command line on a Unix terminal as a foreground process and the user does a Ctrl-D in  order to stop the suite for whatever reasons. The


Continue # Infosys Whitepaper
 suite might have changed some configuration  files or properties files before it received the signal. So, if the changes are not reverted back  before the termination of the suite, then things will go for a toss.  Self-sufficiency in individual testcases: Testcases should not be dependent on preceding  testcases for execution. If there is dependency on testcases occurring before in the sequence, then  the subsequent testcases will fail without any reason. If at all such dependence is unavoidable, the  error message in the log file, when such testcases fail because of the failing of preceding testcase,  should be explanatory enough.  Equipped with test data: The automation suite should be equipped with all the test data required  by the different testcases. The test data may consist of simple data input as required by the  testcases to supply parameters to the functions for testing different conditions like numeric input,  alpha-numeric input, non-alpha-numeric input, etc. It may as well consist of specific files to be  supplied to the testcases to test particular functionality of the application/product. The automation  suite has to be accompanied with such test data and this test data has to be prepared for the suite  with precision. Example: - A particular feature of the application/product may have to be tested  with files of different sizes, say 0 bytes, 64 KB, 1MB, 30 MB, etc. So, the suite requires to have  the files precisely of these sizes only. All such files may be kept in a particular folder from where  the suite picks them up. The regular input data, which is required by the functions as parameters  can be supplied through the input data files. The individual testcases may parse the parameters to  be supplied to the testcases while reading them from the input data files. The tools available in the  market support different types of file to be used as data input files. Example: - WinRunner uses  excel sheets for reading data, while SilkTest uses.dat files.  Dynamic generation of names for temporary files and input data: Sometimes, the automation  suite would require to create certain temporary files. If the suite does not delete the temporary  files created by itself, then they will get over-written in the next run of the suite. Besides, if a file  © QAI India Ltd, 3rd Annual International Software Testing Conference, 2001. No use for profit permitted.

---

  Page: 10 / 12

---

   Presented at the 3rd International Software Testing Conference, India  by the same name exists even before the first run of the suite, then that file may get over-written  in the first run itself. The consequence will be even worse if the write permission is not there on  the already existing file. The script will fail to over-write also in such a case and the testcase  might eventually bombard. Similar problems are faced when the suite contains a positive  testcases like creating a folder with a given name. If the suite does delete this folder created as a  part of the clean-up process, the testcases fails unnecessarily when the suite is run again with the  testcase trying to create a folder with the same name.   A solution to all such problems is to dynamically generate the names for temporary files  and all such input data at the run time. This way the names will not conflict with those of the  existing files and fresh data. Such dynamic generation of names can be accomplished by several  ways. One typical way of generation can be stripping the microsecond part of the current time  and appending it to a name. This way there will be an extremely rare probability (10 to the power  of –6, to be precise) that a conflict in the names will take place.  Cleaning-up: It has to be ensured that the automation suite brings the application/product back to  the original state it was in before the suite executed. If any configuration or properties file was  changed for the execution of some testcase, then the changes must be reverted back. If the suite  generates some temporary files, they should be deleted by the suite towards the end.  Incorporating user-friendliness: The automation suite should be as user-friendly as possible.  Some basic points for ensuring user-friendliness are: -  � The user should have freedom to put the test data files anywhere on the m/c.  � The suite can be run from anywhere on the m/c.  � It can be installed anywhere on the m/c.  � Once it is run, the suite should not require any manual intervention till completion. The  user should be able to run the suite unattended.  For incorporating such user-friendliness, the suite needs to be designed in a proper way. A  separate configuration file can be created that contains all the variables that the user might want  © QAI India Ltd, 3rd Annual International Software Testing Conference, 2001. No use for profit permitted.

---

  Page: 11 / 12

---

   Presented at the 3rd International Software Testing Conference, India  to change. E.g. – The user might want the log files to be generated on the desktop instead of a  hard-coded path. The user might as well want the suite to pick-up the test data/files from a  directory of his choice. All such entities can be placed in the configuration file in the form of  variables that the user can change easily. The suite can read these variables from the  configuration files every time it is run. If such a design is used, all that the user would need to do  before running the script is to change the configuration file as per his needs. Thus, the user will  get a tremendous amount of flexibility and independence.  Developing an efficient error recovery routine: Error Recovery routine enables the test suite to  run continuously unattended. The function of this routine is to anticipate errors, decide on  corrective action, log the error and proceed further with next test, if possible. E.g. - If unexpected  termination of application under test happens, the routine should recognize the interruption and  restart the application. This prevents cascading effect or reporting wrong defects after a test suite  execution. In a nutshell, this will ensure that failures in test execution are effectively trapped,  interpreted and suite continues to run without failures. Without such an error recovery system,  automated test suite runs will never take off. Manual presence will become a necessity during test  suite execution.  Test scripts for test data setup and cleaning up: If the automation suite does not take care of  test data setup, it will have to be done manually by the user, which reduces the fun of test  automation. This becomes all the more important when test data setup requirements are huge and  as a result, the whole exercise become highly time consuming. Hence, an ideal automation suite  should incorporate dedicated scripts for test data set-up. These scripts are executed before any  other functionality test can be executed on the product. E.g. – When the application/product in  focus is an ERP suite or a banking software, the test data setup part itself may take 3-4 man-days  of effort. With the automation in place for this setup, the effort is reduced drastically.    Similarly, scripts for cleaning-up should also be incorporated in the automation suite.  Such scripts will aim at bringing the application to the ground state it was in before the  © QAI India Ltd, 3rd Annual International Software Testing Conference, 2001. No use for profit permitted.

---

  Page: 12 / 12

---

   Presented at the 3rd International Software Testing Conference, India  automation suite was run, i.e., they will undo all the changes that any testcases in the suite  brought about while executing. E.g. – If there is a testcases for creating a folder, then the clean-up  action will delete this folder.  Testing the test scripts: Test scripts should be tested before they are used in a test suite. Testing  of all test scripts should be planned in test automation activity. Adequate tests need to be  performed for each test script. When test error simulation and rectification is difficult and time- consuming process, reporting false errors can cost more and defeat the objective. The goal for the  automation team has to be that a test program should never report a false problem. All scripts  should satisfy the following criteria: -  � When given a valid input, they produce the correct output.  � When given an invalid input, they correctly and gracefully reject the input.  � Do not hang or crash, given either valid or invalid input.    Conclusion  Test automation is a great idea. But it is not a magic wand. Proper time and effort has to be spent  for the development of the test automation suite. And the key is to follow the right processes. In  eagerness to achieve fast results, the desirable processes are compromised. And that is the reason  why, more often than not, it only promises and raises hopes, but simply fails to deliver.   Acknowledgement  I wish to express my sincere gratitude towards Sridhar Kumanduri and KiranK


Continue # Infosys Whitepaper
umar Marri for  sharing their experience in test automation with me and giving me extremely valuable feed-back.  References  1. Bach, James. 1996. “Test Automation Snake Oil.” Windows Technical Journal, (October).  http://www.satisfice.com/articles/test_automation_snake_oil.pdf  2. Success with Test Automation by Bret Pettichord (bret_pettichord@bmc.com)  3. Howard Fear on Test Automation by Howard Fear (hsf@pageplau.com)  4. Automated Testing: A Practical Approach for ERP product by Kishore C.S.  (cs@rsi.ramco.com)  © QAI India Ltd, 3rd Annual International Software Testing Conference, 2001. No use for profit permitted.

***


Infosys Press Release (PR)
Title: Infosys Public Services Expands in Canada
Author: ['Infosys Limited'] Infosys Public Services (IPS), a North America-based company of Infosys (NSE, BSE, NYSE: INFY), today announced the opening of its new subsidiary, Infosys Public Services Canada, Inc. (IPS Canada) headquartered in Ottawa, Ontario with local offices in Mississauga ON, Calgary AB, and Burnaby BC. IPS Canada accelerates digital transformation for public sector organizations across the country, including federal departments, provincial ministries, municipalities, and crown corporations, and provides access to top tier IT talent and innovative solutions to improve the delivery of government services to Canadians.<|endoftext|> Infosys Public Services’ Canadian expansion marks the next phase of its decade-plus presence in the country and is the logical next step for the company given its growth in Canada and the evolving government security standards and regulation. This IPS Canada announcement is the latest development in a series of investments made by Infosys which has expanded the employee count to over 7,000 with a commitment to increase to 8,000 employees by 2024. IPS Canada will also work with local universities and technical colleges to recruit talent.<|endoftext|> Bhanu Prasad Narayan, Interim CEO, Infosys Public Services, said, “The Canadian incorporation of Infosys Public Services Canada, Inc. underscores our continued commitment to our public sector clients, as we help them modernize service delivery for Canadian citizens and businesses. Our offices will enable us to tap into strong local talent across the country to support continued business growth in the region.”  Franco Chirichella, President and CEO, Innovapost, said, “As one of Innovapost’s key strategic partners, Infosys Public Services Canada has helped us successfully deliver IT initiatives to meet the demands of the evolving mail, courier and logistics industry. IPS Canada does a great job of bringing the breadth and depth of their global and Canadian capabilities to Innovapost to support us in meeting our business and technical needs.”  IPS Canada will help modernize public sector service delivery for new and existing Federal, Ontario, and Manitoba government and crown corporation clients, creating resiliency for their core business systems and processes with digital and cloud solutions. The IPS Canada headquarter in Ottawa is a 10,000 square feet digital center. The facility is designed to allow the delivery of managed services that can comply with the security requirements associated with delivering services to each level of government. It is located at 275 Slater Street, Suite 501 in downtown Ottawa.<|endoftext|> To learn more about IPS Canada, please visit: www.infosyspublicservices.com/Canada.<|endoftext|> About Infosys Public Services  Infosys Public Services is a leader in next-generation digital services and consulting. With benchmark processes, access to cross-industry insights and innovative public sector solutions, Infosys Public Services is helping public sector organizations to navigate their digital transformation, helping them renew existing systems into modern, agile, intelligent platforms, develop new capabilities and deliver better outcomes to all stakeholders at a lower cost with less risk.<|endoftext|> Navigate your next with Infosys Public Services. Visit www.infosyspublicservices.com to learn how.<|endoftext|> About Infosys  Infosys is a global leader in next-generation digital services and consulting. Over 300,000 of our people work to amplify human potential and create the next opportunity for people, businesses and communities. We enable clients in more than 56 countries to navigate their digital transformation. With over four decades of experience in managing the systems and workings of global enterprises, we expertly steer clients, as they navigate their digital transformation powered by the cloud. We enable them with an AI-powered core, empower the business with agile digital at scale and drive continuous improvement with always-on learning through the transfer of digital skills, expertise, and ideas from our innovation ecosystem. We are deeply committed to being a well-governed, environmentally sustainable organization where diverse talent thrives in an inclusive workplace.<|endoftext|> Visit www.infosys.com to see how Infosys (NSE, BSE, NYSE: INFY) can help your enterprise navigate your next.<|endoftext|> Safe Harbor  Certain statements in this release concerning our future growth prospects, or our future financial or operating performance are forward-looking statements intended to qualify for the'safe harbor' under the Private Securities Litigation Reform Act of 1995, which involve a number of risks and uncertainties that could cause actual results or outcomes to differ materially from those in such forward-looking statements. The risks and uncertainties relating to these statements include, but are not limited to, risks and uncertainties regarding the execution of our business strategy, our ability to attract and retain personnel, our transition to hybrid work model, economic uncertainties, technological innovations such as Generative AI, the complex and evolving regulatory landscape including immigration regulation changes, our ESG vision, our capital allocation policy and expectations concerning our market position, future operations, margins, profitability, liquidity, capital resources, and our corporate actions including acquisitions. Important factors that may cause actual results or outcomes to differ from those implied by the forward-looking statements are discussed in more detail in our US Securities and Exchange Commission filings including our Annual Report on Form 20-F for the fiscal year ended March 31, 2023. These filings are available at www.sec.gov. Infosys may, from time to time, make additional written and oral forward-looking statements, including statements contained in the Company's filings with the Securities and Exchange Commission and our reports to shareholders. The Company does not undertake to update any forward-looking statements that may be made from time to time by or on behalf of the Company unless it is required by law.<|endoftext|> Media contacts:  For more information, please contact: PR_Global@infosys.com

***


Infosys Press Release (PR)
Title: International Tennis Hall of Fame and Infosys Launch Immersive Metaverse Museum Experience
Author: ['Infosys Limited'] Infosys (NSE, BSE, NYSE: INFY), a global leader in next-generation digital services and consulting, and the International Tennis Hall of Fame today announced the debut of a dynamic Metaverse museum, bringing the ITHF experience to tennis fans around the world. In a Hall of Fame first, this deeply interactive, immersive offering brings the museum’s collection and the stories of its Hall of Famers into the Metaverse. The ITHF Metaverse is now available at tennisfame.com/metaverse, with a virtual reality experience currently in development.<|endoftext|> In the Metaverse, fans can experience the hallowed grounds of the ITHF, combining real and virtual elements. They can view larger-than-life holographic statues of Hall of Famers and learn about the legends via their careers, stats, trivia and more. As a user navigates the Metaverse, they can browse through a number of different Hall of Famers and artifacts to find out more and answer trivia questions to earn points to claim rewards in the ITHF virtual shop.<|endoftext|> Featured Hall of Famers include Martina Navratilova, Rod Laver, Billie Jean King, Arthur Ashe and 2023 inductee Esther Vergeer, among many others. Fans can discover iconic items from throughout tennis history in the Hall of Fame’s collection, including an original pair of Stan Smith Adidas sneakers, a racquet used by Stefanie Graf during her Golden Slam in 1988, and a dress worn by Serena Williams at the 2018 US Open designed by Virgil Abloh.<|endoftext|> “Infosys and the International Tennis Hall of Fame have embarked on a truly transformational process to take the physical museum into a 3D digital environment,” said Dan Faber, CEO, ITHF. “Induction into the Hall of Fame is the ultimate honor in tennis, and Newport is where a player’s career is cemented in history. This cutting-edge experience takes history beyond borders and provides an immersive avenue for fans of all ages to be inspired by the legends’ careers, accomplishments and stories.”  “Carefully crafted digital infrastructure is taking center stage, enhancing our understandings of and interactions with experiences,” said Sumit Virmani, Infosys EVP and Global Chief Marketing Officer, Infosys. “Through this Metaverse, Infosys and the International Tennis Hall of Fame are bridging physical and digital worlds to redefine the fan experience and bring fans closer to their favorite historical moments. It has created a strong digital foundation for the ITHF to experiment and engage new tennis enthusiasts with the history and heritage of the sport on platforms accessible to the millions of fans around the world.”  Within the experience, users can express themselves through many fun personalization options, including snapping photos to create and customize their digital avatars, chatting with friends, watching videos and feeling like they are truly on the grounds of the ITHF in Newport. Users can also step foot on the famous grass Horseshoe Court and play a game of tennis at the iconic venue.<|endoftext|> The new ITHF experience launches just weeks ahead of the upcoming Infosys Hall of Fame Open and the Induction of wheelchair tennis legends Esther Vergeer of the Netherlands and Rick Draney of the United States, to be held Saturday, July 21 in Newport.<|endoftext|> Beyond the Metaverse, the Infosys Hall of Fame Open hosted by the ITHF will also leverage innovations like the Infosys Match Centre, providing fans with rich AI-powered insights and new ways of following the tennis action during the tournament. Additionally, players will be able to record and offset their carbon footprint to Newport through the recently launched Carbon Tracker developed by Infosys in collaboration with the ATP.<|endoftext|> About the International Tennis Hall of Fame  The International Tennis Hall of Fame (ITHF) is a non-profit organization that preserves and promotes the history of tennis and celebrates its champions, thereby serving as a vital partner in the growth of tennis globally. The ITHF is located in Newport, Rhode Island, in the United States, with Hall of Famers hailing from 27 nations around the world. The Hall of Fame honors these legends and chronicles the sport’s history in a comprehensive interactive museum in Newport and programming to celebrate the sport around the world. For information on the International Tennis Hall of Fame and its programs, visit tennisfame.com.<|endoftext|> About Infosys  Infosys is a global leader in next-generation digital services and consulting. Over 300,000 of our people work to amplify human potential and create the next opportunity for people, businesses and communities. We enable clients in more than 56 countries to navigate their digital transformation. With over four decades of experience in managing the systems and workings of global enterprises, we expertly steer clients, as they navigate their digital transformation powered by the cloud. We enable them with an AI-powered core, empower the business with agile digital at scale and drive continuous improvement with always-on learning through the transfer of digital skills, expertise, and ideas from our innovation ecosystem. We are deeply committed to being a well-governed, environmentally sustainable organization where diverse talent thrives in an inclusive workplace.<|endoftext|> Visit www.infosys.com to see how Infosys (NSE, BSE, NYSE: INFY) can help your enterprise navigate your next.<|endoftext|> Safe Harbor  Certain statements in this release concerning our future growth prospects, or our future financial or operating performance are forward-looking statements intended to qualify for the'safe harbor' under the Private Securities Litigation Reform Act of 1995, which involve a number of risks and uncertainties that could cause actual results or outcomes to differ materially from those in such forward-looking statements. The risks and uncertainties relating to these statements include, but are not limited to, risks and uncertainties regarding the execution of our business strategy, our ability to attract and retain personnel, our transition to hybrid work model, economic uncertainties, technological innovations such as Generative AI, the complex and evolving regulatory landscape including immigration regulation changes, our ESG vision, our capital allocation policy and expectations concerning our market position, future operations, margins, profitability, liquidity, capital resources, and our corporate actions including acquisitions. Important factors that may cause actual results or outcomes to differ from those implied by the forward-looking statements are discussed in more detail in our US Securities and Exchange Commission filings including our Annual Report on Form 20-F for the fiscal year ended March 31, 2023. These filings are available at www.sec.gov. Infosys may, from time to time, make additional written and oral forward-looking statements, including statements contained in the Company's filings with the Securities and Exchange Commission and our reports to shareholders. The Company does not undertake to update any forward-looking statements that may be made from time to time by or on behalf of the Company unless it is required by law.<|endoftext|> Media contacts:  For more information, please contact: PR_Global@infosys.com

***


Infosys Press Release (PR)
Title: Infosys Collaborates with Skillsoft to Foster Digital Learning Through its Springboard Platform
Author: ['Infosys Limited'] Infosys (NSE, BSE, NYSE: INFY), a global leader in next-generation digital services and consulting, today announced that it has signed a Memorandum of Understanding (MoU) with Skillsoft, a leading provider of transformative learning experiences, to revamp education and learning for students from class 6 to lifelong learners in India. Infosys will provide learners, free of cost, access to a rich repository of Skillsoft learning content designed to build technology, leadership and business, and behavioral skills through Infosys Springboard.<|endoftext|> Aimed at creating learning and employment avenues for school students, graduates, and lifelong learners, this collaboration will democratize learning for eager minds and prepare them to be future-ready. The content ranges from Skillsoft’s basic to advanced level courses covering topics such as digital transformation, artificial intelligence (AI) and machine learning (ML), data science, cloud, cybersecurity, and effective communication and presentation. To cater to beneficiaries in Tier 2 and Tier 3 cities, all content will be augmented with commentaries in multiple Indian regional languages, including Hindi, Marathi, Gujarati, Tamil and in some international languages, enabling beneficiaries across the globe to transcend linguistic barriers.<|endoftext|> “Infosys’ collaboration with Skillsoft strongly aligns with the company’s vision to democratize quality learning for lifelong learners. This collaboration, aided by commentaries in Indian regional language and international language subtitles, will transcend geographical boundaries and offer solid learning opportunities to learners across the world,” said, Thirumala Arohi, Senior Vice President and Head – Education, Training and Assessment – Infosys.<|endoftext|> “Like Infosys, Skillsoft is passionate about democratizing learning and providing access to upskilling and reskilling opportunities,” said, Apratim Purakayastha, Chief Product Officer and Chief Technology Officer, Skillsoft. “Our collaboration with Infosys will give young learners access to quality content that will help them build mission-critical leadership and technology skills needed for success in the 21st century.”  In line with its ESG Vision 2030, Infosys aims to enable digital skills at scale and empower over 10 million people in India by 2025 through the Infosys Springboard program. Infosys Springboard continues to expand its reach to learners by growing its thriving community to more than 5.5 million registered users in India, since its launch.<|endoftext|> About Infosys  Infosys is a global leader in next-generation digital services and consulting. Over 300,000 of our people work to amplify human potential and create the next opportunity for people, businesses and communities. We enable clients in more than 56 countries to navigate their digital transformation. With over four decades of experience in managing the systems and workings of global enterprises, we expertly steer clients, as they navigate their digital transformation powered by the cloud. We enable them with an AI-powered core, empower the business with agile digital at scale and drive continuous improvement with always-on learning through the transfer of digital skills, expertise, and ideas from our innovation ecosystem. We are deeply committed to being a well-governed, environmentally sustainable organization where diverse talent thrives in an inclusive workplace.<|endoftext|> Visit www.infosys.com to see how Infosys (NSE, BSE, NYSE: INFY) can help your enterprise navigate your next.<|endoftext|> Safe Harbor  Certain statements in this release concerning our future growth prospects, or our future financial or operating performance are forward-looking statements intended to qualify for the'safe harbor' under the Private Securities Litigation Reform Act of 1995, which involve a number of risks and uncertainties that could cause actual results or outcomes to differ materially from those in such forward-looking statements. The risks and uncertainties relating to these statements include, but are not limited to, risks and uncertainties regarding the execution of our business strategy, our ability to attract and retain personnel, our transition to hybrid work model, economic uncertainties, technological innovations such as Generative AI, the complex and evolving regulatory landscape including immigration regulation changes, our ESG vision, our capital allocation policy and expectations concerning our market position, future operations, margins, profitability, liquidity, capital resources, and our corporate actions including acquisitions. Important factors that may cause actual results or outcomes to differ from those implied by the forward-looking statements are discussed in more detail in our US Securities and Exchange Commission filings including our Annual Report on Form 20-F for the fiscal year ended March 31, 2023. These filings are available at www.sec.gov. Infosys may, from time to time, make additional written and oral forward-looking statements, including statements contained in the Company's filings with the Securities and Exchange Commission and our reports to shareholders. The Company does not undertake to update any forward-looking statements that may be made from time to time by or on behalf of the Company unless it is required by law.<|endoftext|> Media contacts:  For more information, please contact: PR_Global@infosys.com

***


Infosys Press Release (PR)
Title: Danske Bank Selects Infosys as Strategic Partner to Accelerate Digital Transformation
Author: ['Infosys Limited'] Infosys (NSE, BSE, NYSE: INFY), a global leader in next-generation digital services and consulting, today announced that it has signed a strategic collaboration with Danske Bank, a leading Nordic Bank, to accelerate the bank’s digital transformation initiatives with speed and scale. This collaboration will help Danske Bank achieve its strategic priorities towards better customer experiences, operational excellence, and a modernised technology landscape, powered by next-gen solutions.<|endoftext|> Headquartered in Denmark, Danske Bank provides banking services to personal and business customers, as well as large corporate and institutional customers. In a bid to accelerate the bank’s technology transformation, optimise their access to talent and capabilities and improve productivity, Danske Bank chose Infosys as its strategic partner.<|endoftext|> As part of this collaboration, Infosys will also acquire Danske Bank’s IT center in India, where over 1,400 professionals are employed. With its global expertise and industry-solutions, Infosys will accelerate the bank’s digital agenda by significantly enhancing their IT operations and capabilities, powered by Infosys Topaz, an AI-first set of services, solutions and platforms, experience design, and services that support operations.<|endoftext|> Frans Woelders, Chief Operating Officer, Danske Bank, said, “Our Forward ’28 strategy sets clear ambitions for Danske Bank to be a leading bank in a digital age. This is backed by significant investments in digitalisation and technology, including plans to further develop our customer-facing digital solutions, and modernising our technology infrastructure to enable even better customer experiences and drive operational efficiency. We have a strong starting point, and we want to further accelerate our digital and technology transformation. We have conducted a thorough process to find a partner that can help us achieve that. Infosys has the tools, experience, and expertise to support us in accelerating our transformation using cloud and AI technologies. Given Infosys’ global presence and scale, this collaboration will also give us access to wider talent pools and capabilities.”  Salil Parekh, Chief Executive Officer & Managing Director, Infosys, said, “We are delighted to bring our rich experience in financial services transformation to work for Danske Bank and help the bank accelerate its strategic growth agenda. Infosys will collaborate with Danske Bank to strengthen their core business with greater digital, cloud and data capabilities. This will help Danske Bank create more value for their customers using powerful advances in AI, including generative AI.<|endoftext|> Infosys looks forward to welcoming Danske India employees joining our team as part of this journey.<|endoftext|> Nordics is a strategic market for Infosys and this collaboration further enhances our commitment to the region. Infosys has acquired BASE Life Science in Denmark and Fluido in Finland, and recently opened a new proximity center in Gothenburg, Sweden and Oslo, Norway. With this relationship with Danske Bank, Infosys has further enhanced its localization strategy in the Nordics.<|endoftext|> Infosys expects the transactions to be completed before Q2’FY2024, subject to customary closing conditions.<|endoftext|> About Danske Bank A/S  For more than 150 years, Danske Bank has strived to be a driver of growth and development in society. We have developed in tandem with the societies we are part of, and our advisory services, expertise and financial solutions have helped individuals, families, businesses and organisations to realise their ambitions and potential. With long-term sustainable development as our ambition, we will continue to work every day to be the best possible bank, for the benefit of our customers, employees, shareholders and the societies we are part of.<|endoftext|> About Infosys  Infosys is a global leader in next-generation digital services and consulting. Over 300,000 of our people work to amplify human potential and create the next opportunity for people, businesses, and communities. We enable clients in more than 56 countries to navigate their digital transformation. With over four decades of experience in managing the systems and workings of global enterprises, we expertly steer clients, as they navigate their digital transformation powered by the cloud. We enable them with an AI-powered core, empower the business with agile digital at scale and drive continuous improvement with always-on learning through the transfer of digital skills, expertise, and ideas from our innovation ecosystem. We are deeply committed to being a well-governed, environmentally sustainable organization where diverse talent thrives in an inclusive workplace.<|endoftext|> Visit www.infosys.com to see how Infosys (NSE, BSE, NYSE: INFY) can help your enterprise navigate your next.<|endoftext|> Safe Harbor  Certain statements in this release concerning our future growth prospects, or our future financial or operating performance are forward-looking statements intended to qualify for the'safe harbor' under the Private Securities Litigation Reform Act of 1995, which involve a number of risks and uncertainties that could cause actual results or outcomes to differ materially from those in such forward-looking statements. The risks and uncertainties relating to these statements include, but are not limited to, risks and uncertainties regarding the execution of our business strategy, our ability to attract and retain personnel, our transition to hybrid work model, economic uncertainties, technological innovations such as Generative AI, the complex and evolving regulatory landscape including immigration regulation changes, our ESG vision, our capital allocation policy and expectations concerning our market position, future operations, margins, profitability, liquidity, capital resources, and our corporate actions including acquisitions. Important factors that may cause actual results or outcomes to differ from those implied by the forward-looking statements are discussed in more detail in our US Securities and Exchange Commission filings including our Annual Report on Form 20-F for the fiscal year ended March 31, 2023. These filings are available at www.sec.gov. Infosys may, from time to time, make additional written and oral forward-looking statements, including statements contained in the Company's filings with the Securities and Exchange Commission and our reports to shareholders. The Company does not undertake to update any forward-looking statements that may be made from time to time by or on behalf of the Company unless it is required by law.<|endoftext|> Media contacts:  For more information, please contact: PR_Global@infosys.com

***


Infosys Press Release (PR)
Title: Infosys to Provide Certification in AI and Generative AI skills, Crucial to Landing Jobs, through Infosys Springboard Virtual Learning Platform
Author: ['Infosys Limited'] Infosys (NSE, BSE, NYSE: INFY), a global leader in next-generation digital services and consulting, today announced that it has launched a free Artificial Intelligence (AI) certification training on Infosys Springboard. Infosys AI-first specialists and data strategists, responsible for delivering Infosys Topaz™ AI-first set of services, solutions and platforms will help shape the curriculum to help learners build future-ready skillsets.<|endoftext|> This certification will offer a variety of courses that cover a broad spectrum of topics related to AI, including an introductory course on AI and Generative AI, with a focus on deep learning and natural language processing, and a masterclass on AI and the impact of Generative AI, that will aim to focus on prompt engineering and AI-first software engineering. Additionally, a customized course on ‘Citizens Data Science’ will aim to cover various aspects of data science discipline, including python programming, linear algebra, probability and statistics, and exploratory data analysis. Learners will be awarded a certificate upon successful completion of the course.<|endoftext|> Thirumala Arohi, Senior Vice President and Head - Education, Training and Assessment at Infosys, said, “Infosys Springboard is committed to democratize quality education and strengthen the next-generation workforce with digital and life skills. Our aim is to demystify AI for learners through Infosys Springboard and help them make a conscious choice in building their careers. We firmly believe that AI proficiency will give young aspirants and professionals a competitive advantage in a dynamic and demanding job market.”  Infosys Springboard provides a curriculum-rich virtual platform that delivers corporate-grade learning experiences, on any device, with closer educator-learner collaboration for students from Class 6 to lifelong learners. This, alongside formal education, helps accelerate digital reskilling for participating learners, ranging from school and college students to professionals and adults. Since its launch, Infosys Springboard continues to expand its reach to learners by growing its thriving community to more than 5.5 million registered users. Infosys, in line with its ESG Vision 2030, aims to enable digital skills at scale and empower over 10 million people in India through the Infosys Springboard program.<|endoftext|> About Infosys  Infosys is a global leader in next-generation digital services and consulting. Over 300,000 of our people work to amplify human potential and create the next opportunity for people, businesses and communities. We enable clients in more than 56 countries to navigate their digital transformation. With over four decades of experience in managing the systems and workings of global enterprises, we expertly steer clients, as they navigate their digital transformation powered by the cloud. We enable them with an AI-powered core, empower the business with agile digital at scale and drive continuous improvement with always-on learning through the transfer of digital skills, expertise, and ideas from our innovation ecosystem. We are deeply committed to being a well-governed, environmentally sustainable organization where diverse talent thrives in an inclusive workplace.<|endoftext|> Visit www.infosys.com to see how Infosys (NSE, BSE, NYSE: INFY) can help your enterprise navigate your next.<|endoftext|> Safe Harbor  Certain statements in this release concerning our future growth prospects, or our future financial or operating performance are forward-looking statements intended to qualify for the'safe harbor' under the Private Securities Litigation Reform Act of 1995, which involve a number of risks and uncertainties that could cause actual results or outcomes to differ materially from those in such forward-looking statements. The risks and uncertainties relating to these statements include, but are not limited to, risks and uncertainties regarding the execution of our business strategy, our ability to attract and retain personnel, our transition to hybrid work model, economic uncertainties, technological innovations such as Generative AI, the complex and evolving regulatory landscape including immigration regulation changes, our ESG vision, our capital allocation policy and expectations concerning our market position, future operations, margins, profitability, liquidity, capital resources, and our corporate actions including acquisitions. Important factors that may cause actual results or outcomes to differ from those implied by the forward-looking statements are discussed in more detail in our US Securities and Exchange Commission filings including our Annual Report on Form 20-F for the fiscal year ended March 31, 2023. These filings are available at www.sec.gov. Infosys may, from time to time, make additional written and oral forward-looking statements, including statements contained in the Company's filings with the Securities and Exchange Commission and our reports to shareholders. The Company does not undertake to update any forward-looking statements that may be made from time to time by or on behalf of the Company unless it is required by law.<|endoftext|> Media contacts:  For more information, please contact: PR_Global@infosys.com

***