According to a recent LinkedIn post from Earthmover, the company’s engineering team has completed a three-part deep-dive series detailing how it tests Icechunk, its data-handling technology. The post focuses on ensuring that Icechunk 2.x can operate alongside 1.x on the same repositories without causing data corruption for existing users.
The LinkedIn post highlights a “cross-version stateful testing” strategy that runs Icechunk 1.x and 2.x simultaneously within a single Python process, using the Hypothesis library to randomly interleave calls across both versions. Failures are automatically minimized to reproducible cases, and Icechunk 1.x itself is used as the reference model for garbage-collection behavior.
As shared in the post, a supporting tool called “third-wheel” enables separate imports of both versions in the same environment, which appears to facilitate this parallel testing regime. The post also notes that, according to the team, there have so far been no reported issues with compatibility between the 1.x and 2.x versions.
For investors, the emphasis on rigorous backward-compatibility testing suggests Earthmover is prioritizing reliability for existing users while evolving its core technology. If sustained, this approach could reduce migration risk, support customer retention, and enhance the company’s reputation in data infrastructure markets where stability and correctness are critical purchasing criteria.
More broadly, the engineering practices described may signal a mature development culture capable of handling complex version transitions, which can be a key risk factor for infrastructure software vendors. Effective management of such transitions can lower support costs and build trust with enterprise customers, potentially improving Earthmover’s competitive position and long-term revenue prospects.