Evolve with Evidence II: Automated Testing in MOSIP

The UN’s DPI Safeguards Initiative has outlined 259 recommendations to help regulators, advocates, donors, technology providers, and governments ensure that their digital public infrastructure (DPI) implementations are secure, inclusive, practical, and adaptable.

This article is part of our ongoing series where we examine how MOSIP has worked to put these safeguards into practice, what we have learnt in doing so, and what more we can do to protect the integrity of DPI and foster a secure and trustworthy environment for all stakeholders. In this second piece, we continue our focus on the safeguard “Evolve with Evidence”, examining how MOSIP’s automated testing protocols support quality, resilience, and scalability throughout our development lifecycle. 

Read Part 1 here: Evolve With Evidence: Rigorous Testing and Proactive Risk Management at MOSIP

For governments rolling out national ID programmes, stability and reliability is a matter of public trust. Each release, each update, must work flawlessly in diverse environments, across devices, and for every user, from urban areas to remote rural communities. In this context, foundational platforms like MOSIP must operate with near-invisible efficiency, and that level of performance is only possible with continuous automated testing at scale. 

At MOSIP, automation plays a critical role in enabling rapid development cycles, catching issues early, and ensuring consistent quality across releases. With over 14,000+ automated test cases covering more than 54% of all test scenarios, our testing infrastructure is designed to be both comprehensive and adaptive – scaling with each enhancement and evolving with every deployment.

Why Automated Testing Matters

As digital ID becomes the gateway through which residents access core services, such as healthcare, financial inclusion, social protection, and education, it is critical that these systems remain secure, reliable, and consistent over time.  

In the diverse environments where MOSIP is deployed, automated testing plays a critical role in validating performance across geographies, devices, and connectivity conditions. As the platform evolves, with new modules, integrations, and national-scale rollouts, automated testing ensures continued alignment with global principles of reliability, privacy, and inclusivity. It enables governments to deliver trusted, resilient digital public infrastructure that scales with confidence.

At MOSIP, automation supports:
 

1. Regression Protection: Ensures that new code changes do not affect existing functionalities.
 

2. Early Bug Detection: Surfaces issues early, reducing cost and effort.
 

3. Compatibility Checks: Validates the system and handles both expected and unexpected scenarios, ensuring backward compatibility of APIs, particularly with Long-Term Support (LTS) versions.

4. Continuous Build Validation: Ensures high-quality code through continuous testing.

5. Community Contribution: By automating the entire testing process, MOSIP lowers the barrier for community contributions – enabling faster, safer collaboration.

Types of Automation Testing at MOSIP

To assure quality, reliability, backward compatibility, and faster releases, MOSIP uses the following automation testing types:

1. Application Programming Interface (API) Testing
    
2. User Interface (UI) Testing
    
3. Domain-Specific Language (DSL) Testing

1.  API Testing

MOSIP’s microservices architecture relies heavily on APIs for communication between modules, making API testing essential. These tests validate:

–  API responses, making sure the endpoints respond as expected.

–  Data integrity and Security, for secure and accurate data transmission.

– Compliance with MOSIP's system requirements.

– Version adherence and backward compatibility 

2. UI Testing

The MOSIP platform spans both web and mobile interfaces, making UI testing a fundamental requirement. But when deployed at population scale, the complexity increases significantly. The system must perform seamlessly across diverse geographies, device types, and network conditions – while also meeting the needs of a highly varied user base, spanning age groups, literacy levels, digital experience, and accessibility requirements. In such a context, even small UI flaws can become barriers to access. Automated UI testing therefore becomes critical not just to catch regressions and validate user flows, but to ensure that the platform remains intuitive, accessible, and dependable for every user in every context.

To ensure seamless experiences across MOSIP’s web and mobile platforms, automated UI tests verify:
 

– Consistency Across Platforms: Buttons, forms, and workflows are tested to behave consistently across various devices and browsers.

– Real User Simulations: Automated scripts replicate real user interactions, such as form submissions, navigation, timeouts, and readability checks to surface issues before they reach users.

– Cross-Browser Testing: Tests are run across all major browsers, including Chrome, Firefox, Safari, and Edge, to ensure broad compatibility.

