Skip to content

Generated smoke check for every page and role, on the production database engine #353

Open
Open
Generated smoke check for every page and role, on the production database engine#353

Description

@MendixMau
MendixMau
opened on Oct 14, 2026

Source: external reviewer feedback (2026-10-14).

Now: project-tests/e2e/full-app-walkthrough.js and module journeys exist, but the page × role matrix is not generated. The test stack's DB engine is not checked against the production engine.

Proposal: generate the page × role matrix from the model (SHOW PAGES, page access) and smoke-load each page as each allowed role. The gate flags a test DB engine that differs from the production setting.

Value: medium.

Generated by Claude Code

Activity

  1. MendixMau commented on Oct 14, 2026

    @MendixMau
    MendixMau
    on Oct 14, 2026
    OwnerAuthor

    Gain test case

    Metric: pages × roles with zero smoke coverage, and crashing pages caught.

    • Bench: in a test model, plant one page that crashes for one role only (e.g. a data source that role cannot read).
    • Before: count the pages × roles that journeys touch, and check whether the planted page is caught (expected: missed).
    • Target: 100% of allowed page × role pairs loaded, with the planted crash caught.
    • Also report: matrix run time, and whether the test DB engine matches the production setting.

    Generated by Claude Code

  2. MendixMau commented on Oct 14, 2026

    @MendixMau
    MendixMau
    on Oct 14, 2026
    OwnerAuthor

    Tier: release gate (before UAT or production, budget as needed). The full page × role smoke runs on the production database engine. This applies per skills/testing-shape.md §3 "Check tiers" once #364 lands. Until this issue is built, the table marks it as "(planned: #353)".

    Generated by Claude Code

  3. MendixMau commented on Oct 14, 2026

    @MendixMau
    MendixMau
    on Oct 14, 2026
    OwnerAuthor

    Correction to my comment above: review of #364 renamed "tiers" to check moments, so that it does not collide with testing-shape.md §1's "No tiers". The placement is unchanged: this issue runs at the release gate moment, before UAT or production.

    Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions