For this test you need to use an existing site with existing users. (This is required to make it easy to check that the predictions are generated from the first time the prediction is generated instead of from the moment when the user was created)
Log in as admin
Set up a course with at least 1 student enrolled and an assigment with due date in 2 days
Go to site admin > analytics > analytics settings and untick onlycli setting
Go to site admin > analytics > analytics models
Click on "Actions > Edit" for the model "Upcoming activities due"
Tick "Enabled", select "Upcoming 3 days" as "Time-splitting method" and save changes
Click on "Actions > Get predictions" for the model "Upcoming activities due". Click on "Continue" once finished
Select a user from the menu in the "Insights" column for the "Upcoming activities due" model
The time displayed in the "Time predicted" row, in the "Prediction details" table SHOULD be just a few seconds ago.
The time displayed in the "Time range" row, in the "Prediction details" table SHOULD be the same time than in "Time predicted" and the to ... part SHOULD be the same time but with +3 days
For this test you need to use an existing site with existing users. (This is required to make it easy to check that the predictions are generated from the first time the prediction is generated instead of from the moment when the user was created)
Log in as admin
Set up a course with at least 1 student enrolled and an assigment with due date in 2 days
Go to site admin > analytics > analytics settings and untick onlycli setting
Go to site admin > analytics > analytics models
Click on "Actions > Edit" for the model "Upcoming activities due"
Tick "Enabled", select "Upcoming 3 days" as "Time-splitting method" and save changes
Click on "Actions > Get predictions" for the model "Upcoming activities due". Click on "Continue" once finished
Select a user from the menu in the "Insights" column for the "Upcoming activities due" model
The time displayed in the "Time predicted" row, in the "Prediction details" table SHOULD be just a few seconds ago.
The time displayed in the "Time range" row, in the "Prediction details" table SHOULD be the same time than in "Time predicted" and the to ... part SHOULD be the same time but with +3 days
This is a bug introduced in MDL-65348. Part of the patch was not unit tested.