LorenEteval_Furious/tests/README.md

Furious test suite

The suite uses Python's built-in unittest runner. Qt tests select the offscreen platform before importing PySide6, construct one deliberately small test QApplication, and route QSettings to a unique temporary directory. They do not initialize Furious's singleton IPC server, production repositories, system proxy, TUN, routing, update network clients, or real proxy cores.

Coverage map

Area	Principal tests
Configuration, profiles, migration, repositories	test_models_and_services.py
Plugin registration, capability dispatch, factories, rollback	test_plugin_architecture.py
Controller state and error transitions with injected runtimes	test_controllers.py
SOCKS URI codec and import boundaries	test_socks_uri.py
External process launch, output, shutdown, threads, TUN metadata	test_external_core.py
Editor mappings, lazy log rendering, routing/message-box behavior	test_ui_behavior.py
Direct Qt ownership and destruction across independent UI families	test_qt_lifetime.py
Batched Qt object, Python allocation, and RSS trends	test_qt_stress.py

The lifecycle tests classify AppQTransientDialog, protocol/plugin editors, routing dialogs, subscription editors, message boxes, QR windows, and TUN settings dialogs as transient. TextEditorWindow is intentionally reusable: it must survive normal close/show cycles without multiplying actions, and is then explicitly destroyed by its owner. Main pages/controllers are application lifetime objects and are tested through isolated service/UI boundaries rather than by starting the production application runtime.

Commands

From the repository root on Windows PowerShell:

$env:QT_QPA_PLATFORM = 'offscreen'

# Everything
.\.venv-python313\Scripts\python.exe -m unittest discover -s tests -v

# Fast logic, persistence, plugin, controller, process, codec, and UI behavior
.\.venv-python313\Scripts\python.exe -m unittest `
    tests.test_models_and_services `
    tests.test_plugin_architecture `
    tests.test_controllers `
    tests.test_external_core `
    tests.test_socks_uri `
    tests.test_ui_behavior -v

# Direct Qt destruction/lifetime checks
.\.venv-python313\Scripts\python.exe -m unittest tests.test_qt_lifetime -v

# Hundreds-of-cycles allocation/RSS trend check
.\.venv-python313\Scripts\python.exe -m unittest tests.test_qt_stress -v

Equivalent commands work on Linux/macOS after replacing the virtual-environment executable path with the platform's Python path. No external network access or installed Xray/Hysteria executable is required.

Packaged-build smoke procedure

Packaged/Nuitka builds cannot be safely driven by these in-process unittest fixtures. For an optional release smoke check, use an otherwise disposable test OS account or VM, redirect all Furious application-data/settings locations to a temporary directory, and keep system proxy and TUN disabled. Open and close each transient editor family 50 times, verify one reusable TextEditorWindow does not duplicate actions, and compare live-object diagnostics from an instrumented build before/after the loop. Do not run this procedure against a production profile or rely on process-name cleanup; close only the exact packaged process started for the smoke test.

Isolation rules

• Tests clean up only exact subprocess handles/PIDs and threads they create.
• Tests never search for, signal, or terminate another Furious/core process.
• Persistence tests use temporary INI-backed QSettings namespaces.
• Controller tests inject fake runtime managers and patch host-mutation APIs.
• Qt tests use normal close/deferred-delete paths and collect Python cycles only at diagnostic batch boundaries, never once per UI operation.
• A lifetime failure must be investigated as an ownership defect; increasing thresholds or forcing production garbage collection is not an acceptable fix.