[Avocado-devel] Static code checking in avocado and avocado-vt
Cleber Rosa
crosa at redhat.com
Thu Nov 19 20:59:56 UTC 2015
Hi Alan,
You may want to take a look at selftests/checkall. It uses inspektor[1], which includes pylint checks. Can you give a list of failures? Those may be related to version and/or configurations, but we should check!
[1] - https://github.com/autotest/inspektor
Thanks!
CR.
----- Original Message -----
> From: "Alan Evangelista" <alanoe at linux.vnet.ibm.com>
> To: avocado-devel at redhat.com
> Sent: Thursday, November 19, 2015 5:49:14 PM
> Subject: [Avocado-devel] Static code checking in avocado and avocado-vt
> I have noticed avocado and avocado-vt don't pass pylint (1.4.3) validation.
> Do you guys use any static code checker during development and testing in
> Travis CI?
> If not, is there a reason why not? I use Pylint in all my Python projects and
> it helps me a lot to detect bugs early, before running test suites. A patch
> which makes code pass Pylint (or other static code checker of your choice)
> validation would be viable and desired?
> Regards,
> Alan Evangelista
> _______________________________________________
> Avocado-devel mailing list
> Avocado-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/avocado-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/avocado-devel/attachments/20151119/d4fb83a2/attachment.htm>
More information about the Avocado-devel
mailing list