NLSR

In NLSR, dispatcher can setInterestFilter for the remote router interests on dummy face without router prefix registration when I use addTopPrefix(topPrefix, false, m_signingInfo), so my unit test case for remote router retrieving dataset can pass successfully. But in reality nlsr doesn't register router name prefix.

Is there any way I can add in my unit test to check if the router prefix is registered successfully or not to avoid this error?

But in reality nlsr doesn't register router name prefix.

addTopPrefix invocation sets wantRegister=false so that the dispatcher does not register prefix. It must be changed to true.

Is there any way I can add in my unit test to check if the router prefix is registered successfully or not to avoid this error?

The test case needs to assert a prefix registration command was emitted.

NLSR should:

registerPrefix for:
/<router-name>/nlsr

set interest filter for:
/<router-name>/nlsr/INFO
/<router-name>/nlsr/KEY
/<router-name>/nlsr/lsdb/name
/<router-name>/nlsr/lsdb/coordinate
/<router-name>/nlsr/lsdb/adjacency
/<router-name>/nlsr/routing-table

NLSR is added because in the future /<router-name> might not be registered by NLSR.
Process ID will be added after NLSR component in #3277

For consistency, "/localhost/nlsr" should be changed to "/localhost/NLSR"
will keep this /localhost/nlsr otherwise change is required in NFD, will change NLSR above to nlsr
registerPrefix for:
/localhost/nlsr

set interest filter for:
/localhost/nlsr/lsdb/name
/localhost/nlsr/lsdb/coordinate
/localhost/nlsr/lsdb/adjacency
/localhost/nlsr/routing-table
/localhost/nlsr/prefix-update/advertise
/localhost/nlsr/prefix-update/withdraw
/localhost/nlsr/rib/register
/localhost/nlsr/rib/unregister

Need to update any affected wiki pages.