Objective :

• Describes the implementation details of testing the BCA Life (Android Apps) phase 2 feature to ensure that all aspects of functionality are working as expected criteria and expected condition

Test Case :

Test Scenario BCA Life 2.0_Android Internal.xlsx

Scope Testing :

• Phase 2 feature
  • CMS
  • Tracking Billing Summary
  • Tracking Claim
  • Form Claim Update
  • Klaim Rawat Inap - Kecelakaan
  • Notification
  • Klaim Rawat Jalan - Kecelakaan
  • Klaim Rawat Inap - Penyakit
  • Klaim Rawat Jalan - Penyakit
  • Cacat Tetap - Kecelakaan
  • Cacat Tetap - Penyakit
  • Penyakit Kritis - Kanker
  • Penyakit Kritis - Penyakit Jantung
  • Penyakit Kritis - Penyakit Ginjal
  • Penyakit Kritis - Penyakit Paru Paru
  • Penyakit Kritis - Penyakit Pembuluh Darah Otak
  • Meninggal Dunia - Kecelakaan
  • Meninggal Dunia - Penyakit
  • Terminal Illness - Kecelakaan
  • Terminal Illness - Penyakit

Not to be Tested :

Testing Environment :

• Hardware :
  • Nokia 5.1 Plus - Android 10
• Environment :
  • Staging
  • UAT
  • Pre-Production
• Testing Tools :
  • Jira
  • Lightshot
  • DBeaver
  • Chucker

Testing Schedule :

• 1 Month

Testing Member :

• 3 Person

Exit Criteria :

• Functional Success
  • All functional test cases must pass without critical bugs.
  • User is able to submit claims for all product types.
  • Integration with 3rd-party vendors (e.g., Workflow) must be successful.
  • User’s policy must be successfully synchronized with the system to ensure accurate claim processing and benefits.
• Usability Success
  • Users should be able to access the app across different smartphone models and OS versions smoothly, without encountering any critical issues.
  • The app should provide an intuitive and user-friendly interface, allowing users to navigate seamlessly.
  • All app functionalities must be easily accessible and should not cause confusion or frustration.
  • Performance must meet expectations, with fast load times and no crashes or freezes.
  • The app should be responsive and adaptable to different screen sizes and orientations.
• UAT
  • Users have tested the app in their environment.
  • Users confirm that the system meets their expectations and criteria.

Documentation and Reporting :