[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MirageOS-devel] Concerning testing network protocols



Hi,

> 1. Split all wire format de/serialization code out of each protocol
> into a distinct library. Link against this library in both
> `pcap-format` and `ocaml-<protocol>`. Unit test the protocol
> implementation separately (perhaps via property-based testing which
> might not require a separate implementation, perhaps relying on
> completely distinct implementations like `libpcap`).

In my opinion, that's the preferable way to go. It's sometime not very easy and 
practical to split the repository into pieces, but hopefully opam 1.2.1 let you 
add `opam` and `foo-format.opam` to host two opam packages in the same 
repository.

Best,
Thomas

> 2. Make `pcap-format` the only place all wire format parsing is done,
> then much as 1.
> 
> 3. Simply stop protocol unit tests depending on `pcap-format`, forcing
> them to express tests differently (perhaps as property-based tests
> that don't need a separate implementation of `parse`/`marshall`).
> 
> Thoughts?
> 
> -- 
> Richard Mortier
> richard.mortier@xxxxxxxxxxxx
> 
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.