Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Test Case Candidates

Open
  • Is something wrong?
#56 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
anaconda, linux, shell
Domain
documentation, operating-systems, testing

Research direction

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.

Written by the indexing model from the issue text.

Description

type: discussion

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

Dominant language
HTML
Stars
22
Forks
29
No merged PRs in 30d

Getting set up

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.

More from rocky-linux/testing

All issues in rocky-linux/testing

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.