Hacker News

Move tests to closed source repo

2026-02-264:345840github.com

Move the test suite out of the open source tldraw/tldraw repo and into the closed source repo. Context The tldraw monorepo currently contains ~327 test files across unit, integration, and e2e tests...

@steveruizok
@steveruizok

Move the test suite out of the open source tldraw/tldraw repo and into the closed source repo.

Context

The tldraw monorepo currently contains ~327 test files across unit, integration, and e2e tests:

  • packages/tldraw: ~148 unit/integration tests (shapes, tools, commands, UI)
  • packages/editor: ~41 unit/integration tests (geometry, managers, tools)
  • packages/store: ~27 unit tests (records, queries, migrations)
  • packages/utils: ~30 unit tests (array, cache, media, hashing)
  • packages/sync-core: ~20 unit/integration tests (room, storage, protocol)
  • packages/state: ~12 unit tests (atoms, computed, transactions)
  • packages/tlschema: ~9 unit tests (schema, migrations)
  • packages/validate: ~2 unit tests
  • packages/sync: ~2 unit tests
  • apps/examples/e2e: ~24 Playwright e2e tests
  • apps/dotcom/client/e2e: ~12 Playwright e2e tests

Scope

  • Move all vitest unit/integration tests
  • Move all Playwright e2e tests
  • Move test configuration (vitest configs, playwright configs, test setup files)
  • Move test utilities and helpers (e.g. TestEditor)
  • Ensure CI in the closed source repo runs the full test suite against the SDK packages
  • Remove test files from the open source repo
Reactions are currently unavailable

You can’t perform that action at this time.


Read the original article

nilsbunger

Karma: 2889
...
 @Hacker__News
@hacker._news

Comments

  • By alt187 2026-02-276:581 reply

    Whether this was a joke or a backtracking, or this dared waste your oh so precious time- You're missing the forest for the trees. There's extreme covert and even overt hostility between how people stand on AI's gluttonous usage of the commons.

    We're about to waltz into a deep period of tension between developers, and people who, empowered by multimillion dollars corporations, bravely violate developers' copyrights in the hopes of replacing their jobs, while bullying these same developers who dare express their discontent.

    This is not gonna end well.

    • By Antibabelic 2026-02-2710:41

      Developers never had "intellectual property". Under capitalism, only billion-dollar corporations do. So the problem with AI isn't that it violated some license. The real problems are that people are losing jobs, that the Internet and our community gets clogged up with more low-effort slop competing for our attention than ever before, and that the products we are all forced to use are becoming worse because corporations are trying to shove AI-features into them and put quotas on engineers to vibe-code as much as possible. There are definitely others. "Copyright" is not even scratching the surface of real problems with LLMs, and many of the people leading the charge in pointing out the evil and hypocrisy of AI companies are themselves copyright abolitionists.

  • By hellcow 2026-02-274:502 reply

    This is interesting because it’s also one of SQLite’s monetizations. SQLite is in the public domain, but you need a commercial license to access their TH3 test harness with 100% branch coverage used to validate SQLite on different platforms.

  • By latchkey 2026-02-274:051 reply

    Read the thread, it was a joke.

    "Sorry folks, this issue was more of a joke (am I allowed to do that?) but I'll keep the issue open since there's some discussion here."

HackerNews

About