-
Task
-
Resolution: Done
-
Minor
-
None
-
4.1
-
MOODLE_401_STABLE
-
6
-
Team Hedgehog 4.1 sprint 0.3, Team Hedgehog Sprint 2.2
A mock MoodleNet endpoint should be created to represent API calls being made between LMS and MoodleNet, primarily to facilitate easy automated testing runs (such as CI testing), as well as more complex development testing (compared with the basics available from MDL-77294).
The basic setup of this can possibly be copied from the existing BigBlueButton or Matrix equivalent, and then have the API built out onto that.
Requirements
- A mock API endpoint for the MoodleNet API side of “share to MoodleNet”, which accepts valid requests for OAuth metadata, registration and MoodleNet API calls, and provides accurate responses.
- Handling for unexpected/invalid requests, as necessary to perform LMS testing.
- May need data storage for tests (will eventually, but potentially not required for phase 1).
- If it will be running on CI, it must handle multiple clients - i.e. behat parallel runs on different base URLs storing data separately and clearing it separately.
- Needs to run either as a docker image, or locally.
An important consideration is that Moodle's OAuth provider implementation requires https or it will be rejected, so this will likely need to handle that (which is not currently supported in the BBB mock setup).