33 lines
1.2 KiB
Gherkin
33 lines
1.2 KiB
Gherkin
Feature: Verbose Logging Levels
|
|
As a developer
|
|
I want granular control over logging verbosity
|
|
So that I can see appropriate levels of detail based on my needs
|
|
|
|
Background:
|
|
Given the verbose logging test environment is initialized
|
|
|
|
Scenario Outline: Verbose count maps to correct logging level
|
|
Given I create an application with verbose level <verbose_count>
|
|
When I check the logging configuration
|
|
Then the root logger level should be <expected_level>
|
|
And all handlers should have level <expected_level>
|
|
|
|
Examples:
|
|
| verbose_count | expected_level |
|
|
| 0 | CRITICAL |
|
|
| 1 | ERROR |
|
|
| 2 | WARNING |
|
|
| 3 | INFO |
|
|
| 4 | DEBUG |
|
|
| 5 | DEBUG |
|
|
|
|
Scenario: Application stores verbose parameter correctly
|
|
Given I create an application with verbose level 2
|
|
When I check the application configuration
|
|
Then the verbose attribute should be 2
|
|
|
|
Scenario: Handler logging levels are configured correctly
|
|
Given I create an application with verbose level 2
|
|
When I check the handler configuration
|
|
Then all handlers should have WARNING level
|