Due to the large number of input fuzzing tests that have been submitted, I've been thinking of ways to reduce the amount of code needed to achieve this (whether we should do it or not is a totally different discussion). Rather than have x number of input tests for say create server, wouldn't it be far easier to have a single create server fuzz test which is data driven and accepts the desired inputs and the expected exception. So instead of this (pseudo-coded things up a bit):
https://gist.github.com/2919066 we could get the same effect with much less code by doing this: https://gist.github.com/2919177 Regardless of implementation, I think the general idea of moving this type of testing towards data driven functions would really help cut down on redundant code. Daryl -- Mailing list: https://launchpad.net/~openstack-qa-team Post to : openstack-qa-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-qa-team More help : https://help.launchpad.net/ListHelp
