lwIP - A Lightweight TCP/IP stack - Tasks: task #7930, Create automatic test cases
You are not allowed to post comments on this tracker with your current authentication level.
task #7930: Create automatic test cases
Submitter: | Simon Goldschmidt <goldsimon> | ||
Submitted: | Tue 08 Apr 2008 05:20:02 PM UTC | ||
Category: | None | Should Start On: | Tue 08 Apr 2008 12:00:00 AM UTC |
Should be Finished on: | Tue 08 Apr 2008 12:00:00 AM UTC | Priority: | 5 - Normal |
Status: | Done | Privacy: | Public |
Assigned to: | None | Percent Complete: | 10% |
Open/Closed: | Closed | Planned Release: | None |
Effort: | 0.00 |
Jump to the original submission
Fri 12 Nov 2021 09:36:21 PM UTC, comment #8: |
Simon Goldschmidt <goldsimon> |
Fri 27 Nov 2009 08:05:57 AM UTC, comment #7: First unit tests added, mainly for testing tcp ooseq processing. |
Simon Goldschmidt <goldsimon> |
Fri 27 Jun 2008 06:22:28 PM UTC, comment #6: Great news! But at least for unit tests, I'd prefer them to be under the LWIP_SRC/test/ (LWIP_SRC being the dir where the CHANGELOG file is). This is because it tests the main tree and I hope tests are more 'in sync' with the code if they are in the same tree.
|
Simon Goldschmidt <goldsimon> |
Fri 27 Jun 2008 12:05:08 PM UTC, comment #5: That's great Thomas. contrib/test sounds like a good place for it, and once we've got something there it will, I hope, get the ball rolling and more may follow. |
Kieran Mansley <kieranm> |
Fri 27 Jun 2008 11:40:30 AM UTC, comment #4: The lwIP test harness I was talking about last year has been completed, and I'm working on getting it open-sourced. It's a black-box (works through socket-api) test framework, implemented using python on a user PC, and interfaces to the embedded target via a network interface. It's implemented in a fairly general manner, so it's suitable for mass consumption.
|
Thomas Taranowski <taranowski> |
Tue 15 Apr 2008 11:17:52 AM UTC, comment #3: Thank you Erik, I hope be able to try your tests this weekend.
|
Frédéric Bernon <fbernon> |
Tue 08 Apr 2008 07:58:09 PM UTC, comment #2:
|
Simon Goldschmidt <goldsimon> |
Tue 08 Apr 2008 06:54:50 PM UTC, comment #1: Ideally with unit tests one tests as small bit of the code as possible, so I think it is a good idea to start with the support code.
|
Erik Ekman <yarrick> |
Tue 08 Apr 2008 05:20:02 PM UTC, original submission:
On lwip-users, we kind of agreed to include test-cases based on the 'check' framework (http://check.sourceforge.net/) into a new CVS folder (src/test ?). (The check framework is also available as package in cygwin!)
|
Simon Goldschmidt <goldsimon> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2021-11-12 | goldsimon | Status | None | Done | |
Open/Closed | Open | Closed | |||
2010-01-10 | goldsimon | Percent Complete | 0% | 10% |
Powered by Savane 3.13-758e.
Corresponding source code
Closing: no need to keep this open... Even if we could have more unit tests...