Another information, we would like to mention is about UUID docstring.
For every new test case, we need to have UUID in the docstring and that should be generated using python -c 'import uuid; print(uuid.uuid4())' .
Duplicate values will be handled by https://pagure.io/389-ds-base/blob/master/f/dirsrvtests/create_test.py#_119

Thanks!

I don't understand what you mean about the docstring? What function does it serve? I would really like to understand this.

I don't understand what you mean about the docstring? What function does it serve? I would really like to understand this.
We need it for Polarion.

So the testcase id is added by create_test anyway, so I don't think we need to add it. I've now updated the wiki pages as you asked :)

I think that we should review the steps in the future, as these seem overly complex for our scenarios and I think we can do better - I certainly have simpler setup than this on my own machine.

Hi William,

Thanks for doing it. But we still need testcase ID information as create_test only creates it for 1 test case, rest of the newly added test cases need to have ID generated the way mentioned above.

And, for the simpler steps - should I open another ticket :)

Regards,
Amita

I don't quite get what you mean: if you need test cases id's in every test, that's not a wiki problem, that's a "lets write some code" problem.

Create_test should create the id's automatically from what I was reading.

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 issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/2226

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.