In order to run tests that carry out automated functionality testing for the Moodle App, you can write Acceptance tests. This can be useful if you want to test plugins that are compatible with the app, or you're contributing to the app core. Behat tests for the app work the same way as tests for Moodle core, but they are not run as part of a normal Behat execution and there are some differences that we'll go through in this page.
Screen readers
Tests can be useful during development, but a good test suite really shines with CI processes in place. Running tests and other checks on a regular basis can be helpful to maintain good quality assurance, and catch regressions as early as possible.
You can implement custom course formats using the CoreCourseFormatDelegate:
You can implement custom course modules using the CoreCourseModuleDelegate.
Unfortunately, the core team does not have the resources to help people use the open source code to build custom apps.
Introduction
In this example, we are going to see how to display a form and send the data to a Web Service when it's submitted.
If you have an activity that uses groups, you may want to implement a group selector to filter the rendered content. There are many ways to achieve this, and we're going to outline some of them in this example.
You can create a link handler to intercept what happens when links are clicked using the CoreContentLinksDelegate.
Pressing a link inside the app
Welcome to the Moodle App developer documentation!
Release date: 25th June 2018
Release date: 6th July 2018
Release date: 10th September 2018
Release date: 11th January 2019
Release date: 29th March 2019
Release date: 7th June 2019
Release date: 30th August 2019
Release date: 20th September 2019
Release date: 20th December 2019
Release date: 25 March 2020
Release date: 2 April 2020
Release date: 26 June 2020
Release date: 3 July 2020
Release date: 16 July 2020
Release date: 30 November 2020
Release date: 28 December 2020
Release date: 27 August 2021
Release date: 22 April 2022
Release date: 26 May 2022
Release date: 25 October 2022
Release date: 19 December 2022
Release date: 28 February 2023
Release date: 9 June 2023
Release date: 10 November 2023
Release date: 28 June 2024
Release date: 9 July 2024
In the following guide, you will learn how to upgrade your plugins' acceptance tests to support newer versions of the app.
The Moodle App Coding Style guidelines
The Moodle App can be customised in different ways:
Overview
This document contains information that developers should know before starting to code on the Mobile App. If you are only interested in developing a site plugin, you should read the Moodle App Plugins development guide instead.
The development of new features and improvements in the Moodle App is organised in the following six phases:
Moodle HQ provides a couple of Docker images that contain the Moodle App ready for use. You can search all the available versions in Docker Hub.
How can I contribute to the Moodle App?
Push notifications will open the app when clicked, and you can customize which page is open by default.
The Moodle App is a mobile application that helps users make the best of their Moodle sites on handheld devices. It has some additional features like offline access, and a dedicated interface adapted to mobile. It's focused on student functionality, so you won't find all the features you have on the web for teachers and admins. You can learn more about the features available in the user documentation.
Content responses
If you want add mobile support to your plugins, you only need to write PHP code. You can also use JavaScript for advanced functionality, but mobile plugins are written the same way as any other Moodle plugin: using PHP and Mustache templates.
In the following guide, you will learn how to upgrade your plugins to support newer versions of the app.
Moodle App 4.x
Six weeks before (Code freeze)
How do Remote themes work?
In the following guide, you will learn how to migrate your styles from an older version of the app.
Version 1 was jQuery based with usage of Cordova.
Release date: 31th July 2015
Release date: 28th August 2015
Release date: 10th September 2015
Release date: 8th October 2015
Release date: 21th October 2015
Release date: 6th November 2015
Release date: 27th November 2015
Release date: 29th December 2015
Release date: 22th January 2016
Release date: 29th February 2016
Release date: 15th April 2016
Release date: 23th May 2016
Release date: 14th June 2016
Release date: 26th July 2016
Release date: 19th October 2016
Release date: 12th December 2016
Release date: 28th February 2017
Release date: 26th May
Release date: 28th July
Release date: 29th September
Release date: 30th November 2017
Release date: 28th February 2018
Release date: 19th March 2018
CoreCourseModuleDelegate handlers allow you to define a list of offline functions to prefetch a module. However, you might want to create your own prefetch handler to determine what needs to be downloaded. For example, you might need to chain Web Service calls (passing the result of a Web Service request to another), and this cannot be done using offline functions.
You can implement custom question types using the CoreQuestionDelegate:
Using CoreEnrolDelegate handlers you can support enrolment plugins in the app. In this example, we can see how to support a self enrol plugin. You'll need to register a handler in db/mobile.php and return the following JavaScript from the method implementation:
There are two ways to send custom Push Notifications to the Moodle app users:
The structure of this page is the following:
Information related to mobile app testing of LMS issues
Plugin changes are not picked up in the app
This page contains a list of common errors that have been found and how to solve them. However, keep in mind that these may be platform-dependent and could not fix the problem in your machine, even if you are seeing the same error message.
Unit tests are written in JavaScript using Jest. If you want to create a new one, Jest is already configured and you only need to create a file ending with .test.ts within the project. If you're going to do so, remember to follow the file location conventions.
Browsers are not officially supported by the application in production, but you can use a Chromium-based browser for development if you don't need any native functionality.