a2nr
/
velxio
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge pull request #225 from davidmonterocrespo24/fix/spice-custom-chip-fixture-check 

test(spice): exclude custom-chip from the static-fixture catalog check
This commit is contained in:
David Montero Crespo 2026-06-10 23:36:22 -03:00 committed by GitHub
parent 2408ccde54 190bb204a0
commit 06a3fef61a
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
frontend/src/__tests__/component-to-spice.test.ts
View File

@ -222,9 +222,18 @@ describe('PASSIVE_PRESETS — preset variants share their base mapper', () => {
});
});
// Mappers whose output depends on live runtime state rather than the static
// component (pins + properties) a fixture can describe. `custom-chip` emits its
// SPICE sources from getChipDrivenPins(comp.id) — the chip's currently-driven
// output pins — so a static fixture always yields null. It is exercised by the
// chip-bus integration tests instead, not this catalog harness.
const RUNTIME_STATE_MAPPERS = new Set(['custom-chip']);
describe('componentToSpice — catalog completeness', () => {
it('every mapped metadataId has a test fixture', () => {
const missing = mappedMetadataIds().filter((id) => !MINIMAL_FIXTURES[id]);
const missing = mappedMetadataIds().filter(
(id) => !MINIMAL_FIXTURES[id] && !RUNTIME_STATE_MAPPERS.has(id),
);
expect(missing, `Missing fixtures for: ${missing.join(', ')}`).toEqual([]);
});