Console Edisonfile

• Example
• keys

Example

The Edisonfile allows you to save, and version control, the arguments that you can supply to the console application. The file is of YAML format and should be saved at the root of your repository. The following is an example of the format:

assemblies:
  - "./path/to/test.dll"
  - "./path/to/other/test.dll"

disable_test_output: true
console_output_type: dot
fixture_threads: 2

url: 'http://some.url.com/results'
test_run_id: 'v1.2'
test_run_name: 'v1.2.0-a3b25c+rc1'
test_run_project: 'website'

To run the application, just run Edison.Console.exe at the root, with no arguments supplied. The application will locate the Edisonfile and populate the parameters accordingly.

For example, the above will be just like running:

Edison.Console.exe --a ./path/to/test.dll, ./path/to/other/test.dll --dto --cot dot --ft 2

You can also specify both parameters on the CLI as well as in a passed Edisonfile. However, the Edisonfile will overwrite whatever you pass in on the CLI.

Keys

Each key-value pair you can specify in the Edisonfile directly corresponds to one of the console's arguments. The following are the keys mapped to their console equivalent:

Key	Console Arguments	Type
assemblies	--a	string list
console_output_type	--cot	string
disable_console_output	--dco	boolean
disable_file_ouptut	--dfo	boolean
disable_test_output	--dto	boolean
exclude	--e	string list
fixtures	--f	string list
fixture_threads	--ft	integer
include	--i	string list
test_run_id	--tid	string
test_run_name	--tname	string
test_run_project	--tproj	string
test_run_env	--tenv	string
test_result_url	--turl	string
output_directory	--od	string
output_file	--of	string
output_type	--ot	string
tests	--t	string list
test_threads	--tt	integer
rerun	--rft	boolean
rerun_threshold	--rt	integer
suite	--s	string
solution	--sln	string
solution_config	--sconfig	string
slack_token	--slack	string