-
Notifications
You must be signed in to change notification settings - Fork 9
StorEvil Configuration
StorEvil is configured in the (creatively named) storevil.config file.
When StorEvil is run, it will look for a storevil.config file in the present working directory. If it is not found there, it will look in the parent directory, and continue until it reaches the volume root (C:\ for example). It will only process the first storevil.config file that is found.
If no storevil.config is found, StorEvil will look for a .csproj
So, if executed from C:\foo\bar\baz, it will first look for C:\foo\bar\baz\storevil.config.
If that is not found, it will check C:\foo\bar\storevil.config, followed by C:\foo\storevil.config, then C:\storevil.config.
It works this way so that (assuming you have storevil in your PATH), you can navigate into any sub-directory and execute the stories within it.
This specifies the paths to the DLLs containing the Context classes used to interpret the language in the stories.
The paths are separated by commas and are relative to the directory containing the config file.
Assemblies: ..\Pizza.TestContext\bin\Debug\Pizza.TestContext.dll
This specifies the file extensions of the files that have the natural language specifications, that StorEvil should execute:
These are comma separated and should each begin with a period.
Extensions: .feature, .txt