microsoft / microsoft/ltp-platform

V1.4.0 Test Plan

Open
#124 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
11
Forks
5
Avg merge
3m
Merged PRs (30d)
1

Description

Test Cases

  1. Platform Features & Stability @yukirora @hippogr
  • Blobfuse2 installation failure (#94 )
  • Fix deployment on arm64 architecture (#109 )
  • Alert manager deployment bugfix (#106 )
  • add image regex to support valid image limitation (#107 )
  • Add webportal plugin for cluster local storage (#69 )
  • Add tolerance and priority class in cluster-local-storage (#119 )
  • Create postgresql backend and support backend switch with kusto (#117)
  1. Inference @hippogr @abuccts
  • Inference plugin support model proxy (#101 )
  • Support training/inference job type in restserver (#105 )
  • Support training/inference job type in webportal (#113 )
  • New Inference Job template implementation in model proxy (#118 )
  1. CI/CD @zhogu
  • CI/CD to build all service image (#102, #120 )
  • enable imagelist argument for image build script (#95 )
  • fix copy error of building image(#97)
  1. Security @zhogu
  • Upgrade Dockerfile with system update (#96)
  • Credentials in source code PR (#108,#99 )
  • Cilium update(#56)
  1. User Experience @zhogu
  • Slow portal response (#104)
  • Add user manual doc (#111 )
  • Improve copilot test experience (#100 )

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

This is a release checklist rather than a single-file change; start by reviewing the referenced issues, from #94 through #120, and identify the expected verification for each platform, inference, CI/CD, security, and user-experience item. Done means the V1.4.0 test cases have been executed and the checklist accurately records their status.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, dockerfile, postgresql, python
Domain
devops, release, security, testing-qa
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.