Testing OppiaMobile

OppiaMobile incorporates several types of tests to make the app and server stronger and make sure updated code does not break existing functionality.

For the core components of OppiaMobile, we use the SonarCloud code analysis tool to help us measure and improve the maintainability of the code and the automated test coverage. The current Sonarcloud analysis reports can be found at:

• Oppia Server: https://sonarcloud.io/project/overview?id=DigitalCampus_django-oppia

• Oppia App: https://sonarcloud.io/project/overview?id=DigitalCampus_oppia-mobile-android

• Moodle to Oppia Export Block: https://sonarcloud.io/dashboard?id=DigitalCampus_moodle-block_oppia_mobile_export

The processes for running the existing tests, and also how to add new tests, is described below:

• Running Tests for OppiaMobile App
  • Initial Set Up
  • Running All Tests
  • Running Specific Tests
• Creating new tests for OppiaMobile App
  • Local Unit Tests
  • Instrumented Unit Tests
  • User Interface Tests
  • Mock Web Server
  • Temporary Files and Folders
  • Considerations to create consistent tests
• Testing in-app Notifications
  • For course updates and new courses
  • Reminders for users to complete courses
• Testing OppiaMobile Server
  • Run the tests on your Oppia server
  • Creating new tests
• Testing Oppia Moodle Export Block
  • PHPUnit
  • Behat
  • GitHub Workflow

If you have problems or failures when running or creating tests, then please contact us via the OppiaMobile Community