Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Story]: Add test coverage for kserve migration #1980

Closed
lucferbux opened this issue Oct 18, 2023 · 1 comment
Closed

[Story]: Add test coverage for kserve migration #1980

lucferbux opened this issue Oct 18, 2023 · 1 comment
Assignees
Labels
feature/model-serving Model Serving Feature kind/story A user story for larger work. Should always be referenced by a "tracker" labelled issue. migrated priority/high Important issue that needs to be resolved asap. Releases should not have too many of these.

Comments

@lucferbux
Copy link
Contributor

lucferbux commented Oct 18, 2023

Goal

Add jest to the backend and test the migration of kserve

Dependency issue

Itemized goals

  • Add Jest to the backend -> Update Already in main and the branch, no need to be done.
  • Add unit testing coverage

Aspects continued elsewhere

No response

Mocks

No mocks

@lucferbux lucferbux added priority/high Important issue that needs to be resolved asap. Releases should not have too many of these. kind/story A user story for larger work. Should always be referenced by a "tracker" labelled issue. feature/model-serving Model Serving Feature labels Oct 18, 2023
@lucferbux lucferbux self-assigned this Oct 18, 2023
@lucferbux lucferbux removed their assignment Nov 8, 2023
@dgutride
Copy link
Contributor

dgutride commented Dec 8, 2023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature/model-serving Model Serving Feature kind/story A user story for larger work. Should always be referenced by a "tracker" labelled issue. migrated priority/high Important issue that needs to be resolved asap. Releases should not have too many of these.
Projects
Status: Done
Archived in project
Status: No status
Development

No branches or pull requests

2 participants