Re: Anaconda and python-coverage

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> I've finally managed to get `coverage report' to report on
> pyanaconda by changing the initialization line to:
> 
> cov = coverage.coverage(data_file='/mnt/sysimage/root/anaconda.coverage',
>                         branch=True,
>                         source=['/usr/sbin/anaconda', 'pyanaconda']
>                        )
> 
> Which misses other modules like pykickstart, yum and blivet from my previous try.
> 
> I'm not sure why without the source parameter coverage doesn't pick
> up pyanaconda (it's in site-packages after all), I've been asking
> its maintainer about this.
> 
> The question now is which modules do we want to have reported ? Only
> /sbin/anaconda and pyanaconda or more ?  Any thoughts are welcome.

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.

- Chris

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list




[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux