release icon indicating copy to clipboard operation
release copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes

Tests for `krel obs` implementation

Open xmudrii opened this issue 2 years ago • 13 comments

We skipped writing tests while working on a proof-of-concept because it was uncertain if that's going to be the final implementation. Now that we have the final implementation, we should ensure krel obs is properly tested before putting OBS in the production.

Tasks:

  • [ ] Unit, integration, and e2e tests for krel obs specs
  • [ ] rpmlint tests for specs (#3166)
  • [ ] At least unit tests for krel obs stage
  • [ ] At least unit tests for krel obs release

krel obs stage and krel obs release should have a similar set of tests as krel stage and krel release respectively.

/priority critical-urgent /sig release /area release-eng /kind feature

xmudrii avatar Jul 24 '23 19:07 xmudrii

/unassign If anyone else wants to pick this up while I'm on PTO

xmudrii avatar Aug 04 '23 11:08 xmudrii

I'd like to work on this issue!

nitishfy avatar Sep 12 '23 17:09 nitishfy

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

This bot triages un-triaged 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:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue 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 Jan 28 '24 05:01 k8s-triage-robot

/remove-lifecycle stale

xmudrii avatar Jan 28 '24 20:01 xmudrii

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

This bot triages un-triaged 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:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue 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 Apr 27 '24 20:04 k8s-triage-robot

/remove-lifecycle stale

xmudrii avatar May 20 '24 14:05 xmudrii

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

This bot triages un-triaged 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:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue 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 Aug 18 '24 15:08 k8s-triage-robot

/remove-lifecycle stale

xmudrii avatar Aug 19 '24 10:08 xmudrii