Task #2162
closed
Forwarder persistent loop test case: use UnitTestClock
100%
Description
Modify FwForwarder/Bug1953 test case to use UnitTestClock, and C++11 features such as lambda expression.
Rename it to InterestLoopWithShortLifetime.
Updated by Junxiao Shi about 10 years ago
- Status changed from New to In Progress
As part of this Task, I'll make a UnitTestClockFixture to be shared between test suites.
Updated by Junxiao Shi about 10 years ago
- Status changed from In Progress to Code review
- % Done changed from 0 to 100
Updated by Junxiao Shi about 10 years ago
- Status changed from Code review to In Progress
- % Done changed from 100 to 40
- Estimated time changed from 0.50 h to 1.50 h
There's a design problem of how io_service could be called when clock is mocked.
I'll work on this after I have sufficient understanding of the problem addressed in http://gerrit.named-data.net/1441
Updated by Junxiao Shi almost 10 years ago
The fixture has appeared in ndn-cxx d3a55b29ece1df247ec7fc01771332ebd678cb2f.
I'm requesting approval of importing this code http://www.lists.cs.ucla.edu/pipermail/nfd-dev/2014-November/000623.html
Updated by Junxiao Shi almost 10 years ago
Importing UnitTestTimeFixture from ndn-cxx has been approved http://www.lists.cs.ucla.edu/pipermail/nfd-dev/2014-November/000626.html.
Work on this Task is now resumed.
There is a suggestion of letting LimitedIo recognize mocked clocks.
However, this isn't necessary for this test case, so I'll do that in another Task if that test case needs this.
Updated by Junxiao Shi almost 10 years ago
- Status changed from In Progress to Code review
- % Done changed from 40 to 100
Updated by Junxiao Shi almost 10 years ago
- Status changed from Code review to Closed