On Sat, Aug 16, 2014 at 3:28 AM, Sebastien J. <[email protected]> wrote: > I'd start with the parts that process input, particularly from the client. > > Good point indeed. From a run-time perspective, the new python SPA packet fuzzer together with -DFUZZING_INTERFACES also helps with this. It currently generates nearly a half-million SPA packets with various malicious content, and the code coverage it achieves against libfko is pretty good. I'm probably going to extend the fuzzer to generate (optionally) millions of SPA packets. I think the c unit framework would add another aspect of testing as well that is more in line with more standard unit testing techniques. Seems like both strategies in concert would be powerful.
Thanks, --Mike > // Sebastien > > On 16 Aug 2014, at 04:01 am, Michael Rash <[email protected]> wrote: > > > > On Fri, Aug 15, 2014 at 3:46 PM, Franck Joncourt <[email protected]> > wrote: > >> Hi michael, >> >> Have you thought about using c unit framework to improve code coverage? >> From my point of view fwknop test suite is built as an integration test >> suit, with improved capabilities such as fault injection. Any thoughts >> about unit testing? >> >> > Hello Franck, > > I think using the c unit framework would be a good addition. It would > likely help test certain portions of the code more rigorously - would you > agree? I'm not well versed in the c unit framework though, and I need to > work on that. I wonder which portions of the code could use the framework > the most? > > Thanks, > > --Mike > > > > >> Regards, >> >> Franck >> >> On 8 août 2014 03:55:50 HAEC, Michael Rash <[email protected]> >> wrote: >> >>> >>> Hi all, >>> >>> With all of the effort that went into the fwknop-2.6.3 test suite, I >>> thought I would write up a few techniques that it uses: >>> >>> >>> http://www.cipherdyne.org/blog/2014/08/code-coverage-challenges-for-open-source-projects.html >>> >>> This ended up being a set of challenges that can apply more broadly to >>> open source projects in general. Contained in this post code coverage >>> results not only for fwknop, but also for OpenSSH-6.6p1 and OpenSSL-1.0.1h. >>> >>> Thanks, >>> >>> --Mike >>> >>> ------------------------------ >>> >>> Want fast and easy access to all the code in your enterprise? Index and >>> search up to 200,000 lines of code with a free copy of Black Duck >>> >>> Code Sight - the same software that powers the world's largest code >>> search on Ohloh, the Black Duck Open Hub! Try it now. >>> http://p.sf.net/sfu/bds >>> >>> ------------------------------ >>> >>> Fwknop-discuss mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/fwknop-discuss >>> >>> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Fwknop-discuss mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/fwknop-discuss >> >> > > > -- > Michael Rash | Founder > http://www.cipherdyne.org/ > Key fingerprint = 53EA 13EA 472E 3771 894F AC69 95D8 5D6B A742 839F > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Fwknop-discuss mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/fwknop-discuss > > -- Michael Rash | Founder http://www.cipherdyne.org/ Key fingerprint = 53EA 13EA 472E 3771 894F AC69 95D8 5D6B A742 839F
------------------------------------------------------------------------------
_______________________________________________ Fwknop-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fwknop-discuss
