FlexMeasures / flexmeasures / 37447223201

87%

Build Type

push

github

Committed by web-flow

Commit Message

perf: speed up the test suite about threefold (#2638)

* fix: order an asset's sensors by id

Without an ORDER BY, PostgreSQL returns the rows in physical order, which drifts from
insertion order once the sensor table has a history of updates, so asset.sensors[0]
could be any of the asset's sensors.

Signed-off-by: Stijn van Houwelingen <teadrinkingprogrammer@proton.me>

* docs/changelog: link PR #2637 in the sensor order entry

Signed-off-by: Stijn van Houwelingen <teadrinkingprogrammer@proton.me>

* perf: hash test passwords with minimal argon2 cost

Flask-Security's default argon2 settings cost 50 to 90 ms per hash, and the fixtures
hash eleven passwords several hundred times per run; about 160 s of the suite.

Signed-off-by: Stijn van Houwelingen <teadrinkingprogrammer@proton.me>

* perf: create the test schema once and truncate between tests

Tests that took asset.sensors[0] picked up the wrong sensor once tables kept their
history; they now select the power sensor by name.

Signed-off-by: Stijn van Houwelingen <teadrinkingprogrammer@proton.me>

* perf: create the test users in one flush

Signed-off-by: Stijn van Houwelingen <teadrinkingprogrammer@proton.me>

* perf: share module data in read-only API and CLI test modules

Module-scoped fixtures now commit: flushed-only data vanished at the first rollback,
which is what made several tests order dependent.

Signed-off-by: Stijn van Houwelingen <teadrinkingprogrammer@proton.me>

* refactor: rename the CLI dummy fixtures to the fresh_db convention

Signed-off-by: Stijn van Houwelingen <teadrinkingprogrammer@proton.me>

* refactor: drop db fixtures that data fixtures already provide

Signed-off-by: Stijn van Houwelingen <teadrinkingprogrammer@proton.me>

* perf: shrink two oversized test inputs

A config test ran 120 forecast steps for an assertion about its config, and a
load-speed test inserted 100k rows one by one.

Signed-off-by: Stijn van Houwelingen <teadrinkingprogrammer@proton.me>

* docs/cha... (continued)

Coverage Stats

79 of 83 new or added lines in 2 files covered. (95.18%)

2 existing lines in 2 files now uncovered.

20995 of 24318 relevant lines covered (86.34%)

0.86 hits per line