mflux-manual-testing

To manually test CLI changes in mflux, run guided scenarios for basic generation, model saving, and disk-based runs using local uv tooling, then review the produced images and artifacts to validate the output.

Manual CLI validation for mflux models is a change-driven checklist that exercises entrypoints under src/mflux/models/**/cli/ and related callbacks to verify generated outputs without automated checks.

Yes, you need uv tooling to validate mflux generation commands, specifically by running uv tool install --force --editable --reinstall . to set up local executables before testing.

A manual testing strategy for mflux image saving workflows involves executing disk-based runs and model save paths, then visually reviewing generated images and artifacts to confirm correct behavior.

Yes, you can verify mflux CLI callbacks without automated testing by manually running basic generation and disk-based scenarios, then reviewing produced metadata and image artifacts.

Use a manual test checklist for mflux CLI entrypoints when changes target src/mflux/models/**/cli/ paths and you need to validate basic generation, model saving, and disk runs without automated verification.