binbashar / leverage / 35021423738

65%

master: 65%

push

github

Fix | Restore the integration tests (#323)

* Fix | Restore the integration tests

Fix `leverage project create`:

  The root command builds the project paths for every invocation, which
  requires an already configured project. `project init` creates the git
  repository, so from that point on the configuration loads fine but still
  holds no project name, and `project create` aborts with "Project name has
  not been set" on what is its normal, intended use. The command that creates
  a project could not run on a project that did not exist yet.

  Before #316 the root command only loaded the config to check the toolbox
  version, and returned early when it was absent, with a comment noting that
  the config does not exist yet at some points of the project. That guard was
  lost when the paths were introduced. The project commands now skip the paths
  setup, which they never use. A unit test covers the regression.

Run the bats tests on the runner, and drop the testing image:

  The image existed to run the cli inside a container. Since #316 the cli runs
  the binaries on the host, and the image was never given terraform or tofu, so
  `leverage terraform version` had been failing on every run since December
  2025. What was left of the image was a Linux box with python, bats and
  leverage in it, which is what the runner already is, and which the unit test
  workflow already relies on.

  Dropping it also removes a dind base that no longer had a purpose, the
  `--privileged` flag and the dockerd entrypoint it needed, and a bind mount
  that had no effect since the image ran out of the copy made at build time.

  The no-git test used to `apk del git`, tying it to the image and to the file
  ordering of the suite. It now runs the cli with a PATH holding nothing but
  its own entry point, which `shutil.which` resolves the same way, without
  touching the system.

  Two portability fixes let the suite run on macOS as well: an explicit mktemp
  template, s... (continued)

514 of 1024 branches covered (50.2%)

Branch coverage included in aggregate %.

2 of 2 new or added lines in 1 file covered. (100.0%)

2778 of 4014 relevant lines covered (69.21%)

0.69 hits per line