On Wed, Jan 29, 2014 at 07:52:44PM -0500, John Ferlan wrote:
> Adding tests for new virModprobe{Config|Load|Unload|UseBlacklist} API's.
> Other than the virModprobeConfig() calls, the tests require some special
> set up and to be run from root.
The unit tests need to be isolated from the host OS entirely. For the
load/unload APIs we could use the newly introduced 'virCommandSetDryRun'
API to let us test them. Basically we only want to validate that the
API is invoking the right set of commands / args. We don't actually
want to affect our host kernel / os.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list