The snippets, ordered obscure → unmistakable

  1. Snippet 1(Tiny helper)
  2. Snippet 2(Test API)
  3. Snippet 3(Mocks)
  4. Snippet 4(Snapshot serializer)
  5. Snippet 5(Runner internals)
  6. Snippet 6(package banner)

Why this project gives itself away

The give-away. Snippet 1 is generic. Snippet 2's describe/beforeEach/test/expect(...).toBe() matches the Jest globals exactly. Snippet 3's jest.mock(...) with module-factory replacement is Jest-only (Vitest mimics the shape but uses vi.mock). Snippet 4 is the React-element-aware snapshot serializer. Snippet 5 names TestScheduler.scheduleTests and the @jest/core dispatcher. Snippet 6 reveals the 🃏 + Meta Platforms banner.

How a Framed puzzle is built

Every Framed project ships exactly six snippets, hand-ordered from deeply obscure to unmistakable. The first snippet must be plausible for a dozen codebases — a generic loop, a small utility, a comment that could appear anywhere. The last snippet carries a project-specific tell: a function name, a code-comment idiom, a file header, a build invocation. Between them sit four snippets that gradually narrow the field. Reading them in order is half the puzzle: a returning Framed player learns to triangulate on indentation conventions, comment voice, naming, and the small-but-distinctive choices that betray a project's era and community.