Increasing coverage and simplifying coverage report creation.

[David Adams (davidadas)]

This has no breaking changes or customer facing features.

Checklist

• I have successfully built and used a custom CLI binary, without linter issues from this PR.
• I have clearly specified in the What section below whether this PR applies to Confluent Cloud, Confluent Platform, or both.
• I have verified this PR in Confluent Cloud pre-prod or production environment, if applicable.
• I have verified this PR in Confluent Platform on-premises environment, if applicable.
• I have attached manual CLI verification results or screenshots in the Test & Review section below.
• I have added appropriate CLI integration or unit tests for any new or updated commands and functionality.
• I confirm that this PR introduces no breaking changes or backward compatibility issues.
• I have indicated the potential customer impact if something goes wrong in the Blast Radius section below.
• I have put checkmarks below confirming that the feature associated with this PR is enabled in:
  • Confluent Cloud prod
  • Confluent Cloud stag
  • Confluent Platform
  • Check this box if the feature is enabled for certain organizations only

What

• Increased coverage of various unit and integration tests.
• Set gotestsum runs both in the Semaphore pipeline and locally.
• Amended the .gitignore to include other coverage artifacts.

Blast Radius

The blast radius here is nil. At worst, it will cause unit or integ tests to fail or for the coverage to run improperly.

References

N/A

Test & Review

It is tests, so it has indeed been tested.

[confluent-cla-assistant]

🎉 All Contributor License Agreements have been signed. Ready to merge.
✅ davidadas
_{Please push an empty commit if you would like to re-run the checks to verify CLA status for all contributors.}

[Copilot]

Pull Request Overview

This PR aims to increase unit and integration test coverage while simplifying the creation of coverage reports. Key changes include:

• Adding new test cases for Flink CLI error scenarios (empty cloud provider and empty region).
• Updating golden files for error output messages.
• Enhancing tests for login commands and BYOK functionality.
• Modifying the Makefile to improve test execution and coverage data merging.

Reviewed Changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
test/flink_test.go	New tests for detecting empty cloud provider and region scenarios
test/fixtures/output/flink/region/unset-region.golden	Added golden file for region unset command
test/fixtures/output/flink/endpoint/*	New golden files for handling missing cloud provider, region, or empty args
internal/login/command_test.go	Added test for suspended organization error handling
internal/byok/command_create_test.go	Expanded table-driven testing for GCP metadata and BYOK policy command generation
Makefile	Updated targets for unit, integration tests, and coverage data merging

Comments suppressed due to low confidence (1)

test/flink_test.go:609

• The fixture name specified in TestFlinkEmptyRegion ('flink/region/unset.golden') does not match the actual golden file name ('unset-region.golden'). Please update the fixture name in the test or rename the golden file for consistency.

{args: "flink region unset", fixture: "flink/region/unset.golden", exitCode: 0}

[Steven Gagniere (sgagniere)]

We'll want to put this above line 15 because everything below that is managed by automation, which will probably revert this.

[Steven Gagniere (sgagniere)]

This file looks unused; can we remove it?

[Steven Gagniere (sgagniere)]

This file also looks unused.