On Mar 28, 2005, at 9:06 AM, Neil Hancock wrote:
I'm also thinking about the same issue - how to do path level code coverage
on the motes in a reasonably productive manner, and then integrate it into
and debug on mote2dot.
Path-level code coverage is a bit tricky, due to the component separations and implicit shared state across those boundaries.
My approach so far is to do so probabilistically. I try out lots of scenarios with many nodes. As my code is almost always application level (not, for example, a radio stack), I've found TOSSIM to generally be sufficient. If there's a real crazy edge case that I think unlikely to happen, then I trigger it explicitly, through Tython or a simple nesC test case framework.
This hasn't caught every single edge case, but usually those that remain are performance, rather than correctness problems, which I then slowly discover and work through (e.g., send a redundant message rather than crash).
Phil
-------
"We shall not cease from exploration And the end of all our exploring Will be to arrive where we started And know the place for the first time."
- T. S. Eliot, 'Little Gidding'
_______________________________________________ Tinyos-users mailing list [email protected] http://mail.Millennium.Berkeley.EDU/mailman/listinfo/tinyos-users
