Skip to content

tests: Add env-var-default.test - #120

Merged
awelzel merged 1 commit into
masterfrom
topic/awelzel/119-default-env
Sep 24, 2025
Merged

awelzel merged 1 commit into
masterfrom
topic/awelzel/119-default-env

Conversation

@awelzel

@awelzel awelzel commented Sep 23, 2025

Copy link
Copy Markdown
Contributor

In #119 it was reported variables from [DEFAULT] do not work within environment sections. Cannot reproduce here, but add a test to see if it fails on some other platform.

In #119 it was reported variables from [DEFAULT] do not work within
environment sections. Cannot reproduce here, but add a test to see
if it fails on some other platform.

@evantypanski evantypanski left a comment •

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems reasonable, the crappy error seems to be from configparser lib. It's just weird since we don't mention "interpolation" anywhere in btest docs, but it's the term they use.

I guess another thing we could do is mention interpolation and link the configparser. This is also mentioned in the README:

(the weird syntax is due to Python's ConfigParser class).

but it's never linked

Though, not a big deal & fine as-is, but I wouldn't oppose more nudging in the README too

@awelzel
awelzel merged commit c1f5885 into master Sep 24, 2025
22 checks passed
@awelzel
awelzel deleted the topic/awelzel/119-default-env branch September 24, 2025 07:25
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.

2 participants