v0.2.0 (13/N): qmltestrunner harness + CI wiring + close out v0.2.0 plan
Closes the testing-strategy row of PLAN.md §13 v0.2.0 and parks the
two remaining items with rationales.
Shipped:
- framework/qml/tests/{CMakeLists.txt, main.cpp, tst_smoke.qml}
Qt Quick Test scaffold: QUICK_TEST_MAIN bootstrap + one smoke test
proving the harness loads. New tests land as tst_<feature>.qml in
the same dir; qmltestrunner auto-discovers them. Built only when
-DBUILD_TESTING=ON (production AppImages stay clean).
- skeleton + example/todo Makefiles: `make qmltest` target invokes
the configure → build → ctest dance. `make quality` now depends
on qmltest.
- .gitea/workflows/ci.yml: `QML unit tests` step after qmllint in
the Quality job. Out-of-tree build dir (build-tests) so the
CTest run doesn't pollute the cached release build.
Verified locally: configure + build + ctest pass, both smoke
assertions pass, runs in 0.5s.
Closed in PLAN.md §13 v0.2.0 with rationale (no code change):
- Build-time Symfony cache warmup → moved to v0.3.0. The obvious
approach (cache:warmup at build, copy at first launch) doesn't
save any time because Symfony bakes absolute kernel.project_dir
into the compiled cache, and the AppImage's FUSE mount path
changes every launch — every cached path is stale on launch N+1.
Doing it properly requires virtualising getProjectDir(), symlink
fix-up, multi-app namespacing — its own minor's worth of design.
- ReactiveObject cursor pagination → closed N/A. ReactiveObject
already has pending / invoke() / Idempotency-Key correlation /
version-gap detection at parity with ReactiveListModel; the only
feature it lacks is *pagination*, which is meaningless for a
single-entity model.
That fully closes the v0.2.0 plan as documented. Remaining v0.2.0
items in PLAN.md §13 are the audit-ends already shipped earlier in
the cycle (interfaces / BridgeOp / BridgeBundleInfo / Maker DRY /
--with-dto / port negotiation / pre-migration backup / bridge:export
/ periodic auto-update / native-dialogs doc / event maker /
read-model maker / qmltestrunner) plus the two parked items
documented above. Ready to tag when the user gives the word.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
27
framework/qml/tests/CMakeLists.txt
Normal file
27
framework/qml/tests/CMakeLists.txt
Normal file
@@ -0,0 +1,27 @@
|
||||
# QML unit tests — opt-in, only built when BUILD_TESTING is on (CTest's
|
||||
# convention). Wired from ../CMakeLists.txt under the same guard.
|
||||
#
|
||||
# Run via:
|
||||
# cmake -S . -B build -DBUILD_TESTING=ON
|
||||
# cmake --build build --target qml_unit_tests
|
||||
# ctest --test-dir build --output-on-failure -R qml_unit_tests
|
||||
#
|
||||
# Or from the skeleton / example Makefiles via `make qmltest`.
|
||||
|
||||
find_package(Qt6 6.5 REQUIRED COMPONENTS QuickTest)
|
||||
|
||||
qt_add_executable(qml_unit_tests main.cpp)
|
||||
target_link_libraries(qml_unit_tests PRIVATE
|
||||
Qt6::QuickTest
|
||||
Qt6::Qml
|
||||
Qt6::Quick
|
||||
)
|
||||
|
||||
# QUICK_TEST_MAIN reads QUICK_TEST_SOURCE_DIR from the macro definition
|
||||
# at compile time. Point it at this directory so qmltestrunner finds
|
||||
# the tst_*.qml files regardless of where the binary runs.
|
||||
target_compile_definitions(qml_unit_tests PRIVATE
|
||||
QUICK_TEST_SOURCE_DIR="${CMAKE_CURRENT_SOURCE_DIR}"
|
||||
)
|
||||
|
||||
add_test(NAME qml_unit_tests COMMAND qml_unit_tests)
|
||||
9
framework/qml/tests/main.cpp
Normal file
9
framework/qml/tests/main.cpp
Normal file
@@ -0,0 +1,9 @@
|
||||
// QML unit-test runner. Bootstraps the Qt Quick Test framework against
|
||||
// the `tst_*.qml` files in this directory. Invoked via CMake's
|
||||
// `qmltest` test target (CTest) or directly via the produced exe.
|
||||
//
|
||||
// PLAN.md §13 v0.2.0 testing-strategy row.
|
||||
|
||||
#include <QtQuickTest/quicktest.h>
|
||||
|
||||
QUICK_TEST_MAIN(qml_unit_tests)
|
||||
25
framework/qml/tests/tst_smoke.qml
Normal file
25
framework/qml/tests/tst_smoke.qml
Normal file
@@ -0,0 +1,25 @@
|
||||
// Smoke test — proves the qmltestrunner harness is wired up. Doesn't
|
||||
// touch BackendConnection (which would require a live FrankenPHP child)
|
||||
// or any other framework-side code that needs network/state. The
|
||||
// assertion is intentionally trivial; the *infrastructure* is what's
|
||||
// being tested at this layer.
|
||||
//
|
||||
// Add domain-meaningful tests as `tst_<feature>.qml` next to this file
|
||||
// — qmltestrunner auto-discovers any `tst_*.qml` and runs every
|
||||
// `TestCase` function whose name starts with `test_`.
|
||||
|
||||
import QtQuick
|
||||
import QtTest
|
||||
|
||||
TestCase {
|
||||
name: "Smoke"
|
||||
|
||||
function test_qml_engine_alive() {
|
||||
compare(2 + 2, 4, "QtTest harness is loaded and arithmetic still works")
|
||||
}
|
||||
|
||||
function test_string_template() {
|
||||
const x = 7
|
||||
compare(`x is ${x}`, "x is 7", "QML template literals available")
|
||||
}
|
||||
}
|
||||
Reference in New Issue
Block a user