#48017 lib389 - add script to generate test script
Closed: wontfix None Opened 5 years ago by mreynolds.

Create a script where you can specify the ticket number, replicas, etc, and it will generate a test script/template. It should generate the topology, test, final, and run_isolated functions. Then only the "test' function will need to be completed by the user.


Very cool!

It's be nice if you could note that if -m -h -c options, standalone test case is generated in the usage. (but once it's learned, there's no difficult, though... :)

create_ticket.py -t <ticket number> [-m|--masters <number of masters> -h|--hubs <number of hubs> -c|--consumers <number of consumers> -o|--outputfile]

Replying to [comment:2 nhosoi]:

Very cool!

It's be nice if you could note that if -m -h -c options, standalone test case is generated in the usage. (but once it's learned, there's no difficult, though... :)

I'll update the usage, and I want to make a few more adjustments to the scripts (like multiple standalone instances, etc). I'll be sending a new patch out for review later today...

create_ticket.py -t <ticket number> [-m|--masters <number of masters> -h|--hubs <number of hubs> -c|--consumers <number of consumers> -o|--outputfile]

Improved the usage, and added support for 10 standalone servers, and 10 masters, hubs, and consumers.

New patch attached...

Thanks a lot, Mark! The new usage and option '-i' is very clear.

(And sorry about my previous comments. I'm glad you understood what I was hoping to tell you. It was soooo buggy, wasn't it? :p)

Replying to [comment:5 nhosoi]:

Thanks a lot, Mark! The new usage and option '-i' is very clear.

(And sorry about my previous comments. I'm glad you understood what I was hoping to tell you. It was soooo buggy, wasn't it? :p)

It wasn't that bad :-)

18547e4..f68e2d4 master -> master
commit f68e2d4
Author: Mark Reynolds mreynolds@redhat.com
Date: Thu Jan 29 08:56:06 2015 -0500

Milestone lib389 1.0 deleted

Metadata Update from @mreynolds:
- Issue assigned to mreynolds

3 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/1348

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.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)

2 months ago

Login to comment on this ticket.

Metadata