ci / build-test (push) Successful in 2m31s
The dashboards told several stories at once. Overview asked for full calendar years, meter detail for a fixed 12-month window that was really 13, Trends for 24 months with an Apply button, and the energy pages for 60. Each page derived "today" from UTC, so the first hours of a local day belonged to yesterday. A missing tariff, a month nobody measured and a genuine zero all rendered as 0. And a virtual meter -- the one thing the spreadsheet leans on hardest -- was excluded from analysis outright: MeterPeriodService returned null for it and the page offered a flow diagram instead. docs/DASHBOARD_ANALYSIS_CHANGE_BRIEF.md is the work order. Every choice it left open is settled in docs/ANALYSIS_IMPLEMENTATION_NOTE.md as D-01..D-58 plus amendments A-01..A-30; code, tests and release notes cite those ids. The analysis layer Core/Analysis holds the pure rules: period presets resolved once in the instance zone into a local date range and a half-open UTC range, bucket plans, calendar-unit comparisons, coverage runs with a resolution class, normalized quantities and units, the totals policy, the virtual formula parser/validator/evaluator, and the cost calculator. "Now" comes from TimeProvider; services never read the clock. Normalization now writes, in the same transaction as consumption and by diff, per-meter rollups by local day and month plus coverage runs and a rollup state (AnalysisDataWriter). AnalysisReader answers a request from those tables -- month rollups for month and year buckets, day rollups otherwise, at most two partial edge days from consumption -- and CostReader prices the result month by month. Pages, /api/v1 and the CSV export read nothing else. The unused continuous aggregates are dropped. The reader's statement count per request is constant whether it covers one meter or a thousand. On a synthetic 1,000-meter, ten-year instance the brief's target request (100 meters, ten years, monthly) takes 374 ms against a two-second target, and the Overview went from 48,244 SQL statements per load to 205. Missing is not zero Every bucket carries a status -- available, partial, missing, unresolved, invalid, pending -- derived from coverage, never from the amount, with provenance and a reason code beside it. A true zero is a number and a bar on the baseline; an unknown bucket is a gap that says why; a month whose data only exists monthly says so instead of inventing daily detail; a scope with no tariff says "not priced" instead of 0. Rows whose interval closes after now are reported separately rather than counted. Virtual meters are analysis subjects A virtual meter stores a canonical definition -- expression over m<id> references, result kind, unit and cost rule -- validated on save and on read for syntax, unknown or self references, loops and unit/kind rules. It is evaluated on read from its sources' rollups over their joint coverage: a missing source makes the bucket missing, an observed zero is a valid input, a non-finite result is invalid with its dependency path, and the page lists each source's contribution. Topology links are topology only and never rewrite a saved calculation; expression-less meters from older installs are converted once at startup. The editor has Sum, Difference and Advanced modes with a live preview. Totals and the bill Per energy type the totals policy separates use, grid import, export, generation and runtime, marks breakdown meters as breakdowns and virtual meters as views, and never adds across units. The bill follows it: grid import where there is one, separately priced subsections at their own price, feed-in only on export meters, standing charges once per scope per local day, manual costs once on their start day, categories as non-overlapping covers whose composition reconciles to the bill. The seeded demo's yearly totals now match the spreadsheet. Pages and navigation The period lives in the URL and every page reads the same contract, so a link, a reload and the browser's Back button keep it. Shared components carry it: page header with breadcrumbs, period toolbar, theme-aware chart with an accessible table beside it, metric cards, comparison and availability states, attention items that each link to the one action that fixes them. Meter detail leads with an Analysis tab and resolves its tabs by key; the energy page has Overview, History, Flow and Meters; the old cost-only Trends page is a general Analysis page over portfolio, type, category, meter or a meter comparison. Records tabs are paged server-side instead of showing the latest 200. Everything is English and German, light and dark, down to 360px. Some figures change on purpose; docs/RELEASE_NOTES.md lists each one and what the first start after the update does (it rebuilds all analysis data before the web server listens). docs/SDD.md and CLAUDE.md describe the system as it now is. Tests: 1,733 Core and 746 integration, all green, plus an opt-in performance suite with a synthetic 1,000-meter generator.
98 lines
4.1 KiB
C#
98 lines
4.1 KiB
C#
using System.Data.Common;
|
|
using Microsoft.EntityFrameworkCore;
|
|
|
|
namespace MeterVault.Integration.Tests;
|
|
|
|
[Collection("Timescale")]
|
|
public sealed class SchemaTests(TimescaleFixture fx)
|
|
{
|
|
[Fact]
|
|
public async Task Migrations_are_applied()
|
|
{
|
|
await using var ctx = fx.CreateContext();
|
|
var applied = (await ctx.Database.GetAppliedMigrationsAsync()).ToList();
|
|
|
|
Assert.Contains(applied, m => m.EndsWith("InitialSchema", StringComparison.Ordinal));
|
|
Assert.Contains(applied, m => m.EndsWith("TimescaleHypertables", StringComparison.Ordinal));
|
|
Assert.Contains(applied, m => m.EndsWith("AnalysisRollups", StringComparison.Ordinal));
|
|
}
|
|
|
|
[Fact]
|
|
public async Task The_continuous_aggregates_and_their_refresh_jobs_are_gone()
|
|
{
|
|
// D-17: nothing read them, they were Berlin-only and stale; the analysis tables replace them.
|
|
await using var ctx = fx.CreateContext();
|
|
var conn = ctx.Database.GetDbConnection();
|
|
await conn.OpenAsync();
|
|
|
|
Assert.Empty(await QueryStringsAsync(conn,
|
|
"SELECT view_name::text FROM timescaledb_information.continuous_aggregates;"));
|
|
Assert.Empty(await QueryStringsAsync(conn,
|
|
"SELECT proc_name::text FROM timescaledb_information.jobs WHERE proc_name = 'policy_refresh_continuous_aggregate';"));
|
|
Assert.Empty(await QueryStringsAsync(conn,
|
|
"SELECT relname::text FROM pg_class WHERE relname IN ('consumption_daily', 'consumption_monthly', 'consumption_yearly');"));
|
|
}
|
|
|
|
[Fact]
|
|
public async Task The_analysis_tables_are_plain_tables_that_go_with_their_meter()
|
|
{
|
|
// D-12: plain tables (the hypertable list above stays reading + consumption), each tied to its meter by a
|
|
// cascading foreign key, so deleting a meter — or wiping all of them — never trips over them.
|
|
await using var ctx = fx.CreateContext();
|
|
var conn = ctx.Database.GetDbConnection();
|
|
await conn.OpenAsync();
|
|
|
|
var cascading = await QueryStringsAsync(conn,
|
|
"SELECT tc.table_name::text FROM information_schema.table_constraints tc " +
|
|
"JOIN information_schema.referential_constraints rc ON rc.constraint_name = tc.constraint_name " +
|
|
"JOIN information_schema.constraint_column_usage cu ON cu.constraint_name = tc.constraint_name " +
|
|
"WHERE tc.constraint_type = 'FOREIGN KEY' AND rc.delete_rule = 'CASCADE' AND cu.table_name = 'meter' " +
|
|
"AND tc.table_name IN ('consumption_rollup', 'consumption_rollup_month', 'meter_coverage', 'meter_rollup_state') " +
|
|
"ORDER BY 1;");
|
|
|
|
Assert.Equal(["consumption_rollup", "consumption_rollup_month", "meter_coverage", "meter_rollup_state"], cascading);
|
|
}
|
|
|
|
[Fact]
|
|
public async Task Reading_and_consumption_are_hypertables()
|
|
{
|
|
await using var ctx = fx.CreateContext();
|
|
var conn = ctx.Database.GetDbConnection();
|
|
await conn.OpenAsync();
|
|
|
|
var names = await QueryStringsAsync(conn,
|
|
"SELECT hypertable_name FROM timescaledb_information.hypertables ORDER BY hypertable_name;");
|
|
|
|
Assert.Equal(["consumption", "reading"], names);
|
|
}
|
|
|
|
[Fact]
|
|
public async Task Reading_has_a_compression_policy()
|
|
{
|
|
await using var ctx = fx.CreateContext();
|
|
var conn = ctx.Database.GetDbConnection();
|
|
await conn.OpenAsync();
|
|
|
|
// A compression/columnstore policy shows up as a scheduled job against the hypertable.
|
|
var jobs = await QueryStringsAsync(conn,
|
|
"SELECT hypertable_name FROM timescaledb_information.jobs " +
|
|
"WHERE proc_name IN ('policy_compression', 'policy_columnstore') AND hypertable_name = 'reading';");
|
|
|
|
Assert.Contains("reading", jobs);
|
|
}
|
|
|
|
private static async Task<List<string>> QueryStringsAsync(DbConnection conn, string sql)
|
|
{
|
|
await using var cmd = conn.CreateCommand();
|
|
cmd.CommandText = sql;
|
|
var results = new List<string>();
|
|
await using var reader = await cmd.ExecuteReaderAsync();
|
|
while (await reader.ReadAsync())
|
|
{
|
|
results.Add(reader.GetString(0));
|
|
}
|
|
|
|
return results;
|
|
}
|
|
}
|