Skip to content
This repository has been archived by the owner on Oct 10, 2023. It is now read-only.

CLI test coverage requirements #29

Open
iancoffey opened this issue Jul 6, 2021 · 0 comments
Open

CLI test coverage requirements #29

iancoffey opened this issue Jul 6, 2021 · 0 comments
Assignees
@vuil
Labels
area/cli area/core-cli area/testing kind/enhancement Categorizes issue or PR as related to an enhancement migration/essential migration/imported priority/critical-urgent
Milestone
2021-December

Comments

@iancoffey
Copy link
Contributor

Define requirements for CLI test coverage and how do we enforce that?

This goes into how we test Tanzu as a whole. Do we use the SDK tests? should the SDK tests be exported and also executable from the CLI? What is the coverage amount expected?

Collated Context

Context from 2021-03-02 18:36:42
User: pbarker
We should engage the test team on this
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Assignees

@vuil vuil

Labels
area/cli area/core-cli area/testing kind/enhancement Categorizes issue or PR as related to an enhancement migration/essential migration/imported priority/critical-urgent
Projects
None yet
Milestone
2021-December
Development

No branches or pull requests
3 participants
@iancoffey @vuil @saji-pivotal