All files / realm/blong-party/browser/test/feature aclDiagnostics.ts

100% Statements 39/39
100% Branches 0/0
100% Functions 0/0
100% Lines 39/39

Press n or j to go to the next uncovered block, b, p or k for the previous block.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 401x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x  
/**
 * ACL matrix diagnostics — the failure has to be readable.
 *
 * A matrix is only worth its green run if a red one tells you which cell is wrong
 * and why, so the report is a contract rather than a side effect: the table is
 * redrawn with the offending cell marked `expected≠actual`, and every mismatch is
 * also named (row, column, both values) underneath it.  These scenarios hold that
 * contract in place — they drive the real `aclMatrix` (`party.person.get`) and the
 * real `aclFixture` (`party.fixture.get`) with a **deliberately wrong** table and
 * assert that the report marks each mismatch *in the cell it belongs to*, then
 * that a table with nothing wrong reports nothing.
 *
 * They are a feature file rather than a unit test on purpose: what is being
 * asserted is the whole path a reader sees — the probe through the gateway, the
 * comparison, the redraw and the assertion message tap prints.
 *
 * Asserted by `browser/test/test/testAclDiagnostics.ts`
 * (group `test.acl.diagnostics`), which runs in every suite run.
 */
export default `Feature: ACL matrix diagnostics — a failure has to be readable
 
  Scenario: A wrong matrix cell is marked where the reader looks
    # Amy may read herself and Ben (both are in North); Cam is in South, so the
    # cell below is wrong on purpose.
    Then probing the access matrix reports every mismatch in its own cell
      | viewer | Amy | Ben | Cam | notes               |
      | Amy    | ✅  | ✅  | ✅  | Cam is out of scope |
 
  Scenario: A wrong fixture row is marked where the reader looks
    # North belongs to Axis; the table claims Beta, so the row is wrong on purpose.
    Then probing the ACL fixture reports every mismatch in its own cell
      | record | kind | belongsTo | notes       |
      | North  | unit | Beta      | really Axis |
 
  Scenario: A table with nothing wrong reports nothing
    Then probing the access matrix reports no mismatch
      | viewer | Amy | Ben | Cam |
      | Amy    | ✅  | ✅  | ❌  |
`;