This seems like a good project. Ballista looks like it is "dead" upstream. You'll want to scope your project to decide what / how much of RTEMS you can reasonably instrument with fault injection. I also wonder if it would be sensible to first start with a tool that can support test input "fuzzing", which is related to but somewhat different than fault injection. I think "fuzzing" is more appropriately related to test coverage /testing, whereas fault injection can include also non-valid inputs and faults, such as flipping bits in code or modifying values on-the-fly.
On Mon, Jul 29, 2013 at 4:25 AM, Krzysztof Mięsowicz <krzysztof.miesow...@gmail.com> wrote: > Hi! > > My name is Krzysiek. I participated in ESA SOCIS 2012 for RTEMS and worked > on improving test coverage. I'm interested in participating in this edition > of SOCIS again. > > I browse Open Projects page of RTEMS and I have question about topic related > to fault injection tools. Have you any tips or suggestions to this topic > (especially which tools are most desired or promising and how this project > should look in details). > > I googled a bit about fault injection and free tools and find some: > Ballista, LFI, Fuzz, or JACA which potentially could be applied to RTEMS > testing. But I'm looking forward to any tips or thoughts from you and > additionaly is it possible to be selected again this year. > > Thanks in advance for your replies. > Krzysiek Mięsowicz > > _______________________________________________ > rtems-devel mailing list > rtems-devel@rtems.org > http://www.rtems.org/mailman/listinfo/rtems-devel > _______________________________________________ rtems-devel mailing list rtems-devel@rtems.org http://www.rtems.org/mailman/listinfo/rtems-devel
