in reply to TDD when some components talk to hardware?

If you use telnet anyway you can write a test server that behaves like the hardware.

Depending on the emulated hardware it might be enough to dump the TCP streams with wireshark and emit them verbatimly in your test server. If that's not enough, you have to model the hardware, which is probably not a nice job.

In either case it helps to have good abstraction layer, so that you can provide a different backend to test applications that normally talk to your software.

  • Comment on Re: TDD when some components talk to hardware?

Replies are listed 'Best First'.
Re^2: TDD when some components talk to hardware?
by lwicks (Friar) on Apr 18, 2008 at 14:19 UTC
    I think I will be going down the route suggested by moritz. In that I think I will code up dummy applications that respond in the appropriate manner.

    This is becoming approach #1 as I think that my test hardware is going to be moved to a different physical location.

    Thx.

    Kia Kaha, Kia Toa, Kia Manawanui!
    Be Strong, Be Brave, Be perservering!

[reply]

In Section Seekers of Perl Wisdom