Does it make sense to write unit/integration tests that verifies the properties or configurations?

Since any medium to highly complex applications include a lot of configurations (via yaml or properties files).

Many of these configurations derive the run time behaviour even if they are used by the underlying libraries or frameworks. Would it be a sensible idea to verify that the configurations are correctly used at runtime?

One pro-argument is since there is no compiler safety, we need to somehow verify if the configurations are dictating the behaviour correctly.

The con argument is, are we verifying the underlying frameworks implementation?

Testing just the configuration file might not be enough as it does not guarantee if the configuration will be correctly employed at runtime (there could be typos or other similar mistakes).