Project

General

Profile

Actions

Task #4401

closed

Feature #4279: Self-learning strategy

Unit tests for Self-learning Forwarding Strategy

Added by tianxiang li almost 7 years ago. Updated 12 months ago.

Status:
Abandoned
Priority:
Normal
Assignee:
-
Category:
Forwarding
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:

Description

Write two test cases for Broadcast-based Self-learning Forwarding Strategy.

Test Case 1 (Wired network scenario):
Set up point to point link with three nodes, node A broadcast packet to node B and C.
Node B and C returns data packet, Node A creates the corresponding forwarding table.
Node A unicast to Node B based on self-learned forwarding path .
Check that only Node B received the packet.

Test case 2 (Wireless network scenario):
Set up multicast link with three nodes, node A broadcast packet to node B and C using multicast face.
Node B and C returns data packet, Node A creates the corresponding forwarding table.
Node A uses unicast face to send packet to Node B based on self-learned forwarding path .
Check that A successfully set up unicast face.
Check that only node B received the packet.


Related issues 1 (1 open0 closed)

Is duplicate of NFD - Task #5026: Self-learning: unit testingNew

Actions
Actions #1

Updated by Davide Pesavento almost 7 years ago

  • Category set to Integration Tests
  • Start date deleted (12/16/2017)

Are these unit tests or integration tests?

Actions #2

Updated by Junxiao Shi almost 7 years ago

  • Category changed from Integration Tests to Forwarding

The title has made clear that these are unit tests. They can be easily implemented with TopologyTester facility.

“Tests” category is solely for integ, so this belongs to “Forwarding” category.

Actions #3

Updated by Davide Pesavento almost 7 years ago

Then why do we need a separate task? Unit tests belong in the same task/patch that introduces the feature they're supposed to test.

Actions #4

Updated by Junxiao Shi almost 7 years ago

Unit tests belong in the same task/patch that introduces the feature they're supposed to test.

Not necessarily. A test may be developed before the feature and marked as “expected failure”, and the implementation commit can remove the expected failure annotation. Such practice exists in ndn-cxx but not yet in NFD.

A substantial test case like this may be assigned to a different developer, necessitating a separate task.

Actions #5

Updated by Davide Pesavento almost 7 years ago

  • Subject changed from Provide Unit Test for Broadcast-based Self-learning Forwarding Strategy to Unit tests for Self-learning Forwarding Strategy
  • Parent task set to #4279
Actions #6

Updated by Junxiao Shi about 6 years ago

  • Tags set to SelfLearning
Actions #7

Updated by Davide Pesavento about 6 years ago

  • Tags changed from SelfLearning to SelfLearning, UnitTests
Actions #8

Updated by Junxiao Shi almost 6 years ago

  • Status changed from New to Rejected
Actions #9

Updated by Davide Pesavento almost 6 years ago

  • Status changed from Rejected to Abandoned
Actions #10

Updated by Junxiao Shi about 5 years ago

  • Is duplicate of Task #5026: Self-learning: unit testing added
Actions #11

Updated by Davide Pesavento 12 months ago

  • Tags changed from SelfLearning, unit-tests to unit-tests, self-learning
Actions

Also available in: Atom PDF