Skip to content

test: add CellpyLimits to cellpy-core parity contract (STEP-08)#390

Merged
jepegit merged 1 commit into
masterfrom
step08-cellpylimits-parity
Jul 1, 2026
Merged

test: add CellpyLimits to cellpy-core parity contract (STEP-08)#390
jepegit merged 1 commit into
masterfrom
step08-cellpylimits-parity

Conversation

@jepegit

@jepegit jepegit commented Jun 26, 2026

Copy link
Copy Markdown
Owner

Summary

  • Completes STEP-08 of the cellpy ⇄ cellpy-core integration roadmap.
  • CellpyLimits (step-type detection thresholds) is mirrored verbatim in cellpycore.legacy; add it to SHARED_CLASSES in tests/test_core_settings_parity.py so the field-for-field parity contract now guards limits alongside headers/units.
  • Updated module docstring/comments to reflect that limits are no longer excluded.

Context: make_step_table already delegates fully to core.make_core_step_table, so no dead step-table engine code remains in cellpy to retire — this test was the last open STEP-08 item.

Test plan

  • uv run pytest tests/test_core_settings_parity.py -q → 5 passed (was 4)
  • uv run pytest tests/ -k "step_table or steptable or make_step" -q → 9 passed (step-table tests stay green via the core seam)

Made with Cursor

CellpyLimits (step-type detection thresholds) is now mirrored in
cellpycore.legacy, so include it in the field-for-field parity test
alongside the headers/units classes to guard against silent drift.

Co-authored-by: Cursor <cursoragent@cursor.com>
@jepegit jepegit merged commit e991130 into master Jul 1, 2026
10 of 14 checks passed
@jepegit jepegit deleted the step08-cellpylimits-parity branch July 1, 2026 08:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant