HAL9000
68fd040e31
Minor improvements to feature descriptions and docstrings for clarity. No behavioral changes - all scenarios produce the same assertions.
43 lines
1.9 KiB
Gherkin
43 lines
1.9 KiB
Gherkin
@tdd_issue @tdd_issue_7874
|
|
Feature: Alembic fileConfig error handling (issue #7874)
|
|
|
|
As an operator running Alembic migrations, I want to receive a clear,
|
|
actionable error message when alembic.ini contains malformed logging
|
|
configuration, so that I can diagnose and fix the issue without being
|
|
confronted by an unhandled traceback.
|
|
|
|
Background:
|
|
Given a fresh temporary directory
|
|
|
|
Scenario Outline: fileConfig failure exits with non-zero exit code
|
|
When the alembic.ini contains an invalid logger section that references nonexistent loggers
|
|
And migrations are invoked normally
|
|
Then the error output on stderr includes actionable guidance about "[loggers]" section
|
|
|
|
Examples: malformed configurations
|
|
| description |
|
|
| references undefined logger key |
|
|
|
|
Scenario Outline: fileConfig failure message includes the config file path
|
|
When the alembic.ini contains a malformed logging configuration
|
|
And migrations are invoked normally
|
|
Then the error output on stderr includes the config file path "alembic.ini"
|
|
|
|
Examples: malformed configurations
|
|
| description |
|
|
| references undefined logger key |
|
|
|
|
Scenario Outline: fileConfig failure message is user-actionable
|
|
When the alembic.ini contains a malformed logging configuration
|
|
And migrations are invoked normally
|
|
Then the error output on stderr includes actionable guidance about "[loggers]" section
|
|
|
|
Examples: malformed configurations
|
|
| description |
|
|
| references undefined logger key |
|
|
|
|
Scenario: fileConfig succeeds silently when INI file is valid
|
|
When the alembic.ini contains a valid logger configuration
|
|
And migrations are invoked normally
|
|
Then no error message appears on stderr
|