On maintenance/gramps60, four addons have a tests/ directory with test_*.py files but no tests/__init__.py package marker. maintenance/gramps61 already has it for all of them, so this is a gramps60-only parity gap. Without the marker the test package isn't a proper Python package and the addon-unit discovery (<Addon>.tests.<module>) can silently skip the suite.
Missing on gramps60 (present on gramps61):
CalculateEstimatedDates/tests/__init__.pyDataEntryGramplet/tests/__init__.pyForm/tests/__init__.pyTMGimporter/tests/__init__.py
gramps60-only fix (do not touch gramps61). Related: #38 (move gi.require_version pins into the __init__.py — assumes it exists); prior ci-validate/931-init-py. No Mantis ticket — tracked here per the non-Mantis→fork-issue convention. (Surfaced from gramps-testbed-v2 issue #8 task 2.)
On
maintenance/gramps60, four addons have atests/directory withtest_*.pyfiles but notests/__init__.pypackage marker.maintenance/gramps61already has it for all of them, so this is a gramps60-only parity gap. Without the marker the test package isn't a proper Python package and the addon-unit discovery (<Addon>.tests.<module>) can silently skip the suite.Missing on gramps60 (present on gramps61):
CalculateEstimatedDates/tests/__init__.pyDataEntryGramplet/tests/__init__.pyForm/tests/__init__.pyTMGimporter/tests/__init__.pygramps60-only fix (do not touch gramps61). Related: #38 (move
gi.require_versionpins into the__init__.py— assumes it exists); priorci-validate/931-init-py. No Mantis ticket — tracked here per the non-Mantis→fork-issue convention. (Surfaced from gramps-testbed-v2 issue #8 task 2.)