I have something like this:public byte[] EncodeMyObject(MyObject obj)I've been unit testing like this:byte[] expectedResults = new byte[3]{ 0x01, 0x02, 0xFF };Assert.IsEqual(expectedResults, EncodeMyObject(myObject));EDIT: The two ways I've seen proposed are:1) Using hardcoded expected values, like the above example.2) Using a decoder to decode the encoded byte array and comparing the input/output objects.The problem I see with method 1 is that it is very brittle and requires a lot of hard coded values.The problem with method 2 is that testing the encoder depends on the decoder working correctly. If the encoder/decoder are broken equally (in the same place), then the tests could produce false positives.These may very well be the only ways to test this type of method. If that's the case then fine. I'm asking the question to see if there are any better strategies for this type of testing. I can not reveal the internals of the particular encoder I am working on. I am asking in general how you would solve this type of problem, and I don't feel the internals are important. Assume that a given input object will always produce the same output byte array.
How do you unit test an encoder?
unit testing
You're in a bit of an obnoxious situation there. If you had a static format you were encoding into, your first method would be the way to go. If it were just your own format, and nobody else had to decode than the second method would be the way to go. But you don't really fit into either of those categories.What I'd do is try to break things down by the level of abstraction. So I'd start with something at the bit level, that I'd test something likebitWriter = new BitWriter();bitWriter.writeInt(42, bits = 7);assertEqual( bitWriter.data(), {0x42} )So the idea is that the bitwriter knows how to write out the most primitive types of fields, like ints. More complex types would be implemented using and tested something like:bitWriter = new BitWriter();writeDate(bitWriter, new Datetime(2001, 10, 4));bitWriter2 = new BitWriter();bitWriter2.writeInt(2001, 12)bitWriter2.writeInt(10, 4)bitWriter2.writeInt(4, 6)assertEquals(bitWriter.data(), bitWriter2.data() )Notice that this avoids any knowledge of how the actual bits get packed. That's tested by the previous test, and for this test we'll pretty much just assume that it works. Then at the next level of abstraction we'd havebitWriter = new BitWriter();encodeObject(bitWriter, myObject);bitWriter2 = new BitWriter();bitWriter2.writeInt(42, 32)writeDate(bitWriter2, new Datetime(2001, 10, 4));writeVarString(bitWriter2, alphanumeric);assertEquals(bitWriter.data(), bitWriter2.data() )so, again, we don't try to include the knowledge of how varstrings or dates or numbers are actually encoded. In this test, we are only interested in the encoding produces by encodeObject.The end result is that if the format for dates is changed, you'll have to fix the tests that actually involve dates, but all other code and tests aren't concerned with how dates are actually encoded and once you update the code to make that work, all those tests will pass just fine.