In short
Moving applications to the cloud only improves customer and employee experiences if the move is tested at every step. Zarka Sultana, Principal Consultant at Sogeti UK (part of Capgemini), shows how the right testing approach depends on the migration path, why an incremental, agile migration is safer than a big bang, and which data, security and performance tests protect users along the way.
Key takeaways
- Moving to the cloud: understanding the technology versus the testing approach.
- Choosing the right testing approaches during migration to the cloud can result in happier user experiences.
- The agility of cloud migration improves application quality.
Why legacy systems push companies to the cloud
Sultana opens by defining cloud migration as moving information, storage, databases and applications from enterprise legacy systems to modern cloud infrastructure, whether private, public, hybrid or multi-cloud. Whatever the deployment model, she insists that testing is not optional.
"Regardless of the development services or deployment services used, some essential testing must be performed when migrating to the cloud to avoid risk of failure on deployment and user acceptability." (1:22)
The reasons to move are familiar: aging in-house systems that cannot compete with newer technology, high maintenance costs for outdated hardware and software, security and compliance challenges, and poor performance. She illustrates the last point with a story from her own consulting work.
"I remember once I went to a client's site to do an independent piece of quality assurance for their product and the system took between 30 to 40 minutes to load every morning." (2:44)
Staff, she recalls, would switch on their computers and head off for a coffee break while they waited.
Matching tests to the migration path
Sultana explains that businesses reassess their requirements and dependencies before choosing a migration service, and testing is configured the same way: around requirements, system functionality, business processes, integrated systems and the chosen cloud solution.
For a lift and shift, where an application and its data are rehosted on cloud virtual machines without changing code or architecture (typically infrastructure as a service), testing covers data migration validation so nothing is lost between source and target, regression and end-to-end checks, security testing of user access and server vulnerabilities, and performance testing for load and runtime. Developers and testers do most of this work before business users run user acceptance testing against real-world scenarios.
Refactoring, which redesigns an application to use cloud-native features (often on platform as a service), and replacing with software as a service call for more. When code is rebuilt and database models change, she says, system testing must confirm each new component works, and system integration testing must prove that the many dependent applications still work together according to business requirements.
Moving in small, tested batches
The core argument of the talk is that agility in both migration and testing raises quality.
"So rather than a big bang migration, it is lower risk to adopt iterative and agile approach, that is to manage data migration to cloud incrementally in small batches." (10:56)
That requires heavy planning: categorising data, applications and integrated systems, then dividing the work into sprints based on workloads and dependencies. Standalone applications and databases can move first, with test execution running in parallel using a fail-first approach to gather feedback early. The same logic applies to code.
"Similarly, during refactoring and rebuilding app, adopting agile approach for coding testing will prevent expensive time-consuming fixes later." (11:31)
After migration, she recommends continuing with iterative Scrum cycles as applications are modernised.
Protecting data and security
Sultana warns that poor data quality (inaccurate, inconsistent, duplicate or lost data) leads to high operational costs, integration risk and interrupted business operations. Her remedy is a pre-migration rehearsal: risk analysis, source data assessment, recording the amount of data to verify afterwards, checking schemas such as field names, types, lengths and mandatory fields, and cleansing data. Her simple flow runs from extracting data and validating row counts through cleansing and transformation to loading into the target environment.
On security, she stresses shared ownership.
"So cybersecurity is a shared responsibility between business and cloud provider to manage both risk and compliance." (14:29)
In practice this means encrypting data during migration, keeping daily backups for disaster recovery and running regression tests after any restore, testing two-factor authentication and account lockout after repeated failed passwords, and continuously scanning servers, endpoints, networks, applications and databases. She adds that employees need training on the new cloud processes and interface before migration.
Performance, and the case for testing in the cloud
To keep the experience fast, Sultana lists load testing across low, normal and high traffic, stress testing to find the breaking point, latency checks, and fault tolerance testing so workloads stay available across geographical locations during disruption.
She closes by contrasting traditional testing, with its large capital spending on hardware and software, with running tests in the cloud.
"Using the cloud to run tests can provide a compelling combination of lower cost, pay per use, and no upfront capital expenditures." (18:31)
Her final point ties it together: testing improves software quality and performance, and users notice when they can browse faster without interruption.
Watch the talk
How Testing in Cloud Shifting improves the customer and employee experiences? by Zarka Sultana (20 minutes): https://www.womentech.net/video/how-testing-in-cloud-shifting-improves-customer-and-employee-experiences-zarka-sultana-0
About the speaker
Zarka Sultana is Principal Consultant (Software Quality Engineer) at Sogeti UK (part of Capgemini), a Digital Assurance and Quality Engineering organization, where she provides expert testing solutions for clients in telecom, energy, non-profit and government. She leads test management and quality engineering across the software delivery life cycle, bringing business, developers, testers and third-party stakeholders together to deliver continuous quality.
Questions this talk answers
- What testing does a lift and shift cloud migration need?
- Why migrate to the cloud incrementally instead of all at once?
- How should data migration be tested?
- Which security tests matter when moving to the cloud?
- Why run testing itself in the cloud?
Drafted with AI from the talk transcript. Editor review pending.