Configuration file

Concordia Compiler can use a configuration file in JSON format named .concordiarc. You can generate it by running the following command:

npx concordia --init

You'll be asked about the desired configuration and then the file will be saved.

Example:

{
    "language": "pt",
    "directory": "docs/features",
    "plugin": "codeceptjs-testcafe",
    "dirScript": "test/e2e",
    "dirResult": "test/e2e/output"
}

Configuration file's properties are similar to CLI parameters. The example above defines: "pt" (meaning "Portuguese") as the default language; the directory "docs/features" for features and test cases; the plug-in "codeceptjs-testcafe" for generating test scripts; the directory "test/e2e" for test scripts; and the directory "test/e2e/output" for output files such as report files and screenshots.

CLI options take precedence over values from the configuration file

directory

Directory to search for .feature and .testcase files.

Example:

{
  "directory": "./features"
}

recursive

Use recursive directory search.

Example:

{
  "recursive": false
}

files

Files to consider, instead of considering directory. The files must be separated by colon.

Example:

{
  "files": "/path/to/file1.feature,/other/file2.feature"
}

Another example:

{
  "files": [
    "/path/to/file1.feature",
    "/other/file2.feature"
  ]
}

We recommend you to configure the property directory whether your project can have new files.

ignore

Files to ignore, considering the parameter directory. The files must be separated by colon. Example:

{
  "ignore": [
    "/path/to/file1.feature",
    "/other/file2.feature"
  ]
}

extensions

To-Do

encoding

File encoding of the files. Accepted values are:

  • utf8 or utf-8

  • latin1

  • ascii

  • ucs2 or ucs-2

  • utf16le or utf-16le

Naturally, the files must be edited with the given file encoding.

To-Do

To-Do

To-Do

To-Do

To-Do

Last updated