#49168 create_test.py --suit in ds/dirsrvtests creates a file, not directory
Closed: wontfix 7 years ago Opened 7 years ago by amsharma.

Issue Description

create_test.py --suit in ds/dirsrvtests creates a file, not directory

Steps to reproduce

1.python create_test.py --suit setup_ds
Created: setup_ds_test.py

Actual results

Created: setup_ds_test.py

Expected results

It should ideally create a directory for the suit. For ticket it is OK to create a file but for suit, it should create a directory.


Hi Amita,
I think it is better as it is because we don't create a lot of suites directories (maybe we will have to create 2-5 dirs, not much of a room for an automation), mostly, they are already created. Though we do create a lot of new modules inside of each test suite directory.

For example, suites/replication has 5 test suite modules and this number will be increased at least two times. The same situation with another test suite directories.

Because of this, I think it is more efficient to keep create_test.py with a file creation, not a directory with a file.

Metadata Update from @spichugi:
- Custom field reviewstatus adjusted to new
- Custom field type adjusted to defect

7 years ago

As was discussed on IRC, the file creation stays the same. Closing.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

7 years ago

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/2227

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.

Login to comment on this ticket.

Metadata