Project

General

Profile

Actions

Task #4381

open

Investigate porting NFD integration tests to Mini-NDN environment

Added by Ashlesh Gawande over 6 years ago. Updated over 5 years ago.

Status:
In Progress
Priority:
Normal
Category:
-
Target version:
-
Start date:
11/10/2017
Due date:
% Done:

30%

Estimated time:

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.


Related issues 2 (1 open1 closed)

Related to mini-ndn - Task #3291: Implement NFD integration tests experimentAbandonedVince Lehman10/26/2015

Actions
Related to mini-ndn - Task #3055: Investigate feasibility of integration tests which require Ethernet Face supportNew07/17/2015

Actions
Actions #1

Updated by Ashlesh Gawande over 6 years ago

  • Related to Task #3291: Implement NFD integration tests experiment added
Actions #2

Updated by Ashlesh Gawande over 6 years ago

  • Related to Task #3055: Investigate feasibility of integration tests which require Ethernet Face support added
Actions #3

Updated by Ashlesh Gawande over 6 years ago

  • Subject changed from Investigate porting NFD integration test to Mini-NDN environment to Investigate porting NFD integration tests to Mini-NDN environment
Actions #4

Updated by Ashlesh Gawande over 6 years ago

  • Assignee deleted (Saurab Dulal)
Actions #5

Updated by Alexander Lane almost 6 years ago

  • Assignee set to Alexander Lane
Actions #6

Updated by Alexander Lane almost 6 years ago

  • Status changed from New to In Progress
Actions #7

Updated by Alexander Lane almost 6 years ago

  • % Done changed from 0 to 30
Actions #8

Updated by Junxiao Shi over 5 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
Actions

Also available in: Atom PDF