Expected Behavior
The sample.conf defines a key for defining a test name. For example: description: "plugin should create the task named x". Upon test execution, the test name uses the description instead of auto-generated description.
Current Behavior
The test name is derived of the directory hierarchy and the prefix of the sample.conf file. The test name is hard to read and doesn't really express its intent.
Context
Auto-discovering tests with one of the Runner implementations produces cryptic test names.
Expected Behavior
The
sample.confdefines a key for defining a test name. For example:description: "plugin should create the task named x". Upon test execution, the test name uses the description instead of auto-generated description.Current Behavior
The test name is derived of the directory hierarchy and the prefix of the
sample.conffile. The test name is hard to read and doesn't really express its intent.Context
Auto-discovering tests with one of the
Runnerimplementations produces cryptic test names.