bug: start starts all #5

Open
opened 2026-07-14 06:32:43 +00:00 by warkanum · 1 comment
Owner

start command starts all instead of starting unit by name. That is what startall command is for. The start command must take a required name.
Also check stop to not do what stopall does.

start command starts all instead of starting unit by name. That is what startall command is for. The start command must take a required name. Also check stop to not do what stopall does.
Member

PR: #6 issue-5 regression tests for start/stop/startall/stopall CLI semantics

Branch: issue-5-targeted-start-stop
Commit SHA: 5026ae4
PR URL: #6

Verification (make test): all packages pass.

What was done

  1. cmd/start_test.go - regression tests for start <name> arg-count enforcement
  2. systemd/start_stop_test.go - regression tests covering buildExecCommands, sort order asc/desc with tiebreakers, skip disabled/uninstalled units

Caveats

  • Unit-level only; no integration test for systemctl calls (requires real systemd env).
  • Existing generator/manager tests cover the actual lifecycle paths.
## PR: #6 issue-5 regression tests for start/stop/startall/stopall CLI semantics **Branch:** `issue-5-targeted-start-stop` **Commit SHA:** `5026ae4` **PR URL:** https://git.warky.dev/wdevs/unitdore/pulls/6 ## Verification (make test): all packages pass. ### What was done 1. `cmd/start_test.go` - regression tests for `start <name>` arg-count enforcement 2. `systemd/start_stop_test.go` - regression tests covering buildExecCommands, sort order asc/desc with tiebreakers, skip disabled/uninstalled units ## Caveats - Unit-level only; no integration test for systemctl calls (requires real systemd env). - Existing generator/manager tests cover the actual lifecycle paths.
Sign in to join this conversation.