E2E Tests for Harbor CLI

[amands98]

End-to-end tests are essential for ensuring the quality of Harbor CLI features

Implementation

1. We can use ginkgo + gomega

• adopting a Behavior-Driven Development (BDD) approach.
• proven effective in various CLI projects, such as kubectl.

2. Standard Go testing framework to test the functionality of a CLI tool.

Using Ginkgo and BDD for Harbor CLI tests can add complexity. Sticking with standard Go testing if the project is simple. But for complex projects, Ginkgo offers clearer tests, better collaboration.

Note: If you have alternative suggestions for constructing end-to-end tests for Harbor, please feel free to share your thoughts below.

// @OrlinVasilev @Vad1mo

[Vad1mo]

Not a bad idea.

[Vad1mo]

regarding ginko and BDD, I wonder if that is not too much added complexity for the project? and we should stikc what golang provides

[amands98]

Using Ginkgo and BDD for Harbor CLI tests can add complexity. Sticking with standard Go testing if the project is simple. But for complex projects, Ginkgo offers clearer tests, better collaboration.

[ Updated the Description ]

[bishal7679]

Specifically for harbor-cli it'd be better to stick with standard go test IMO which will also be helpful for codecov integration

[EshaanAgg]

Hi! Is this project open for external contributors? Not exactly E2E, but I had noticed that the credential store has no associated tests with it. I would love to try o add a test suite for the same.

[Vad1mo]

Hi! Is this project open for external contributors? Not exactly E2E, but I had noticed that the credential store has no associated tests with it. I would love to try o add a test suite for the same.

Sure go ahead!

[criticic]

I noticed there are no unit tests in this repo, can I go ahead and create a PR for the same?

[Vad1mo]

sure @criticic