Export support --bugzilla to link case

[lukaszachy]

Todo:

• Error handling (permissions, login,...)
• Test coverage

All done, ready for final review

[lgtm-com]

This pull request introduces 1 alert when merging d129af2 into 377dd6b - view on LGTM.com

new alerts:

• 1 for Unused local variable

[lukaszachy]

The 'export' part should be ready. Asking for your feedback.

[lgtm-com]

This pull request introduces 3 alerts when merging 5ea421c into 377dd6b - view on LGTM.com

new alerts:

• 2 for Wrong name for an argument in a call
• 1 for Unused local variable

[lukaszachy]

/packit test

[psss]

@hegerj, perhaps something you would like to have a look at?

[psss]

Thanks for implementing this! Looks good and works as expected. Added a short mention about the new feature to the documentation plus a couple of minor adjustments in aff7103. Please, have a look if everything's ok.

[lukaszachy]

@psss LGTM, thanks for adjustments.

[psss]

Good, thanks. The integration test seems to be failing. Could you please have a look?

[psss]

Tests are failing in a weird way, seems we need a requre expert. @jscotka, could you please have a look what could be wrong? The newly added test passes but other two existing are now failing.

[lukaszachy]

What I found so far:

• if newly added test doesn't run tmt (--> require is not used there) or is disabled then all test pass
• moving newly added test to own class didn't help

test_create fails with unable to create a test case error which is raised as returned dict (from require's tcms call) doesn't contain case_id (which would be if case was created). But I don't see how this could happen. test_create require playbook was not touched at all.

[jscotka]

there is correlation between nitrate cache and order of test case execution inside pytest.
There is more ways how to fix this:

1. disable nitrate cache and rut without caching and regenerate the data
2. let's do separate tmt cases for each test inside pytest and regenerate
3. document this issue and just try to let new cases at the end and then regenerate just new one. (but when execute test alone will lead to error.)

[lukaszachy]

I've pushed commit which splits tests/integration execution into two virtual cases. Not ideal but hopefully it will work

[lukaszachy]

fedora-35 issue is caused by sphinx not yet supporting python 3.10 (sphinx-doc/sphinx#9562)

[jscotka]

I've pushed commit which splits tests/integration execution into two virtual cases. Not ideal but hopefully it will work

Yep, it is possible solution. better would be to split all testcases, instead of random splittng, because then when you execute some testcases by pytest alone it will fail as well, because now it depends on order.

Or maybe better solution could be to clean nitrate cache after each testcase, then it should be more predicable.
@psss it is possible to clean all nitrate cache on demand e.g. in tearDown ?

[lukaszachy]

Personally I'd prefer to get this PR merged and do the testsuite improvements as a separate effort.
Pipeline is passing.

[psss]

@psss it is possible to clean all nitrate cache on demand e.g. in tearDown ?

Yes, it's possible to call Cache().clear() to clean up the cache content. But I agree with @lukaszachy to address this as a separate pull request.

[psss]

Rebased and squashed, let's see if tests are green.

[psss]

Known failure on Fedora 34, otherwise green.