Book Image

Moodle 3.x Developer's Guide

By : Ian Wild, Jaswant Tak
Book Image

Moodle 3.x Developer's Guide

By: Ian Wild, Jaswant Tak

Overview of this book

The new and revamped Moodle is the top choice for developers to create cutting edge e-learning apps that cater to different user’s segments and are visually appealing as well. This book explains how the Moodle 3.x platform provides a framework that allows developers to create a customized e-learning solution. It begins with an exploration of the different types of plugin.. We then continue with an investigation of creating new courses. You will create a custom plugin that pulls in resources from a third-party repository. Then you’ll learn how users can be assigned to courses and granted the necessary permissions. Furthermore, you will develop a custom user home. At the end of the book, we’ll discuss the Web Services API to fully automate Moodle 3.x in real time.
Table of Contents (19 chapters)
Title Page
Credits
About the Author
Acknowledgments
About the Reviewer
www.PacktPub.com
Customer Feedback
Dedication
Preface
6
Managing Users - Letting in the Crowds

Behat


In this book, we have been following an Agile approach to development, where a minimum viable product is developed based on user stories. For example, in Chapter 9,Moodle Analytics, we developed a reporting block which, as a minimum, provided access to a bubble chart of user activity, the basic user story upon which this functionality was developed was as follows:

Note

As a teacher, I can access a report showing the number of learner interactions with each activity.

This is the minimum that a teacher needed to assess the relative popularity of each activity included in the course for which they were responsible. That the final report was shown as a bubble chart came out of ongoing conversations with both teachers and managers.

In fact, what we are describing here is an example of behavior-driven development (BDD). What's great about Moodle Behat integration is that test cases are described as human-readable stories (much like the user story above), which can then be automatically tested...