– Cross-Device Testing: At population scale, and with our inclusivity principle in mind, this is a critical step. MOSIP tests on over 40 mobile device types, including iOS and Android smartphones and tablets, to ensure reliable performance across real-world conditions. 

3. End-to-End Testing using DSL

Every resident is affected by their country’s identity system, making it essential to map and validate all user journeys – whether they involve customer support teams, field agents, supervisors, or residents themselves. End-to-end (E2E) testing ensures that identity registration, verification, and authentication processes function smoothly across all of MOSIP’s modules.

MOSIP’s Domain-Specific Language (DSL) offers a unique way to build test scripts focused on user journeys, across both internal personas (operators, supervisors) and resident-facing workflows. Designed to be readable, maintainable, and closer to natural language, the DSL enables teams to simulate real-world scenarios more effectively. This approach enhances the clarity and efficiency of testing, while strengthening collaboration across development, QA, DevOps, and product teams.

Key features of E2E testing in MOSIP include:
 

– Persona-Based Testing: Scenarios are designed around a range of user personas, such as identity applicants, registrars, field agents, and administrators. This ensures that each test reflects the specific responsibilities, actions, and challenges associated with that role. Both positive flows  and negative flows are tested to simulate real-world user behaviour and system responses.

– Comprehensive Scenario Coverage: With over 175 detailed test scenarios, MOSIP’s E2E testing suite is one of the most complex and robust among digital public goods. These scenarios span the full lifecycle of identity across all major user personas. Executed daily, these tests provide critical, real-time validation of system functionality, offering confidence to implementing countries, partners, and the broader MOSIP community that the platform is reliable and ready for deployment at scale. 

Key Practices for Country-Scale Automation

• Test Coverage at Multiple Touchpoints: To support diverse populations across regions, devices, and connectivity levels, automated tests should span a wide range of browsers, platforms, and device types. Broad test coverage ensures the platform performs reliably and consistently for all users, regardless of their environment.
   
• Treat Testing as a Contract: Treat API and UI testing as separate and formal contracts – with third-party systems and end users respectively. Each layer should maintain consistent behaviour, even as internal code evolves, to avoid breaking integrations or user experiences.
   
• Modularity: A modular testing approach allows teams to validate one or a group of components at a time. This enables easier testing, faster isolation of issues, and better community contribution.
   
• CI/CD Integration: Testing should evolve with the codebase. Integrating automated tests into CI/CD pipelines ensures quick feedback, early bug detection, and stable builds throughout development.
   

• Fail Fast, Detect Early: An important principle followed within the MOSIP community is to fail fast. The goal is to predict and catch errors early, before taking users through an entire journey only to encounter a failure down the line. By adopting a fail-fast strategy, teams can design rapid, repeatable tests that validate each step of a user flow. 

  This allows issues to be identified and resolved early, avoiding the need for costly and complex fixes later in the deployment cycle. Early failure detection not only improves efficiency but also supports the delivery of high-quality, reliable systems at scale.

• Mock Data/Systems: Mock systems help simulate consistent and varied user scenarios enabling thorough validation. The mock data within the testing framework allows us to simulate real-world scenarios without relying on complex real-world data. This improves accuracy and speeds up failure detection.

• Sandbox Environments: Testing in sandbox environments ensures that automation scripts evolve safely, without impacting production. It acts as a buffer layer to validate code before live deployment.

• Virtual Countries & Multilingual Testing: To better reflect real-world usage, simulate real-world conditions using virtual countries with region-specific data formats and workflows. Coupling this with multilingual testing helps ensure that localisation is well-supported and that the platform performs reliably across different languages and user contexts.

By embedding automated testing at every layer of the development lifecycle, MOSIP ensures that the platform remains resilient, reliable, and ready for deployment at national scale. These practices help accelerate release timelines. Over time, they also build trust within the global community of adopters, developers, and partners. Without such a rigorous and structured approach to testing, it would be nearly impossible to deliver the quality and consistency required for digital public infrastructure to succeed in diverse, real-world environments.

As we continue to evolve, our goal is to expand automated test coverage to 75%, deepening assurance while supporting rapid, responsible innovation.