Cloud Quality Assurance
  • Cloud Quality Assurance

    • Are the high capital costs for the maintenance of data centres pinching your pocket?

    • Is the complicated architecture making software deployments time-consuming?

    • Are the complex legacy systems becoming too expensive to update and maintain?

    • Are you finding it onerous to scale applications as per the demands of growing businesses?

    • Do you need to move from an in-house development state to a fully managed platform?

    • Do you want to adopt a microservices architecture and take full advantage of Cloud offerings?

Share :

How we manage Cloud Migration?

Based on the needs, a due diligence study is done on all existing applications managed in a data centre and depending upon the current state of each application one of the following is adopted to move the application infrastructure to Cloud.

  • Re-host: The typical lift and shift. The least expensive approach, though one cannot enjoy the complete benefit of moving to cloud except that you move from Capex to Opex, from a cost perspective
  • Modernize Your Application: Re-Factor or Re-Platform your application where you can start with simple containerization to Automation (CI / CD) to de-coupling and breaking down complex architecture and enable APIs
  • Build your application from scratch using Cloud technologies

In all the above scenarios Quality Assurance plays a critical role to ensure that the applications work fine after they are migrated to a Cloud infrastructure. In case of a complete rewrite on Cloud Native for a Microservices-Based architecture, not only is a complete traditional functional and non-functional testing required executed but contract testing and resiliency testing are also vital to ensure all services are developed as per requirement and built with resiliency. Following table illustrates the different types of testing that are required across Cloud adoption strategies:


Cloud adoption strategies

When you migrate to Cloud with or without modifying your application / with or without containerizating the underlying business logic, which does not warrant for an exhaustive functional testing but at least the end-to-end business use cases need to be validated to ensure all stacks migrated to a Cloud infrastructure work as expected and are well connected. Apart from that Hexaware recommends the following tests and diagnosis to assure quality compliance for your Cloud migration:





How are we different?

  • Continuous innovation to build solutions across ever-changing technology landscapes
  • Strategic partnerships with Software vendors 
  • Investments in IP’s and dedicated labs
  • World-class Cloud Testing Services and Engineering with 360-degree coverage

Key Customer Benefits

Benefits of Hexaware’s Cloud Quality Assurance Framework 

  • Achieve successful Cloud migration
  • Optimize costs by executing the right type of testing for respective migration strategies
  • Adopt open source solutions like PACT for contract testing and avoid redundant testing costs
  • In-house resiliency testing solution for microservices

Microservices Testing

Contract Testing:

Testing to ensure the contract is developed as per consumer requirements


Unit Testing:

  • Test small units of the code
  • Use mocks or stubs to test
  • Stateless testing
  • Test groups of unit-tested code within services

Integration Testing:

  • Testing inter-connectivity between services
  • Testing between microservices and external systems
  • Focus on Security, data flow and error scenarios

End-to-end Testing:

  • Limited testing to cover business scenarios and application functionality
  • Virtualization solutions to mitigate system dependency issues

Resiliency Testing – Simulate Destructive Behaviour

  • Validation based on simulation of realistic failure conditions for a Cloud application like:
    • Individual servers that are running part of a specific service may crash or become unavailable
    • Network segments may stop passing traffic reliably
    • Larger aggregations of resources may stop working
  • Involves voluntarily removing portions of an application’s infrastructure or application components
  • Generates sudden, random resource destruction scenarios tests for Microservices resiliency

Hexaware’s TALOS Automation Framework 

Our TALOS automation framework has an AWS out-of-the-box integration and is equipped with Chaos Orchestration through a dedicated UI which you can use to design your chaos test scenarios and map it to the respective microservice by executing the test. TALOS auto-kills the particular service and will run the respective test scenario and capture the application’s response to validate the expected resilient behaviour.

Want us to get back to you ?

  • First Name*
  • Last Name*
  • Business Email*
    • Please enter valid business email
  • Mobile Number*
  • Job Title
  • Organization
  • Others*
  • Your Message For Us
  • The information you provide will be used in accordance with our terms of Privacy Policy

  • Please enter captcha

    ( Mandatory field * )