Test Case Candidates
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 20/100
- Tipo di issue
- Documentazione
- Chiarezza
- Da chiarire
- Stato di attività
- Ferma
- Stack tecnologico
- anaconda, linux, shell
- Ambito
- documentation, operating-systems, testing
Direzione di ricerca
Start by reviewing the candidate scenarios for Anaconda installation and migrate2rocky.sh, then determine how test case documents, release status, requirements cross-references, and naming hierarchy should be tracked. Done means the relevant test case documents have completed review and been merged, with the checklist status documented.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Here is a rough list of potential test case candidates we should be able to knock out pretty easily.
The vast majority of these have been successfully completed, we just haven't documented the process and/or defined how to track that status for each release candidate and/or full release.
Suggest more in this discussion issue by supplying your own lists in comment. I can copy/paste them into this list as they come in.
These would only be checked off as done where a Test Case document has been merged into the repository after completing review.
We'll want/need to create cross reference to a requirements document and implement proper test case naming hierarchy (this is in work). Once those two pieces are defined and we have documentation describing them we can turn this list into a document that will require PRs to update.
Anaconda
boot ISO
[ ] Successful install of minimal from boot ISO (network) with tier0
[ ] Successful install of minimal from boot ISO (network) with auto selected mirror
[ ] Successful install of server from boot ISO (network) with tier0
[ ] Successful install of server from boot ISO (network) with auto selected mirror
[ ] Successful install of graphical server from boot ISO (network) with tier0
[ ] Successful install of graphical server from boot ISO (network) with auto selected mirror
[ ] Successful install of workstation from boot ISO (network) with tier0
[ ] Successful install of workstation from boot ISO (network) with auto selected mirror
minimal ISO
[ ] Successful install of minimal from minimal ISO (no network)
DVD ISO
[ ] Successful install of minimal from DVD ISO (no network)
[ ] Successful install of server from DVD ISO (network) with tier0
[ ] Successful install of graphical server from DVD ISO (network) with tier0
[ ] Successful install of workstation from DVD ISO (network) with tier0
EPEL as extra repository
[ ] Successful install of workstation with XFCE from DVD ISO (network) with tier0 and extra repository (EPEL)
Alternate Language Installs
[ ] Successful install of minimal from DVD ISO (no network) in French
[ ] Successful install of minimal from DVD ISO (no network) in German
[ ] Successful install of minimal from DVD ISO (no network) in Spanish
migrate2rocky.sh
[ ] Successful migration of vagrant base box for each of centos/rhel/ol/alma
[ ] Successful migrate of vagrant base box with EPEL enabled
[ ] Successful blocked migration from Rocky
[ ] Successful blocked migration with extra repositories defined
[ ] Successful migration with EFI boot
[ ] Successful migration with BIOS boot
[ ] Successful migration with MBR
[ ] Successful migration with GPT
[ ] Successful migration with RAID
[ ] Successful migration with LVM on RAID
[ ] Successful migration with MULTI boot grub2 configuration
Applications
[ ] Successful install / test of TBD precompiled application
[ ] Successful build, install and test of TBD source
- Lingua principale
- HTML
- Stelle
- 22
- Fork
- 29
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di rocky-linux/testing
-
Risc-V testing boards for CodeDudeForse di nuovo libera @rlhennig l’ha presa 96 giorni fa e non c’è nessuna pull request aperta. Apertapriority: high
rocky-linux/testing#96 · 1 commento · 1 assegnatario ·
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 25/100
rocky-linux/testing#95 ·
-
Test R8 CA2023 ISOAperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 38/100
rocky-linux/testing#94 · 1 commento ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
rocky-linux/testing#93 ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
rocky-linux/testing#92 · 1 commento ·
Tutte le issue di rocky-linux/testing
Issue simili
-
area:breg criticality:p3 documentation triage:needs-implementation
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 86/100
registrystack/registry-stack#1713 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
posit-dev/ggsql#565 · 1 reazione ·
I maintainer di solito rispondono entro 1 giorno
-
documentation easy good first issue help wanted
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
lacs-project/sysknife#518 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
qgis/QGIS-Plugins-Website#459 ·
-
bot-found documentation priority: P3
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
madenvel/KalinkaPlayer#178 ·