Skip to content

test: add CLI integration tests for build command #25

@pavelanni

Description

@pavelanni

Summary

The internal/cli/ package has zero test files. The build command
now has two code paths (runBuild for local, runBuildRemote for
URLs) and neither is tested at the CLI layer.

What to test

  • Flag parsing: --ref, --filter, --tag, --media-type
  • URL detection routing (source.IsRemoterunBuildRemote)
  • --tag rejected when building multiple skills
  • Error output for missing git, bad URLs, etc.
  • Local build regression (cobra args, output format)

Context

Found during code review of #24. The backend packages
(pkg/source/, pkg/oci/) have good test coverage, but the CLI
wiring is only verified via manual end-to-end testing.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions