Service config migration test Create a fresh site based on the weekly before the LTI feature branch - 67b2c432252 git checkout 67b2c432252 mdk install Go to "Site admin > Plugins > Activities > External tools > Manage tools" Click "Configure a tool manually" Enter: Name: Example Tool URL: http://example.com Expand the "Services" section For each of the 3 service selects, choose the last option Now, via shell or whatever tool you like, open up the DB and check the lti_types_config: select * from mdl_lti_types_config where name ilike 'ltiservice\_%' order by id; You will see 3 entries for the tool you just created. Note the name+value for each row. You should see the following: ltiservice_gradesynchronization | 2 ltiservice_memberships | 1 ltiservice_toolsettings | 1 Just keep this open and note the number of rows; we'll check back in a second. Now, checkout the patch Upgrade the site (ignore any capability-derived warnings you see during upgrade - this is normal for deprecated caps. If you're using Whoops in dev mode, you may just need to reload during the site upgrade if you're on web) Verify the upgrade completes without any problems. In your DB shell/tool the SQL again: select * from mdl_lti_types_config where name ilike 'ltiservice\_%' order by id; Verify you have no results now. In your DB shell/tool, run the following SQL: select * from mdl_lti_types_config where name ilike 'ltixservice\_%' order by id; Verify you now see all the rows again, this time with name prefix 'ltixservice_'. Verify all values are as you originally noted earlier Back in the site, go to "Site admin > General > LTI > Manage tools" Edit the tool "Example" Expand the "Service" section Verify that each select is still set to the last option available For each of the 3 service selects, choose the first option Save the form Edit the tool "Example" again Expand the "Service" section Verify that each select is still set to the first option available