editorconfig-core/tests
rtlhq f783fc51e5 Import Upstream version 0.12.5 2022-11-16 20:09:17 +08:00
..
cli Import Upstream version 0.12.5 2022-11-16 20:09:17 +08:00
cmake Import Upstream version 0.12.5 2022-11-16 20:09:17 +08:00
filetree Import Upstream version 0.12.5 2022-11-16 20:09:17 +08:00
glob Import Upstream version 0.12.5 2022-11-16 20:09:17 +08:00
meta Import Upstream version 0.12.5 2022-11-16 20:09:17 +08:00
parser Import Upstream version 0.12.5 2022-11-16 20:09:17 +08:00
properties Import Upstream version 0.12.5 2022-11-16 20:09:17 +08:00
.editorconfig Import Upstream version 0.12.5 2022-11-16 20:09:17 +08:00
.gitignore Import Upstream version 0.12.5 2022-11-16 20:09:17 +08:00
CMakeLists.txt Import Upstream version 0.12.5 2022-11-16 20:09:17 +08:00
LICENSE.txt Import Upstream version 0.12.5 2022-11-16 20:09:17 +08:00
README.md Import Upstream version 0.12.5 2022-11-16 20:09:17 +08:00

README.md

This project is a series of testing for EditorConfig Core. Please have cmake installed before using this project.

Use editorconfig-core-test independently

After installing cmake, switch to the root dir of this project, and execute:

cmake -DEDITORCONFIG_CMD=the_editorconfig_core_cmd_you_want_to_test .

After that, if testing files are generated successfully, execute ctest . to start testings.

Use editorconfig-core-test in your project as a git submodule

If you are using git and cmake to manage your project, this method should be suitable for you.

Suppose that you will add editorconfig-core-test repo as a submodule in your root directory. First add editorconfig-core-test as a gitsubmodule in your repo by execute:

git submodule add git://github.com/editorconfig/editorconfig-core-test.git tests

Then add the following lines to your project root CMakeLists.txt:

enable_testing()
set(EDITORCONFIG_CMD the_editorconfig_core_path)
add_subdirectory(tests)

Now after executing cmake . in you project root dir, you should be able to run the testings by executing ctest ..