flake8/tests/fixtures/config_files
Ian Cordasco 3f434f7d1c
Add broken config file to test error handling
ConfigFileFinder should absolutely handle broken/invalid config files
by refusing to try to parse them. Here we catch the ParsingError,
log the exception, and then return normally. The RawConfigParser
instance is perfectly valid still and will behave as if nothing had
been read and we just need to indicate that we didn't find any files
worthy of reading.

Related to: https://github.com/PyCQA/pycodestyle/issues/506
2016-06-16 16:19:09 -05:00
..
broken.ini Add broken config file to test error handling 2016-06-16 16:19:09 -05:00
cli-specified-with-inline-comments.ini Add example configuration sections to the docs 2016-05-28 12:00:47 -05:00
cli-specified-without-inline-comments.ini Add example configuration sections to the docs 2016-05-28 12:00:47 -05:00
cli-specified.ini Add config file fixtures 2016-01-09 23:02:20 -06:00
local-config.ini Add forgotten config file fixtures 2016-01-17 13:08:52 -06:00
no-flake8-section.ini Add fixture file without a flake8 section 2016-01-10 21:05:51 -06:00
README.rst Update fixture README with descriptions 2016-01-19 06:43:47 -06:00
user-config.ini Add forgotten config file fixtures 2016-01-17 13:08:52 -06:00

About this directory
====================

The files in this directory are test fixtures for unit and integration tests.  
Their purpose is described below. Please note the list of file names that can 
not be created as they are already used by tests.

New fixtures are preferred over updating existing features unless existing 
tests will fail.

Files that should not be created
--------------------------------

- ``tests/fixtures/config_files/missing.ini``

Purposes of existing fixtures
-----------------------------

``tests/fixtures/config_files/cli-specified.ini``

    This should only be used when providing config file(s) specified by the
    user on the command-line.

``tests/fixtures/config_files/local-config.ini``

    This should be used when providing config files that would have been found
    by looking for config files in the current working project directory.


``tests/fixtures/config_files/no-flake8-section.ini``

    This should be used when parsing an ini file without a ``[flake8]``
    section.

``tests/fixtures/config_files/user-config.ini``

    This is an example configuration file that would be found in the user's
    home directory (or XDG Configuration Directory).