Skip to content

tests/nim: split NIM e2e tests into a dedicated suite - #1212

Open
eriknordmark wants to merge 1 commit into
lf-edge:masterfrom
eriknordmark:nim-suite-split
Open

tests/nim: split NIM e2e tests into a dedicated suite#1212
eriknordmark wants to merge 1 commit into
lf-edge:masterfrom
eriknordmark:nim-suite-split

Conversation

@eriknordmark

@eriknordmark eriknordmark commented Jul 11, 2026

Copy link
Copy Markdown
Contributor

Draft / WIP.

Splits the NIM end-to-end tests into a dedicated tests/nim/ suite:
moves the nine nim_*.txt testdata scripts out of
tests/network/testdata/ into tests/nim/testdata/, with a matching
Makefile, eden-config.yml, and eden.nim.tests.txt, so NIM-focused
coverage is reported independently of the broader network suite. The
escript runner handles them as TestEdenScripts/<name>, mirroring the
nodeagent and baseosmgr suites.

The LPS and radio-silence NIM tests under tests/eclient/testdata/
stay in the eclient suite — they depend on the eclient app and
local-manager harness, so they are NIM tests by exercise but not by
runtime dependency.

Carves the nim_*.txt testdata files out of tests/network/ into a
new tests/nim/ suite so coverage attributable to the NIM-focused
tests is reported independently of the broader network suite.

The suite mirrors the nodeagent and baseosmgr templates: a Makefile,
eden-config.yml pointing at the test scenario, and
eden.nim.tests.txt listing the nine moved scripts. The escript
runner (eden.escript.test) handles them as TestEdenScripts/<name>
without needing a per-suite Go entrypoint, matching how nodeagent
and baseosmgr run.

The LPS and radio-silence NIM tests under tests/eclient/testdata/
stay in the eclient suite because they depend on the eclient app
and local-manager harness; they are NIM tests by exercise but not by
runtime dependency.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Signed-off-by: eriknordmark <erik@zededa.com>
@eriknordmark
eriknordmark marked this pull request as ready for review July 20, 2026 23:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant