mflux-manual-testing

Validates mflux CLI changes by running commands and reviewing generated images and artifacts.

2.4k|187|Updated Aug 10, 2024
One-click install
npx skills add https://github.com/mflux-community/mflux --skill mflux-manual-testing-mflux-community
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mflux-manual-testing
Source: https://github.com/mflux-community/mflux/tree/main/.cursor/skills/mflux-manual-testing
Command: npx skills add https://github.com/mflux-community/mflux --skill mflux-manual-testing-mflux-community

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Automated tests can pass while real CLI usage still breaks, especially for image generation, callbacks, and file IO. This Skill provides a change-driven manual testing checklist for the mflux repository so regressions in CLI entrypoints and image outputs are caught before merge. ## Core Features & Use Cases - Change-Driven CLI Checks: Run only the manual checks relevant to what changed on your branch, such as basic generation, model saving, low-RAM mode, stepwise outputs, and metadata sidecars. - Human-in-the-Loop Output Review: Point reviewers at final images, stepwise composites, and metadata JSON files for visual confirmation rather than pixel-perfect comparison. - diffusers Reference Comparison: Validate new MLX model ports against a sibling diffusers clone with matched prompts, seeds, steps, and precision settings. - Use Case: After modifying a CLI flag under src/mflux/models, reinstall the local tool with uv, run the affected generation command with a small step count, and visually confirm the output image is not noise. ## Quick Start Ask the AI to manually test the mflux CLI paths changed on the current branch and review the generated output images.

Frequently Asked Questions about mflux-manual-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manually test mflux CLI changes?▼

Identify what changed on your branch, reinstall the local tool with uv tool install --force --editable --reinstall ., then run only the relevant CLI checks with 1-2 seeds and a small step count like 4 for fast iteration.

How to compare mflux output with diffusers for a new model port?▼

Use a sibling diffusers clone since mflux does not install diffusers. Match prompt, width, height, seed, steps, and guidance, run both pipelines, and save comparison PNGs to explicit paths without committing them.

When should I run manual testing instead of relying on automated tests?▼

Run manual checks when you changed CLI entrypoints under src/mflux/models, touched callbacks like stepwise output or memory saver, or modified metadata and image saving, even if automated tests are green.

Why does my mflux output differ visually from the diffusers reference?▼

Visual differences do not necessarily mean the port is broken. Run the latent injection workflow from mflux-debugging to separate transformer and VAE quality issues from RNG or scheduler differences.

What should I check when testing stepwise image output in mflux?▼

Run with --stepwise-image-output-dir and confirm step images are written for each step, the final step image qualitatively matches the final output, and the composite image is created.