cluster-api-provider-vsphere icon indicating copy to clipboard operation
cluster-api-provider-vsphere copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

Improving test coverage in pkg/util

Open geetikabatra opened this issue 3 years ago • 5 comments
trafficstars

/kind bug

This issue is to list out the files which are required to be tested in pkg/util

sigs.k8s.io/cluster-api-provider-vsphere/pkg/util/kubeclient.go:33:				NewKubeClient				0.0%
sigs.k8s.io/cluster-api-provider-vsphere/pkg/util/machines.go:40:				GetMachinesInCluster			0.0%
sigs.k8s.io/cluster-api-provider-vsphere/pkg/util/machines.go:65:				GetVSphereMachinesInCluster		0.0%
sigs.k8s.io/cluster-api-provider-vsphere/pkg/util/machines.go:88:				GetVSphereMachine			0.0%
sigs.k8s.io/cluster-api-provider-vsphere/pkg/util/machines.go:104:				GetVSphereClusterFromVSphereMachine	0.0%
sigs.k8s.io/cluster-api-provider-vsphere/pkg/util/machines.go:124:				GetMachinePreferredIPAddress		84.6%
sigs.k8s.io/cluster-api-provider-vsphere/pkg/util/machines.go:150:				IsControlPlaneMachine			0.0%
sigs.k8s.io/cluster-api-provider-vsphere/pkg/util/machines.go:157:				GetMachineMetadata			87.5%
sigs.k8s.io/cluster-api-provider-vsphere/pkg/util/machines.go:223:				GetOwnerVSphereMachine			0.0%
sigs.k8s.io/cluster-api-provider-vsphere/pkg/util/machines.go:236:				getVSphereMachineByName			0.0%
sigs.k8s.io/cluster-api-provider-vsphere/pkg/util/machines.go:263:				ConvertProviderIDToUUID			100.0%
sigs.k8s.io/cluster-api-provider-vsphere/pkg/util/machines.go:278:				ConvertUUIDToProviderID			100.0%
sigs.k8s.io/cluster-api-provider-vsphere/pkg/util/machines.go:291:				MachinesAsString			100.0%
sigs.k8s.io/cluster-api-provider-vsphere/pkg/util/networkutil.go:44:				GetNamespaceNetSnatIP			0.0%
sigs.k8s.io/cluster-api-provider-vsphere/pkg/util/networkutil.go:68:				GetNCPVersion				0.0%
sigs.k8s.io/cluster-api-provider-vsphere/pkg/util/networkutil.go:84:				NCPSupportFW				0.0%
sigs.k8s.io/cluster-api-provider-vsphere/pkg/util/supervisor.go:27:				IsSupervisorType			100.0%
sigs.k8s.io/cluster-api-provider-vsphere/pkg/util/testutil.go:49:				CreateCluster				0.0%
sigs.k8s.io/cluster-api-provider-vsphere/pkg/util/testutil.go:68:				CreateVSphereCluster			0.0%
sigs.k8s.io/cluster-api-provider-vsphere/pkg/util/testutil.go:80:				CreateMachine				0.0%
sigs.k8s.io/cluster-api-provider-vsphere/pkg/util/testutil.go:110:				CreateVSphereMachine			0.0%
sigs.k8s.io/cluster-api-provider-vsphere/pkg/util/testutil.go:131:				createScheme				0.0%
sigs.k8s.io/cluster-api-provider-vsphere/pkg/util/testutil.go:143:				CreateClusterContext			0.0%
sigs.k8s.io/cluster-api-provider-vsphere/pkg/util/testutil.go:167:				CreateMachineContext			0.0%
sigs.k8s.io/cluster-api-provider-vsphere/pkg/util/testutil.go:184:				GetBootstrapConfigMapName		0.0%

What steps did you take and what happened: [A clear and concise description of what the bug is.]

What did you expect to happen:

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]

Environment:

  • Cluster-api-provider-vsphere version:
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):

geetikabatra avatar Feb 08 '22 16:02 geetikabatra

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar May 09 '22 16:05 k8s-triage-robot

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot avatar Jun 08 '22 17:06 k8s-triage-robot

/remove-lifecycle rotten

ditsuke avatar Jun 09 '22 04:06 ditsuke

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Sep 07 '22 05:09 k8s-triage-robot

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot avatar Oct 07 '22 05:10 k8s-triage-robot

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Reopen this issue with /reopen
  • Mark this issue as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-triage-robot avatar Nov 06 '22 05:11 k8s-triage-robot

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Reopen this issue with /reopen
  • Mark this issue as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

k8s-ci-robot avatar Nov 06 '22 05:11 k8s-ci-robot