… enabled

The preference will be set from the admin interface in a new commit

It would be nice if we had an array/list type for preferences. Probably not too hard to implement, but this will do.

It wasn't really necessary, but I'm going to need this list in a moment, so we might as well use it.
Also it allows us to ensure the options are listed in a certain order.

Also maybe it will help protect against corrupt preferences.

I considered adding a request spec, but figured it still doesnt' test the form, so better to use a full system spec.

Could have easily done this manually, but this makes the transition smoother.

BTW I tested each case manually, didn't seem worth writing a spec.

If a checkbox is not selected, the browser does not submit it at all.

I'm not sure, but I assume that Config.set will raise an exception if it failed.