You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I rewrote it as pytest with 50 maps instead of 270 (enough to hit the 32/64 layer thresholds) and added actual assertions. Here's the gist: Fixtures create isolated projects so nothing leaks between tests:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey maintainers,
I came across
testsuite/test.t.vect.observe.strds.layer_bug.shand noticed it's been disabled — line 7 is justexit:The test created 270 maps to check layer limits but never actually asserted
anything. It just ran commands and moved on:
I rewrote it as pytest with 50 maps instead of 270 (enough to hit the 32/64 layer thresholds) and added actual assertions. Here's the gist:
Fixtures create isolated projects so nothing leaks between tests:
Basic tests verify the module actually produces correct output:
Error handling — stuff the shell tests never checked:
Layer-limit tests (the re-enabled part, marked
@pytest.mark.slow):All 9 tests pass (~3.5 min total):
Linting clean:
Questions
Before I open a PR
I wanted to check with you all first is this change needed right or no?
tests/(pytest) alongside the existingtestsuite/(shell) for this module?Beta Was this translation helpful? Give feedback.
All reactions