Add test cases about editorconfig HOT 13 CLOSED

On Sunday, November 27, 2011, Trey Hunner <
[email protected]>
wrote:

I think we should add test cases for the EditorConfig core to ensure that
future changes maintain backwards compatibility and do not any break
current functionality.

It looks like cmake is bundled with a test suite called ctest. Maybe we
should use that.

I agree. I am now try to do this.

Hong

from editorconfig.

The general test mechanism has been implemented: aa726008d0f024cd7c89c43eec377fda22cb9df9

Now what we need to do is to add testing cases.

from editorconfig.

Maybe we should group our test cases into files of like tests. For example the current three test cases for question mark, asterisk, and square brackets could be grouped into one file called test_globs.in.

Here are some starter test file groups I propose:

• test_globs.in: used for testing globbing functionality
• test_properties.in: used for property-specific tests (such as lowercasing eol or setting default values)
• test_ini.in: used for testing INI parsing edge cases and section parsing order
• test_args.in: used for testing command line arguments (e.g. --version)

from editorconfig.

Would test_properties be very long in the future?

from editorconfig.

It may be. We could make a subdirectory called property_tests and add property-specific tests in individual files.

from editorconfig.

Maybe we could use 4 subdirectories for the four categories respectively.

from editorconfig.

That works for me.

from editorconfig.

I think we should remove the test_ prefix from the test directories and files because they are redundant. What do you think?

from editorconfig.

I agree.

from editorconfig.

test_ prefix removed. ee83a1241450b9002d683b2718232a083b46be14

from editorconfig.

According to your recent commit, it seems that you have forgotten that test_ should be removed.
Just a remind here.

from editorconfig.

Ah yes I had started making that file before we changed the naming scheme. Thanks for fixing.

from editorconfig.

The test coverage now seems reasonable to me. I'm closing this.

If we discover gaps in test case coverage in the future new issues should be made to handle them.

from editorconfig.