Loading ...
Sorry, an error occurred while loading the content.
 

Re: [XP] Developer Testing in an embedded development

Expand Messages
  • James Grenning
    What kind of failures have you seen? How many have you seen over what time period? How did you fix them? thanks, James ... James Grenning
    Message 1 of 7 , Mar 25, 2010
      What kind of failures have you seen?

      How many have you seen over what time period?

      How did you fix them?

      thanks, James
      -----
      James Grenning
      james@...
      www.renaissancesoftware.net
      www.renaissancesoftware.net/blog
      www.twitter.com/jwgrenning

      On Mar 25, 2010, at 4:01 PM, Andrew wrote:

      >
      >
      > I've employed the dual target strategy: I used Borland Builder as a development system which gave me the one-click build and test TDD cycle, but the embedded target used command-line tools to produce a binary that was downloaded into the target hardware for manual system tests. It was a rare event that the manual tests failed.
      >
      > --
      > Andrew Wall
      > Still not doing XP
      >
      > --- In extremeprogramming@yahoogroups.com, James Grenning <james.grenning@...> wrote:
      > >
      > > Yes, frequent developer testing is possible for embedded development. I presume you are asking due to build and download times that slow the TDD cycle. To overcome that problem it helps to adopt a dual target strategy, where production code and test code are first created and run in the development environment, where a fast cycle is possible. Less frequently, the tests are run in the target environment. You might even make the target runs automated as part of a CI system.
      > >
      > > This approach means that the embedded developer must manage hardware dependencies so that the bulk of the embedded code can be tested off the target. This is a positive design effect of TDD in an embedded environment.
      > >
      > > If you want to read more about it, take a look at some of the info here http://renaissancesoftware.net/papers.html and on my blog.
      > >
      > > BTW: My book "Test Driven Development in Embedded C" is about to be beta released at http://pragprog.com/
      > >
      > > James
      > >
      >
      > > On Mar 24, 2010, at 6:17 AM, Ajithesh Hegde wrote:
      > >
      > > > Hi,
      > > >
      > > > Is frequent developer testing as required by TDD possible in the
      > > > embedded development environment? The question is because, it may be
      > > > difficult to test a module/a group of modules in isolation in an
      > > > embedded development setup.
      > > >
      > > > Rgds
      > > > Ajithesh
      > > >
      >
      >



      [Non-text portions of this message have been removed]
    Your message has been successfully submitted and would be delivered to recipients shortly.