You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The mock network modules in lib_test/ounit/test_mdns_responder_mirage have a lot of boilerplate and stubbed-out code. Could they be replaced by the mirage-vnetif library, which is intended to provide in-memory network stacks for testing?
The text was updated successfully, but these errors were encountered:
Since #159 is merged, we don't have any test cases for the mirage- or lwt-specific backends (but extensive tests for the core suite). Leaving this open for a mirage-vnetif test suite for this library
when adding mirage-vnetif based tests, please investigate first what you like to test... the mirage layer is rather slim (mainly tcp connection management), most of the server and resolver logic can be tested in a pure fashion -- no need for vnetif :)
The mock network modules in
lib_test/ounit/test_mdns_responder_mirage
have a lot of boilerplate and stubbed-out code. Could they be replaced by the mirage-vnetif library, which is intended to provide in-memory network stacks for testing?The text was updated successfully, but these errors were encountered: