Spinoff of #12274 and a dependency thereof: new test_configurations.py should statically test that configparser, called from idlelib.configHandler, can process all the configuration.def files without error.

The format paragraph entry in main.def is being moved to extensions.def, so don't test for it in main.def.

Attaching a patch to test the default configuration files. config-keys.def will be added once the issues related to it[1] are resolved.
In this patch, test that the configHandler module can successfully extract the values. For places where numeric values are expected, ensure that the values are correct. For strings, it only ensures that the values are reasonably correct.



----

[1] https://mail.python.org/pipermail/idle-dev/2014-June/003431.html

I've done a thorough review of the tests. The overall structure and tests are fine, but I found quite a few issues that should be addressed.

Saimadhav, considering these are some of the first tests you've written, please know that I am impressed! I have many comments because I believe our tests should be excellent and I'm a bit pedantic. However I've seen many people write poorer test suites after despite having considerable experience. So keep up the good work, learn from our feedback and everything will be great!

I closed #12274, but it might be consulted before closing this.

The issue is obsolete with respect to the minimal test implied by the opening message.  At least two tests (added since this was written) read the .def files.

Some of the proposed tests are, now at least, redundant  For boolean tests like
    self.assertIn(get('editor-on-startup', 'bool'), (True, False))
a non-boolean value results in a Warning (treated like error), the assert, and remaining tests are skipped, and IDLD hangs.  Stripping strings should not be needed.

Some of the tests should be part of a startup check of default *and* user options.  Values should also be checked when changed (they mostly are).

Since new options have been added, some tests are missing.

I would like to have a 3-layer option map that can be used for both runtime change and the test suite.