Task #4381
open
Investigate porting NFD integration tests to Mini-NDN environment
30%
Description
Past effort has been trying to run the existing integration tests in Mini-NDN.
https://github.com/ndncomm/mini-ndn
(Also see related issues).
This task will determine whether it is a good idea to port (re-write) the integration tests in Mini-NDN.
If it is then similar to the NLSR integration bot we can run one for NFD and post scores to gerrit changes.
Updated by Ashlesh Gawande about 7 years ago
- Related to Task #3291: Implement NFD integration tests experiment added
Updated by Ashlesh Gawande about 7 years ago
- Related to Task #3055: Investigate feasibility of integration tests which require Ethernet Face support added
Updated by Ashlesh Gawande about 7 years ago
- Subject changed from Investigate porting NFD integration test to Mini-NDN environment to Investigate porting NFD integration tests to Mini-NDN environment
Updated by Alexander Lane over 6 years ago
- Status changed from New to In Progress
Updated by Junxiao Shi almost 6 years ago
NFD integ contains 25 scenarios, but many scenarios are fully covered by unit testing. Having them as integration tests is redundant and increases system complexity.
These are unnecessary:
- cs_freshness
- fib_matching
- hub_discovery
- interest_aggregation
- interest_loop
- localhop
- localhost_scope
- multicast_strategy
- nack
- ndnpeekpoke
- ndnping
- ndntraffic
- nrd
- route_expiration
- route_inheritance
These are important integ scenarios that cannot be fully reproduced as unit tests, and should be given higher priority:
- auto_prefix_propagate
- linkfail
- multicast
- permanent_face
- tcp_udp_tunnel
- unixface
These are partially covered by unit testing, so integ should continue to exist, but worked at a lower priority:
- congestionmark
- mobility_link
- nexthopfaceid
- nfdc