New book: Test Driven Design for Embedded C
1 view
Skip to first unread message
charlesmanning
Apr 28, 2010, 10:35:41 PM4/28/10
to South Island Embedded
As some folk know, I have a policy for yaffs that I call "Test
Tuesday". One day a week is devoted to improving test harnesses and
other process infrastructure. That's normally a Tuesday, but sometimes
ends up being a different day. Testing, of course happens all the time
which is something you can do a lot easier with automated test
harnesses. I have a quad core test box that sits maxed out running
tests most of the time. Automated testing is a good investment as once
you've set it up the tests run for free.
I'm always on the look out for new methods to do embedded system/ OS
testing and was interested to see that there's finally a book in the
works devoted to the subject.
The book is Test Driven Design for Embedded C from www.pragprog.com.
http://pragprog.com/titles/jgade/test-driven-development-for-embedded-c
I've read a lot of Pragmatic Programmers books and they are generally
quite helpful.
The new TDD book is still in beta and can be bought as an ebook/pdf.
You get to download updates as they progress. The dead-tree version
will be available later this year. There is also a forum/feedback
where you can suggest improvements etc. If you want to spread your
embedded wisdom, here's an opportunity...
This book could be a useful political tool for those trying to
convince a development group/ management to adopt TDD as it does do a
reasonable job of explaining many of the benefits.
My impression so far is that the book will be helpful to those
exploring TDD but it is probably not going to significantly benefit
those that are already into TDD in a big way. Some of the areas that
look particularly interesting are still TODO. Perhaps those chapters
will really be more interesting.
Tuesday". One day a week is devoted to improving test harnesses and
other process infrastructure. That's normally a Tuesday, but sometimes
ends up being a different day. Testing, of course happens all the time
which is something you can do a lot easier with automated test
harnesses. I have a quad core test box that sits maxed out running
tests most of the time. Automated testing is a good investment as once
you've set it up the tests run for free.
I'm always on the look out for new methods to do embedded system/ OS
testing and was interested to see that there's finally a book in the
works devoted to the subject.
The book is Test Driven Design for Embedded C from www.pragprog.com.
http://pragprog.com/titles/jgade/test-driven-development-for-embedded-c
I've read a lot of Pragmatic Programmers books and they are generally
quite helpful.
The new TDD book is still in beta and can be bought as an ebook/pdf.
You get to download updates as they progress. The dead-tree version
will be available later this year. There is also a forum/feedback
where you can suggest improvements etc. If you want to spread your
embedded wisdom, here's an opportunity...
This book could be a useful political tool for those trying to
convince a development group/ management to adopt TDD as it does do a
reasonable job of explaining many of the benefits.
My impression so far is that the book will be helpful to those
exploring TDD but it is probably not going to significantly benefit
those that are already into TDD in a big way. Some of the areas that
look particularly interesting are still TODO. Perhaps those chapters
will really be more interesting.
charlesmanning
May 2, 2010, 8:47:24 PM5/2/10
to South Island Embedded
I keep on calling this book Test Driven Design for Embedded C.
It is actually called Test Driven Development for Embedded C.
On Apr 29, 2:35 pm, charlesmanning <cdhmann...@gmail.com> wrote:
> As some folk know, I have a policy for yaffs that I call "Test
> Tuesday". One day a week is devoted to improving test harnesses and
> other process infrastructure. That's normally a Tuesday, but sometimes
> ends up being a different day. Testing, of course happens all the time
> which is something you can do a lot easier with automated test
> harnesses. I have a quad core test box that sits maxed out running
> tests most of the time. Automated testing is a good investment as once
> you've set it up the tests run for free.
>
> I'm always on the look out for new methods to do embedded system/ OS
> testing and was interested to see that there's finally a book in the
> works devoted to the subject.
>
> The book is Test Driven Design for Embedded C fromwww.pragprog.com.http://pragprog.com/titles/jgade/test-driven-development-for-embedded-c
It is actually called Test Driven Development for Embedded C.
On Apr 29, 2:35 pm, charlesmanning <cdhmann...@gmail.com> wrote:
> As some folk know, I have a policy for yaffs that I call "Test
> Tuesday". One day a week is devoted to improving test harnesses and
> other process infrastructure. That's normally a Tuesday, but sometimes
> ends up being a different day. Testing, of course happens all the time
> which is something you can do a lot easier with automated test
> harnesses. I have a quad core test box that sits maxed out running
> tests most of the time. Automated testing is a good investment as once
> you've set it up the tests run for free.
>
> I'm always on the look out for new methods to do embedded system/ OS
> testing and was interested to see that there's finally a book in the
> works devoted to the subject.
>
Grant Sullivan
May 15, 2010, 6:07:21 PM5/15/10
to south-isla...@googlegroups.com
Designing for test has lead me to the world for embedded RTOS. After
ditching the if/while loops world for a world of interrupts, events and
lots of sleeping.
Working with a handfull of embedded RTOS products for embedded systems over
the last decade I have chosen to stick with the Quantum Framwork product.
This RTOS will let me know with assert messages if a task have taken too
long to complete or event stacks have overflowed. Also as this RTOS design
is built on the hierarchical state machine model it allows a piece of code
to be tested in isolation from the other state machines processes in play.
Then couple this up to a real world dedicated hardware test enviroment,
trying to best mimick the real world.
I have not had the option to use the dual targeting design, as the work I do
doesn't require a great deal for specialised hardware, so target hardware is
not so hard to produce.
QF NANO for embedded systems has proven to be a good product for making
realiable 24/7 embedded solution .
http://www.state-machine.com/
--------------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.437 / Virus Database: 271.1.1/2837 - Release Date: 04/26/10
18:27:00
ditching the if/while loops world for a world of interrupts, events and
lots of sleeping.
Working with a handfull of embedded RTOS products for embedded systems over
the last decade I have chosen to stick with the Quantum Framwork product.
This RTOS will let me know with assert messages if a task have taken too
long to complete or event stacks have overflowed. Also as this RTOS design
is built on the hierarchical state machine model it allows a piece of code
to be tested in isolation from the other state machines processes in play.
Then couple this up to a real world dedicated hardware test enviroment,
trying to best mimick the real world.
I have not had the option to use the dual targeting design, as the work I do
doesn't require a great deal for specialised hardware, so target hardware is
not so hard to produce.
QF NANO for embedded systems has proven to be a good product for making
realiable 24/7 embedded solution .
http://www.state-machine.com/
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.437 / Virus Database: 271.1.1/2837 - Release Date: 04/26/10
18:27:00
Reply all
Reply to author
Forward
0 new messages