tom_d4rt_test

> Scaffolded test-harness package for the D4rt interpreter ecosystem. Currently a bare `dart create` skeleton — reserved for D4rt test-suite work but not yet populated.

`tom_d4rt_test` is a standalone Dart console package inside the [D4rt interpreter ecosystem](https://github.com/al-the-bear/tom_d4rt). Its declared purpose (in `tom_project.yaml`) is to host a **D4rt test suite**, but the source tree has not yet been filled in. This README documents exactly what is present today so there are no surprises.

Honest status

This package is, at the moment, an **empty scaffold**:

• `bin/tom_d4rt_test.dart` — empty (one blank line, no `main`).
• `lib/tom_d4rt_test.dart` — empty (one blank line, no exports).
• The only generated source is `lib/src/version.versioner.dart`, a

build-time version stamp produced by the workspace versioner tool. - The `pubspec.yaml` still carries the default `description: A sample command-line application.` from `dart create`. - The sole runtime dependency is `path`; the only dev dependencies are `lints` and `test`. - **There is currently no executable behavior, no public API, and no tests.** Running it produces nothing.

In other words: the project has been created and wired into the workspace (version stamping, build state, copilot guidelines), but the actual D4rt test-suite content is still to be written.

Where it sits in the D4rt ecosystem

The `tom_ai/d4rt/` directory holds the full D4rt interpreter ecosystem. The packages relevant to this one are:

Package	Role
[`tom_d4rt`](../tom_d4rt)	The D4rt interpreter and runtime — a Dart interpreter with bridging, security sandboxing, and dynamic code execution (analyzer-backed).
[`tom_d4rt_ast`](../tom_d4rt_ast)	Serializable AST model for Dart code interpretation **without** an analyzer dependency.
[`tom_d4rt_exec`](../tom_d4rt_exec)	Analyzer-free D4rt interpreter running on the mirror AST from `tom_d4rt_ast`; the migration target from `tom_d4rt` for Flutter/server use.
**`tom_d4rt_test`**	**(this package)** Intended D4rt test suite. Scaffold only at present.

When populated, this package is expected to exercise one or more of the interpreters above. As it stands, it does **not** yet depend on any of them — the dependency wiring will be added when the test suite is implemented.

What it actually contains

tom_d4rt_test/
├── bin/
│   └── tom_d4rt_test.dart          # empty — no entrypoint yet
├── lib/
│   ├── tom_d4rt_test.dart          # empty — no public API yet
│   └── src/
│       └── version.versioner.dart  # GENERATED build-time version info
├── _copilot_guidelines/
│   └── index.md                    # links to applicable workspace guidelines
├── analysis_options.yaml           # package:lints/recommended
├── pubspec.yaml                    # path dep + lints/test dev deps
├── pubspec.lock
├── tom_project.yaml                # project_id: D4T, name: d4-test
├── tom_build_state.json            # workspace build counter
└── LICENSE                         # BSD 3-Clause

`lib/src/version.versioner.dart`

The one non-empty source file. It is a generated, do-not-edit file exposing a `TomVersionInfo` class with build metadata (`version`, `buildTime`, `gitCommit`, `buildNumber`, `dartSdkVersion`) and convenience getters (`versionShort`, `versionMedium`, `versionLong`). It is regenerated by the workspace versioner on each build and is not imported anywhere yet.

`tom_project.yaml`

project_id: D4T
name: d4-test
description: >-
  D4rt test suite.

This is the stated intent for the package within the Tom workspace.

How to run it

There is nothing to run yet. The commands below are the standard package commands and are listed for when content is added.

# Resolve dependencies
dart pub get

# Static analysis (passes — there is no code to flag)
dart analyze

# Run the (currently empty) console entrypoint
dart run                       # or: dart run bin/tom_d4rt_test.dart

# Run tests (none exist yet)
dart test

> Note: `dart run` on the current empty `bin/tom_d4rt_test.dart` will not > execute any logic because the file has no `main`.

Dependencies

From `pubspec.yaml`:

• **Runtime:** `path: ^1.9.0`
• **Dev:** `lints: ^6.0.0`, `test: ^1.25.6`
• **SDK:** `^3.10.4`

`publish_to` is **not** set to `none`, so the package is technically configured as publishable, though the local copilot guidelines note it is "published to pub.dev"; in practice there is nothing meaningful to publish until the suite is implemented.

License

BSD 3-Clause License — Copyright (c) 2024-2026, Peter Nicolai Alexis Kyaw. See [`LICENSE`](LICENSE).

Related packages

• [`tom_d4rt`](../tom_d4rt) — D4rt interpreter and runtime
• [`tom_d4rt_ast`](../tom_d4rt_ast) — serializable analyzer-free AST model
• [`tom_d4rt_exec`](../tom_d4rt_exec) — analyzer-free interpreter on the mirror AST
• D4rt ecosystem repository: <https://github.com/al-the-bear/tom_d4rt>