Usability issue
src/pie-interpreter/__tests__/tests.ts contains four it("") calls with empty description strings. When any of these fail, Jest reports a blank test name in its output, making it impossible to identify which case broke without manually reading through the file.
Context
Encountered when investigating a test failure in CI. The Jest output showed a failing test with no name, requiring manual inspection of the test file to locate the failing case. This slows down debugging significantly.
Suggested improvement
Give each anonymous test case a descriptive name reflecting what it is testing (e.g., "checks identity function synthesizes Pi type"). All it() calls should have non-empty descriptions.
Usability issue
src/pie-interpreter/__tests__/tests.tscontains fourit("")calls with empty description strings. When any of these fail, Jest reports a blank test name in its output, making it impossible to identify which case broke without manually reading through the file.Context
Encountered when investigating a test failure in CI. The Jest output showed a failing test with no name, requiring manual inspection of the test file to locate the failing case. This slows down debugging significantly.
Suggested improvement
Give each anonymous test case a descriptive name reflecting what it is testing (e.g., "checks identity function synthesizes Pi type"). All it() calls should have non-empty descriptions.