Packages and tests

Desktop can restore project dependencies, discover tests, and show test results beside the source you are editing.

Keep the project manifest and lock state with the source so Desktop, CLI, CI, and remote workers use the same dependency versions.

Restore packages

Open Packages to review dependencies declared by the project and restore missing versions. Restore dependencies after cloning or opening a project and whenever the manifest or lock state changes.

Packages can come from the RunMat registry or an allowed local source. Review a package's source and version before adding it. Keep credentials, private datasets, .env files, and generated run artifacts out of package contents.

See Packages for dependency declarations, local sources, and the registry workflow.

Run tests

Open Tests to see the tests discovered in the current project. You can run:

one test while working on a specific behavior;
one test file after changing a related function;
the full project suite before review or release.

Select a failed test to open its diagnostic and source location. Test runs also appear with other runs, so their output and available workspace values can be inspected in the Runtime area.

This example checks that a function returns nonnegative, normalized weights:

function test_normalized_weights()
    w = build_weights([1, 2, 3, 4]);
    assert(all(w >= 0));
    assert(abs(sum(w) - 1) < 1e-12);
end

Keep fixtures small and deterministic. Seed random inputs and compare floating-point values with tolerances appropriate to the calculation.

Match continuous integration

Before pushing a change:

save all source files;
restore the locked dependencies;
run the affected tests;
run the full suite from a clean workspace;
record any required datasets or hardware.

When Desktop and CI disagree, compare the Runtime version, operating system, dependency lock state, environment variables, and execution target. See Packages in CI for automated setup.

Restore packages

Open Packages to review dependencies declared by the project and restore missing versions. Restore dependencies after cloning or opening a project and whenever the manifest or lock state changes.

See Packages for dependency declarations, local sources, and the registry workflow.

Run tests

Open Tests to see the tests discovered in the current project. You can run:

one test while working on a specific behavior;

one test file after changing a related function;

the full project suite before review or release.

Select a failed test to open its diagnostic and source location. Test runs also appear with other runs, so their output and available workspace values can be inspected in the Runtime area.

This example checks that a function returns nonnegative, normalized weights:

function test_normalized_weights()
    w = build_weights([1, 2, 3, 4]);
    assert(all(w >= 0));
    assert(abs(sum(w) - 1) < 1e-12);
end

Keep fixtures small and deterministic. Seed random inputs and compare floating-point values with tolerances appropriate to the calculation.

Match continuous integration

Before pushing a change:

save all source files;

restore the locked dependencies;

run the affected tests;

run the full suite from a clean workspace;

record any required datasets or hardware.

When Desktop and CI disagree, compare the Runtime version, operating system, dependency lock state, environment variables, and execution target. See Packages in CI for automated setup.