Skip to content

test: use "@pytest.mark.complete" where applicable - #1726

Merged
scop merged 1 commit into
scop:mainfrom
akinomyoga:pytest.mark.complete
Aug 13, 2026
Merged

test: use "@pytest.mark.complete" where applicable#1726
scop merged 1 commit into
scop:mainfrom
akinomyoga:pytest.mark.complete

Conversation

@akinomyoga

Copy link
Copy Markdown
Collaborator

#1715 (comment)

I've checked all the occurrences of completion = . I realized that those were mainly added by me, in particular in class TestMake2 and class TestUnitFiledirXspec. The other TestMake* were copied by followers.

In "test/t/{test_make.py,unit/test_compgen_filedir_xspec.py}", the
plain "completion = assert_complete(...)" can be replaced with
"@pytest.mark.complete" markers.

For "test/t/unit/test_unit_compgen_{commands,filedir}.py", the
"class"-scope fixture "functions" are ensured to be initialized before
the "function"-scope fixture "completion", so we can use "completion"
even when the test relies on "functions".

[1] scop#1715 (comment)
@akinomyoga
akinomyoga force-pushed the pytest.mark.complete branch from e2fae71 to abc010a Compare August 13, 2026 17:18
@scop
scop merged commit bc8ed57 into scop:main Aug 13, 2026
9 checks passed
@akinomyoga
akinomyoga deleted the pytest.mark.complete branch August 13, 2026 21:31
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