Skip to content

Chore: [AEA-0000] - fix behave's override to logging#604

Open
tstephen-nhs wants to merge 1 commit intomainfrom
aea-0000-fix-behave-logging
Open

Chore: [AEA-0000] - fix behave's override to logging#604
tstephen-nhs wants to merge 1 commit intomainfrom
aea-0000-fix-behave-logging

Conversation

@tstephen-nhs
Copy link
Contributor

Summary

  • 🤖 Operational or Infrastructure Change

Details

Behave before 1.3.0 captures python standard library logging even when --no-logcapture is specified as it is in our runner.py. This means we cannot use logging statements in steps as currently configured. And consequently this means we have a number of print statements used for logging instead. Note that these print statements too are swallowed as currently configured but can be made to show up if --no-capture is passed to behave (either through direct invocation or my modifying runner.py) .

This PR re-configures logging after behave is initialised in order to make --no-logcapture behave (sic) as advertised.

Note that this approach is a stop gap and ideally we should pay down the tech debt to allow ourselves to move to behave 1.3.0 and beyond.

@github-actions
Copy link
Contributor

github-actions bot commented Feb 2, 2026

This PR is linked to a ticket in an NHS Digital JIRA Project. Here's a handy link to the ticket:

AEA-0000

@sonarqubecloud
Copy link

sonarqubecloud bot commented Feb 2, 2026

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant