Skip to content
This repository has been archived by the owner on May 6, 2022. It is now read-only.

Meta: Improve test coverage for CI #521

Closed
15 tasks
simonleung8 opened this issue Mar 10, 2017 · 9 comments
Closed
15 tasks

Meta: Improve test coverage for CI #521

simonleung8 opened this issue Mar 10, 2017 · 9 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. meta testing
Milestone
1.0.0

Comments

@simonleung8
Copy link
Contributor

simonleung8 commented Mar 10, 2017 •
edited by arschles
Loading

Need to have adequate test coverage for our CI

Packages that need unit testing:

  • cmd/apiserver
  • cmd/controller-manager
  • pkg/apis
  • pkg/apiserver
  • pkg/brokerapi
  • pkg/controller
  • pkg/openapi
  • pkg/registry/servicecatalog/binding
  • pkg/registry/servicecatalog/broker
  • pkg/registry/servicecatalog/instance
  • pkg/registry/servicecatalog/rest
  • pkg/registry/servicecatalog/server
  • pkg/registry/servicecatalog/serviceclass
  • pkg/storage (Add unit tests for the TPR storage interface #700)
  • pkg/util
@arschles arschles added this to the 0.0.2 milestone Apr 3, 2017
@arschles arschles changed the title Improve test coverage for CI Meta: Improve test coverage for CI Apr 3, 2017
@arschles
Copy link
Contributor

arschles commented Apr 3, 2017

I've added this to 0.0.2, as testing is a large task for that milestone. This issue can and should be split apart, and may move into new milestones.

@arschles arschles mentioned this issue Apr 3, 2017
Closed
@pmorie pmorie modified the milestones: 0.0.3, 0.0.2 Apr 7, 2017
@pmorie
Copy link
Contributor

pmorie commented Apr 7, 2017

Moving to 0.0.3 because this is not complete.

@arschles arschles added the meta label Apr 13, 2017
@arschles
Copy link
Contributor

arschles commented Apr 13, 2017 •
edited
Loading

Moving this out of a milestone because it's a meta issue that will likely span multiple milestones

@arschles arschles removed this from the 0.0.3 milestone Apr 13, 2017
arschles pushed a commit to arschles/kubernetes-service-catalog that referenced this issue Apr 13, 2017
writing a test for TPR storage Create
81db7cb 
Ref kubernetes-retired#521,
as this makes progress toward that meta issue
@arschles arschles mentioned this issue Apr 13, 2017
Merged
arschles pushed a commit to arschles/kubernetes-service-catalog that referenced this issue Apr 17, 2017
writing a test for TPR storage Create
8cb8787 
Ref kubernetes-retired#521,
as this makes progress toward that meta issue
krancour pushed a commit to arschles/kubernetes-service-catalog that referenced this issue Apr 17, 2017
@krancour
writing a test for TPR storage Create
342a7e4 
Ref kubernetes-retired#521,
as this makes progress toward that meta issue
@duglin duglin added this to the 1.0.0 milestone Jul 9, 2017
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 21, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 21, 2019
@jberkhahn jberkhahn removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label May 23, 2019
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 21, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 20, 2019
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. meta testing
Projects
None yet
Milestone
1.0.0
Development

No branches or pull requests
7 participants
@arschles @pmorie @duglin @simonleung8 @jberkhahn @k8s-ci-robot @fejta-bot