На 12.02.2014 17:19, Chris Lumens написа:
I already have a coverage target in pykickstart that I run from time to
time, so I'm not concerned about that. I imagine it'd be pretty easy
to do the same with blivet. So I guess I'd just stick with pyanaconda
for the moment and if we notice serious gaps, we can add other modules
later.
Sounds good to me and btw QE has already requested coverage support for the
other modules. I've just filed a bug for blivet today. See:
https://bugzilla.redhat.com/show_bug.cgi?id=1064895 - python-blivet
https://bugzilla.redhat.com/show_bug.cgi?id=1057626 - pyparted
Are you OK with activating coverage when 'debug=1' is passed on the boot command
line or should I add a 'coverage' parameter ?
How about the hard-coded path I'm using ? Any suggestions for that?
Let me know your preferences and I'll follow up with patches for review.
--
Alex
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
