Development & E2E Testing

Build the service on the SP side, integrate with the GUP layer (Event Processing), and validate the full flow — status events, redirection, UI, and edge cases — across non-production environments.

Gate to advance

All implementation items complete and every end-to-end testing checklist passed with no blocking issues.

Output produced

Implemented service, validated end-to-end in non-production and ready for User Acceptance Testing.

Full checklist

Development & E2E Testing (21)
Development & E2E Testing
Task Owner
Develop content following the GUP Content Standards

Accountable: SP

Responsible: SP

Review content

Accountable: MTCIT (Gov.om)

Responsible: MTCIT (Gov.om)

Fix content-related issue, if any

Accountable: SP

Responsible: SP

Integrate with PKI and implement SSO

Accountable: SP

Responsible: SP

Share non-production Kafka credentials

Accountable: MTCIT (Gov.om)

Responsible: MTCIT (Gov.om)

Develop backend Kafka integration on the SP side

Accountable: SP

Responsible: SP

Implement navigational changes on the SP side if required

Accountable: SP

Responsible: SP

Implement service frontend following the GUP Design System and GUP UI/UX guidelines

Accountable: SP

Responsible: SP

Provide JavaScripts tags for Google Analytics configuration

Accountable: MTCIT (Gov.om)

Responsible: MTCIT (Gov.om)

Configure Google Analytics tags on SP side

Accountable: SP

Responsible: SP

Ensure compliance with responsiveness and accessibility standards

Accountable: SP

Responsible: SP

Conduct UI/UX review

Accountable: MTCIT (Gov.om)

Responsible: MTCIT (Gov.om) & SP

Fix UI/UX-related issues, if any

Accountable: SP

Responsible: SP

Make necessary configuration in the GUP test environment to enable end-to-end testing from SP side

Accountable: MTCIT (Gov.om)

Responsible: MTCIT (Gov.om)

Provide GUP test environment login credentials and URLs

Accountable: MTCIT (Gov.om)

Responsible: MTCIT (Gov.om)

Conduct end-to-end testing from the GUP Test environment

Accountable: SP

Responsible: SP

Share Application Numbers upon completion of the end-to-end testing

Accountable: SP

Responsible: SP

Verify results of the end-to-end testing

Accountable: MTCIT (Gov.om)

Responsible: MTCIT (Gov.om)

Fix bugs identified on GUP side during the end-to-end testing, if any

Accountable: MTCIT (Gov.om)

Responsible: MTCIT (Gov.om)

Fix bugs identified on SP side during the end-to-end testing, if any

Accountable: SP

Responsible: SP

Approve closure of the development & end-to-end testing phase

Accountable: MTCIT (Gov.om)

Responsible: MTCIT (Gov.om)