Files
dawnline/web/tests/way.test.ts
T
Aemeath ac90575b0b
Build packages / CI (push) Blocked by required conditions
Build packages / Version (push) Waiting to run
CI / Web (format, types, tests, bundles) (push) Blocked by required conditions
CI / ShellCheck (push) Blocked by required conditions
CI / Backend (Go: vet, tests, a real ubusd and uhttpd) (push) Blocked by required conditions
CI / Package files (push) Blocked by required conditions
Dawnline 0.20.0
- **Backend rewritten in Go.** One daemon, `dawnlined`, replaces the whole ucode backend: the rpcd plugin, the agent, the CLI and the updater. The package no longer depends on ucode.
- **Per-architecture builds.** The release carries the backend for arm64, ARMv7, mips, mipsle and amd64; the router fetches its own after the package is installed and checks its sha256. Dawnline does not run on other architectures (older ARM, 32-bit x86, RISC-V).
- **Faster on the router.** A firewall sync takes 0.06 s instead of 0.9 s; a full apply takes about 300 ms. The portal is served by the daemon itself, without a CGI process per request.
- **Live pages.** The admin and the portal follow a live stream from the router instead of re-fetching the whole state every 30 seconds.
- **Admin redesigned in the portal's style.** Three sections (Overview · Log · Settings); a server is a page of its own with People, Places and Settings; a device opens as a dialog over its person.
- **Changes wait for «Apply».** Every setting, and a person's access, is staged in one dock before it reaches the router.
- **Configuration rollout.** After a change that makes devices fetch their configuration again, the admin shows how many have fetched it and who has not. Every setting shows beforehand (⟳N) how many devices it will touch.
- **Waiting for a decision.** Overview and People put first the people who need one (access ended, limit reached, a device that does not connect), each with its one action a tap away.
- **Bulk actions on people.** «Select» (or a long press on a card) picks several people to extend by a month, pause or resume at once.
- **Undo.** An action done from a card or a request is undone from its toast.
- **Update dialogs redesigned.** An update is one view from its question to its result; Dawnline's own update runs in it like every other, and the page reloads itself once the new version answers. Other versions are a list, each with its notes and Install on a page of its own.
- **Site to site: networks behind a router.** A router connected as a device can have networks behind it (up to eight, /16 to /30): the server routes them and applies the router's access to them. A network that shares addresses with a tunnel, the router's own networks or another site is refused by name.
- **Routers from the portal.** People can add a router and name its networks on their own page; the admin accepts or declines with a reason, or lets them through without asking.
- **Check access and Health know the networks behind routers.**
- **Usage limits reworked.** A monthly limit no longer follows the calendar. A person's month starts with their first traffic and ends a month later; the next one starts only when they connect again, so time away uses up none of it. Before, everyone's limit reset on the 1st.
- Extra data lasts until that person's month ends; «Reset usage» starts the month anew.
- A limit is for a month or for the whole term; the admin and the portal show when it resets.
- Charts that said «this month» show the last 30 days.
- After the update nobody loses what was counted: the month that was running becomes the person's first and ends on the 1st.
- **Access by time of day removed.** The Hours limit is gone from the admin, the portal and the backend; saved hours are dropped.
- **Expiry simplified.** An end date always stops access, with a heads-up three days before; the per-person choice is gone.
- **No false disconnects from sleeping phones.** A phone or a tablet stays online through ten minutes of silence.
- **Mobile Safari fixes.** Pressing a control no longer sends the page to its top; tab tracks that do not fit scroll; switches animate after a press.
2026-11-13 09:43:50 +03:00

78 lines
3.1 KiB
TypeScript
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
import { describe, expect, it } from 'vitest';
import { wayState } from '../src/portal/way';
import type { Device, SetupState } from '../src/shared/types';
/** When the sheet opened (router clock). */
const OPENED = 1_792_400_000;
/** A device as the router sends it while it is being set up: never connected, nothing on its link. */
function dev(o: Partial<Device> = {}): Device {
return {
id: 'd_1',
name: 'Pixel 9',
kind: 'phone',
address: '10.8.0.5',
disabled: false,
created: OPENED - 30,
created_by: 'portal',
online: false,
handshake: 0,
endpoint: '',
active: true,
month: [0, 0],
total: [0, 0],
spark: [],
hostname: 'pixel-9.user.lan',
browser_key: false,
config_stale: false,
config_issued: 0,
lan_bypass: false,
mtu: 0,
keepalive: null,
mtu_used: 1280,
keepalive_used: 25,
link: null,
setup: null,
...o,
};
}
const setup = (state: SetupState, since = OPENED + 5) => ({ state, since });
describe('the set-up sheet’s way', () => {
it('waits while the device is not heard from', () => {
expect(wayState(dev(), OPENED)).toBe('waiting');
// Online with an old handshake, quiet: not this set-up's connection.
expect(wayState(dev({ online: true, handshake: OPENED - 40 }), OPENED)).toBe('waiting');
});
it('shows knocks that never finish whenever they come, before the sheet or after', () => {
expect(wayState(dev({ setup: setup('trying') }), OPENED)).toBe('trying');
expect(wayState(dev({ setup: setup('trying', OPENED - 60) }), OPENED)).toBe('trying');
// An older session still counts online while its rekeys fail: still trying.
expect(wayState(dev({ online: true, handshake: OPENED + 2, setup: setup('trying') }), OPENED)).toBe('trying');
});
it('arrives when data flows after a handshake newer than the sheet', () => {
expect(wayState(dev({ online: true, handshake: OPENED + 9, setup: setup('flowing') }), OPENED)).toBe('connected');
// The router's watcher may lag the handshake by a second: data flowing is what counts, not `online`.
expect(wayState(dev({ online: false, handshake: OPENED + 9, setup: setup('flowing') }), OPENED)).toBe('connected');
});
it('does not arrive on a handshake alone', () => {
expect(wayState(dev({ online: true, handshake: OPENED + 9 }), OPENED)).toBe('waiting');
expect(wayState(dev({ online: true, handshake: OPENED + 9, setup: setup('nodata') }), OPENED)).toBe('nodata');
});
it('keeps what began before the sheet for the sheet before', () => {
// Already flowing, or already without data, on a handshake older than the sheet: not this set-up's.
expect(wayState(dev({ online: true, handshake: OPENED, setup: setup('flowing', OPENED - 90) }), OPENED)).toBe('waiting');
expect(wayState(dev({ online: true, handshake: OPENED - 20, setup: setup('nodata', OPENED - 5) }), OPENED)).toBe('waiting');
});
it('goes back to plain waiting when the device goes quiet, offline or away', () => {
expect(wayState(dev({ online: false, handshake: OPENED + 9, setup: null }), OPENED)).toBe('waiting');
expect(wayState(undefined, OPENED)).toBe('waiting');
});
});