[Discussion] We should add a test suite

[milindsrivastava1997]

We should have tests for atleast serialization/deserialization, correctness of sketch insertion/estimation/merging logic.

datasketches has a test suite and we understand what they do and emulate it here.

Apart from reducing possible bugs, having these tests will also allow us to explore optimizations more aggressively, as we have to worry less about introducing bugs.

cc @GordonYuanyc @zzylol

[milindsrivastava1997]

Maybe a first step to do is to write down high-level properties that we want to test for, both things that we come up with and things that datasketches has.

[GordonYuanyc]

I think we can have a table in the readme about what we have.
The readme will tell people what we have, how to use (small demo), what we guarantee (test we have), and direct people to detailed API documentation. Comparison to datasketches can be somewhere inside doc directory.
I'll add the table when I work at #22 and we can have a discussion after that.

[milindsrivastava1997]

I think you misunderstood. I'm not talking about features or performance comparison with datasketches. I am talking about a set of unit and integration tests for your library. The reason I mention datasketches is because they have a test suite and we should understand what they are testing in the code.