-
Notifications
You must be signed in to change notification settings - Fork 77
Test: Add test framework config generator #1303
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
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. |
020aadf to
773c805
Compare
773c805 to
a017944
Compare
04322b5 to
6ab6129
Compare
There was a problem hiding this 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
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. |
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.
6ab6129 to
44ddbd8
Compare
Add config generator to simplify the process of creating test framework configs.
Add
.gitignorefor generated configs.Move example configs to
examplesdirectory.