-
Notifications
You must be signed in to change notification settings - Fork 664
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
Add tests for import_tasks
and include_tasks
target lookup
#1445
Conversation
1343251
to
a4ee5ea
Compare
Please adjust the explanation and the title to mention what this test is about. |
import_tasks
and include_tasks
target lookup
1a2da16
to
7024149
Compare
7024149
to
3f00d00
Compare
Regression tests for issue number 1446
3f00d00
to
6cff3f9
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.
I think it looks great now. But I'll leave it to @ssbarnea to merge this.
@pytest.mark.parametrize( | ||
'ansible_project_layout', | ||
( | ||
pytest.param(LAYOUT_IMPORTS, id='using only import_tasks'), |
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.
Usually I prefer test ids that do not have spaces or special chars, so I can use them with -k
without trouble but I will likely fix it next time we need to touch the test, hopefully soon for removal of xfail.
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.
FWIW spaced ids work with -k
just fine. But I prefer concrete specifiers like tox -- 'test/TestFilePathEvaluation.py::test_file_path_evaluation[using only include_tasks]'
Ansible-lint incorrectly evaluates the file path when
import_tasks
orinclude_tasks
is used because of a bug that was reported in the following issue #1446.import_tasks
include_tasks