Record a Reproducible Mod Test

A useful test record states exactly what ran, what the tester did and what happened. This page is a protocol, not a completed game test. Published reports and their evidence appear on the maintenance page.

Record the environment before installing

Use a clean test save, retain a backup and record the operating system, store, exact game patch, CPU, GPU and RAM. Note whether the game launches before adding mods. Keep an installed-file list and the original archives so each change can be reversed.

Record the exact version and original release link for every installed mod and prerequisite. A link to a project's latest download page does not establish which files were tested. If you cannot identify an installed version, the record is incomplete.

CET overlay test

1. Confirm the selected CET and RED4ext releases support the same game patch using their own release notes.
2. Install the documented prerequisites and record the exact installed releases.
3. Launch the game, assign the CET overlay key and open the overlay.
4. Record whether the expected interface appears. Save an identifiable screenshot or relevant log excerpt.
5. Restart the game and repeat the overlay check. Record both the restart action and observed outcome.

Do not infer that every CET-based mod works because the overlay opens. This case establishes only the actions recorded.

Minimal wardrobe test

1. Establish patch support for the chosen Equipment-EX release and every prerequisite first. An old README naming another patch does not settle this question.
2. Begin with vanilla clothing and no optional shop or custom clothing pack.
3. Open the wardrobe interface; record the visible result and evidence.
4. Save a small outfit, close and reopen the interface, then apply it again. Record each observed result.
5. Reload the test save and reapply the outfit. Record whether the saved outfit remains available and renders as expected.

The Equipment-EX source review documents unresolved patch evidence. Its dependency table is not a recommendation to combine all those releases for a game test.

Distinguish expected and observed results

Each check needs an action, expected result, observed result, explicit pass or fail, and a screenshot, video or log excerpt. A failed check is useful evidence and should remain visible. Do not fill observations from the expected-result text or mark unexecuted steps as passed.

Publish a report

Download the blank wardrobe report template. All null fields are deliberately unfilled. Add every installed prerequisite, complete the environment and replace each observation with what the tester actually saw.

Before publishing screenshots or logs, remove account identifiers and personal paths. Keep enough game context and version evidence to understand the check. A successful test is limited to that recorded environment and release combination; it does not certify unrelated mods or future patches.

CyberpunkMods publishes only records with complete fields and evidence files. The blank template cannot pass the publication validator. Source reviews and completed game tests remain separate on the maintenance page.