RE : [lwip-devel] testing methods

[Frédéric BERNON]

Right. In my case, I use two differents applications (based on BSD layer) during tests.

 

The first one is a very lwIP's specific using only network functions, without really using the processor :

 

- stack configuration at build time.

- first, I send ping to my lwip's target to check ARP & target's ICMP echo

- ping send from target to several hosts (on my subnet and on others) to test ICMP functions & route with gateway.

- simple dns client to test small UDP send & receive (with SO_RCVTIMEO).

- a syslog sender to test small UDP datagrams.

- a multicast receiver to test IGMP and UDP receives (with SO_RCVTIMEO).

- a simple SMTP sender to test small TCP streams in a half duplex way.

- a simple TELNET connection test to test small TCP connect and/or keepalives and/or in a full duplex way.

- a simple HTTP server to test "larger" TCP streams.

- simple test for SNMP part (just use Net-SNMP).

 

This is not a "formal" framework (sometimes, I don't do all the tests, but only a part to check a new code).

I sometimes use it with TRACE, ASSERT or DEBUG mode.

Problem, some specific OS functions are used ("sleep", "wait thread", etc...).

 

The second one is my real application :

 

- stack configuration at run time.

- Digital Video Compression (so, the DSP is really used and "stressed")

- HTTP/CGI, TELNET, DNS, SNTP, RTSP/RTP, SYSLOG, CIFS, permanent pings, and some others specific ones

- Most of datagrams are in multicast (2x 2Mbps)

- there can be some TCP video streams

- there is possible to upgrade the firmware with datagrams or with HTTP (3MB to upload).

 

This second is use inside our products. I got ~20 units to use with that tests on duration (to see memory leaks & others).

Yesterday, I see they all crash in the same period of time (in few minutes), and I never got that (but they run during 30 hours).

Two solutions : an external event (electrical or others), or a memory leak or corruption. I search now differences between last builds...

 

But..., I'm not sure my boss will be ok to provide some parts of the first one, even "AS IS", but if you want, I will try to see with him...

 

 

====================================
Frédéric BERNON
HYMATOM SA
Chef de projet informatique
Microsoft Certified Professional
Tél. : +33 (0)4-67-87-61-10
Fax. : +33 (0)4-67-70-85-44
Email : address@hiddenr
Web Site : http://www.hymatom.fr
====================================

P Avant d'imprimer, penser à l'environnement

 

-----Message d'origine-----
De : address@hidden [mailto:address@hidden De la part de Taranowski, Thomas (SWCOE)
Envoyé : mardi 13 mars 2007 23:01
À : lwip-devel
Objet : [lwip-devel] testing methods

At the risk of being drug into the street and mauled by angry developers, I’d like to know if we have any sort of informal test framework for the lwIP stack.  I’m pretty confident we all sort of run our own test suite anytime we roll a new build into our respective ports, but I don’t think we have any shared method. 

 

Now, I’m currently working on developing a test suite for my own needs, which will be fairly comprehensive, with respect to the BSD socket layer.  I’d like to propose to my management that we release this to the lwIP community for further enhancement and support.  The primary reason for doing this is because I think it will result in a better product, but another reason, perhaps more compelling for some, is because we’re all doing our own testing thing, and it would be more efficient if we could collaborate on a shared test framework. 

 

Before I work up my proposal, I’d like to know if we already have something, and if anyone else thinks this would be a useful addition to our lwIP project.

Frédéric BERNON.vcf
Description: Frédéric BERNON.vcf