[TOS] Textbook: next steps
adam hyde
adam at flossmanuals.net
Sat Aug 1 11:54:03 UTC 2009
hey guys,
i'd been meaning to join the list for a while, and finally i've done
so...as an intro - I am Adam Hyde, and I founded FLOSS Manuals. We write
free documentation and text books about free software
(http://www.flossmanuals.net)
this looks like a good book...I was wondering if you would like to
utilise the FLOSS Manuals framework to write it...it makes collab
authoring a little easier and can output to boof formatted pdf etc...the
material could then be re-imported into the teaching open source site
adam
On Fri, 2009-07-31 at 12:59 -0400, Greg DeKoenigsberg wrote:
> On Sun, 26 Jul 2009, Joel Sherrill wrote:
>
> > On Thu, Jul 2, 2009 at 4:09 PM, Greg DeKoenigsberg<gdk at redhat.com> wrote:
> >>
> >> 6 Testing
> >> Chris? Clif?
> >
> > Has anyone done any work on this chapter?
>
> I don't believe so. The outline is still completely empty.
>
> > I ask because one of the RTEMS GSoC Projects is focused on code coverage
> > analysis of our core codebase. We are actually generating test reports
> > which show which assembly statements in C routines are executed. The
> > reports map these back to the source code and I am mentoring the student
> > so our coverage percentage is increasing. We are now at about 99.5% of
> > the generated assembly being executed by our test suite. This includes
> > oddball cases like interrupt synchronization and conflict resolution
> > logic in the OS. Interestingly since one of the targets is a SPARC, we
> > can actually tell when a branch is taken or not taken in many cases.
> > :)
> >
> > I know the Testing can cover a lot of ground with things like Junit and
> > friends, automated test frameworks, test case generation, and even
> > advice on debugging techniques.
> >
> > I do not have time to write this alone but would be happy to work with
> > someone to put some meat in this chapter. If you think the RTEMS
> > Coverage Testing is interesting to include, I can focus on turning the
> > technical report I think we need into something useful for the chapter.
>
> I think what really needs to happen is that someone knowledgeable in
> testing needs to put together a basic outline. And the focus should be on
> actionable stuff: some time should be spent describing what a test plan
> is, and then an assignment could be to select a feature from some open
> source project and propose a testing plan.
>
> But fleshing out the outline is the first step, I think. Please feel free
> to work on the testing chapter outline:
>
> http://teachingopensource.org/index.php/User:Gregdek/Textbook
>
> --g
>
> --
> Computer Science professors should be teaching open source.
> Help make it happen. Visit http://teachingopensource.org.
> _______________________________________________ tos mailing list tos at teachingopensource.org http://teachingopensource.org/mailman/listinfo/tos
--
Adam Hyde
Founder FLOSS Manuals
German mobile : + 49 15 2230 54563
Email : adam at flossmanuals.net
irc: irc.freenode.net #flossmanuals
"Free manuals for free software"
http://www.flossmanuals.net/about
More information about the tos
mailing list