firefly
firefly copied to clipboard
Separate or relabel HeapBin and ProcBin proptests in lumen_runtime
The strategies for heap binaries pre-date the ProcBin implementation, so they generate byte sequences that can be > 64 bytes, the cut-off for ProcBin and so the "heap binary" tests are actually testing HeapBin and ProcBin.
One of two things should happen:
- Separate out the strategies and have separate tests for heap and process binaries to isolate bugs to the
HeapBinandProcBin - Rename the heap binary strategies and tests to be "aligned binary" tests to match the
AlignedBinarytrait used forHeapBinandProcBin.