Skip to content

Conversation

@staszczuk
Copy link
Collaborator

@staszczuk staszczuk commented Oct 24, 2025

Add config generator to simplify the process of creating test framework configs.

Add .gitignore for generated configs.

Move example configs to examples directory.

@Sakoram
Copy link
Collaborator

Sakoram commented Oct 27, 2025

I think we should leave a sample configs. Possibly in different directory from where generated ones will be placed, but without any example it will be hard to run tests locally.

@staszczuk staszczuk force-pushed the pstaszczuk/config-generator branch from 020aadf to 773c805 Compare October 27, 2025 15:03
@staszczuk staszczuk changed the title Test: Replace example config files with generator Test: Add test framework config generator Oct 27, 2025
@staszczuk staszczuk force-pushed the pstaszczuk/config-generator branch from 773c805 to a017944 Compare October 27, 2025 15:13
@staszczuk staszczuk force-pushed the pstaszczuk/config-generator branch 2 times, most recently from 04322b5 to 6ab6129 Compare October 27, 2025 15:54
@staszczuk staszczuk enabled auto-merge (rebase) October 28, 2025 12:52
Copy link
Collaborator

@DawidWesierski4 DawidWesierski4 left a comment

Choose a reason for hiding this comment

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

Please call the examples
template

Example is not a widely used word template, works much better

I'm fine with either the folder being called template or the files having
test_config.yaml.template
or test_config_template.yaml

your choice

@staszczuk
Copy link
Collaborator Author

Please call the examples template

Example is not a widely used word template, works much better

I'm fine with either the folder being called template or the files having test_config.yaml.template or test_config_template.yaml

your choice

I would stick to the way of naming example/template configs used by MFD: https://github.com/[intel/pytest-mfd-config](https://github.com/intel/pytest-mfd-config/tree/main)/tree/main.

@DawidWesierski4
Copy link
Collaborator

Please call the examples template
Example is not a widely used word template, works much better
I'm fine with either the folder being called template or the files having test_config.yaml.template or test_config_template.yaml
your choice

I would stick to the way of naming example/template configs used by MFD: [https://github.com/intel/pytest-mfd-config/tree/main](https://github.com/%5Bintel/pytest-mfd-config%5D(https://github.com/intel/pytest-mfd-config/tree/main)/tree/main).

okey then it is fine

Replace the test framework example config files with a config generation
script to simplify the process of creating configs.

Add .gitignore for generated configs.
@staszczuk staszczuk force-pushed the pstaszczuk/config-generator branch from 6ab6129 to 44ddbd8 Compare October 29, 2025 15:52
@staszczuk staszczuk merged commit fdacdbe into main Oct 29, 2025
16 checks passed
@staszczuk staszczuk deleted the pstaszczuk/config-generator branch October 29, 2025 16:01
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.

4 participants