Bug 34548 - Test CLI tool create_ou
Test CLI tool create_ou
Status: RESOLVED FIXED
Product: UCS@school
Classification: Unclassified
Component: ucs-test
UCS@school 3.2 R2
Other Linux
: P5 normal (vote)
: ---
Assigned To: Bugzilla Mailingliste
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-04-15 10:02 CEST by Sönke Schwardt-Krummrich
Modified: 2016-10-13 15:17 CEST (History)
0 users

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sönke Schwardt-Krummrich univentionstaff 2014-04-15 10:02:21 CEST
For refactoring the CLI tool "create_ou" all functions should be tested via ucs-test. Currently the tool uses it's own implementation (which shall be used as reference!).

The upcoming UCS@school import library will provide the same functionality as the import CLI tools and will be used within the CLI tools in near future.

Ideally the test script is able to test the CLI tool as well as the import lib.
Comment 1 Stefan Gohmann univentionstaff 2014-05-02 11:12:09 CEST
CLI interface tests have been added: r49740
Comment 2 Sönke Schwardt-Krummrich univentionstaff 2014-05-05 17:31:08 CEST
The test case "import_ou_with_existing_dc(use_cli_api=True)" should call
"move_domaincontroller_to_ou --dcname <dcname> --ou <ou>" directly after creating the OU and before verifying the OU structure. Otherwise the test will fail.
Comment 3 Stefan Gohmann univentionstaff 2014-05-08 11:40:47 CEST
(In reply to Sönke Schwardt-Krummrich from comment #2)
> The test case "import_ou_with_existing_dc(use_cli_api=True)" should call
> "move_domaincontroller_to_ou --dcname <dcname> --ou <ou>" directly after
> creating the OU and before verifying the OU structure. Otherwise the test
> will fail.

This has been fixed. The fix from Bug #34767 is needed for this test.
Comment 4 Florian Best univentionstaff 2015-05-04 18:17:05 CEST
Is it okay that the subnet address is hardcoded as '10.20.30.0'?
Comment 5 Sönke Schwardt-Krummrich univentionstaff 2016-10-13 15:17:01 CEST
(In reply to Florian Best from comment #4)
> Is it okay that the subnet address is hardcoded as '10.20.30.0'?

I would say "yes". Not optimal, but okay for now.