From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?windows-1252?Q?Simon_K=E5gstr=F6m?= Subject: Re: tools brainstorming Date: Fri, 20 Mar 2015 16:18:46 +0100 Message-ID: <550C3A56.5040000@netinsight.net> References: <3571725.20GtF5MAnU@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit To: dev-VfR2kkLFssw@public.gmane.org Return-path: In-Reply-To: <3571725.20GtF5MAnU@xps13> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" On 2015-03-20 15:51, Thomas Monjalon wrote: > As we are lazy developers, writing guidelines is not enough. It must be > coupled with the integration of some tools. Let's work on these ones: > - make autotests easier and faster to run for smoke testing > - automated basic testpmd check > - build check with various options combinations > - abi check (started with validate-abi.sh) > - static analyze (clang, free online coverity) > - comment check (doxygen, codespell, kerspell) > - format check (customized checkpatch) Code coverage for automated tests can be useful as well. In a way I'm speaking in my own interests here since I've written a tool to do just this (and produce nice HTML etc output), kcov, that can be found at github (https://github.com/SimonKagstrom/kcov). // Simon