| 1 |
@issue |
| 2 |
Feature: Issue #177: Cannot setup logging_format |
| 3 |
|
| 4 |
. DESCPRIPTION: |
| 5 |
. When the logging_format is set in the behave configuration file |
| 6 |
. or on command-line, an exception is thrown, because |
| 7 |
. the ConfigParser tries to replace the placeholders in the format string |
| 8 |
. with option values in the configuration file (which do not exist). |
| 9 |
. |
| 10 |
. SOLUTION: |
| 11 |
. The format string must be processed as raw value (by the ConfigParser). |
| 12 |
. |
| 13 |
. RELATED: |
| 14 |
. * features/logging.setup_format.feature |
| 15 |
. * features/logging.setup_level.feature |
| 16 |
|
| 17 |
|
| 18 |
@reuse.colocated_test |
| 19 |
Scenario: Setup logging_format |
| 20 |
Given I use the current directory as working directory |
| 21 |
When I run "behave -f plain features/logging.setup_format.feature" |
| 22 |
Then it should pass |
| 23 |
And the command output should not contain: |
| 24 |
""" |
| 25 |
Traceback (most recent call last): |
| 26 |
""" |
| 27 |
And the command output should not contain: |
| 28 |
""" |
| 29 |
ConfigParser.InterpolationMissingOptionError: Bad value |
| 30 |
""" |
| 31 |
|
| 32 |
@reuse.colocated_test |
| 33 |
Scenario: Setup logging_level |
| 34 |
|
| 35 |
Ensure that the problem that was also mentioned, works as expected. |
| 36 |
Note that this "problem" never existed (hint: missing user knowledge). |
| 37 |
|
| 38 |
Given I use the current directory as working directory |
| 39 |
When I run "behave -f plain features/logging.setup_level.feature" |
| 40 |
Then it should pass |