Nice porting! Thanks!

Couple of small things we can improve:

We already use the marks for bugzillas and I think we should continue with it.
You can find the associated BZ in the pagure issue and set it like this:
@pytest.mark.bz1118014
@pytest.mark.bz1257294

You don't have the expected results for the step.

We already use the marks for bugzillas and I think we should continue with it. You can find the associated BZ in the pagure issue and set it like this: @pytest.mark.bz1118014 @pytest.mark.bz1257294

I think we should use ticket numbers (and an optional bz number). Not all tickets have a corresponding bugzilla and not all bugzillas are public.

As for the mark format I propose pytest.mark.ds12345 instead of tk12345 similar to Dev whiteboard in bugzilla.

I think we should use ticket numbers (and an optional bz number). Not all tickets have a corresponding bugzilla and not all bugzillas are public.
As for the mark format I propose pytest.mark.ds12345 instead of tk12345 similar to Dev whiteboard in bugzilla.

Ok, it makes sense. I agree.

Nice porting! Thanks!
Couple of small things we can improve:

Yes, I will change the doc-string in the steps, missed that Thanks ! @spichugi

We already use the marks for bugzillas and I think we should continue with it. You can find the associated BZ in the pagure issue and set it like this: @pytest.mark.bz1118014 @pytest.mark.bz1257294

I think we should use ticket numbers (and an optional bz number). Not all tickets have a corresponding bugzilla and not all bugzillas are public.
As for the mark format I propose pytest.mark.ds12345 instead of tk12345 similar to Dev whiteboard in bugzilla.

Sure will do the appropriate changes, Thanks for looking into this @vashirov

Ack. Please, rebase it with current master and we can merge.

Ack. Please, rebase it with current master and we can merge.

Sure thanks!

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This pull request has been cloned to Github as issue and is available here:
- https://github.com/389ds/389-ds-base/issues/2751

If you want to continue to work on the PR, please navigate to the github issue,
download the patch from the attachments and file a new pull request.

Thank you for understanding. We apologize for all inconvenience.