Rehearse the riskiest integration — Flash-check repair

PART I

Warm-up

Reconnect with a useful idea before starting rehearse the riskiest integration. In one or two sentences, describe the input, output or host boundary from the previous exercise that this lesson builds on. If you are arriving directly, skim the worked example first; there is no locked prerequisite.

A rough note is enough. You can revise it after the example.

PART II

Instruction & guided example

Repair a rehearsal that writes the expected answer into its evidence

An integration rehearsal isolates a consequential assumption with disposable inputs, independent expectations and an observation plan. This public site supplies no .ws runtime or native test harness, so the result is a concrete reproducible rehearsal artifact. It must never claim that a paper trace measured host behavior or mutate live user resources to create failure evidence.

The broken rehearsal preloads “two low-stock items” into the output, then declares the query correct because two items are displayed. Sample repair separates source data, independent expected rows, actual host result and comparison. With rope 2/lamp 9/flask 10, the expected identifiers must be rope and lamp, not merely any count of two.

A self-fulfilling output is not an integration test. Even a count match can conceal wrong membership or ordering. In this site, leave actual result unobserved until a real host produces it; do not fill it from the expectation.

Worked reasoning and supplied artifact

// Worked contract artifact:
// The broken rehearsal preloads “two low-stock items” into the output, then declares the query correct because two items are displayed. Sample repair separates source data, independent expected rows, actual host result and comparison. With rope 2/lamp 9/flask 10, the expected identifiers must be rope and lamp, not merely any count of two.

Illustrative example from the proposed WillowScript design. The language and WUIX/WMATH/WDB/WAUDIO/WTMP services are not implemented in the supplied source. This site has no interpreter, VM or native host and does not execute or certify the snippet.

Try the guided change

Rewrite the evidence sheet with distinct input, expectation, actual-result and comparison fields.

• Write the supplied inputs and initial state before following the example.
• Reconstruct each intermediate calculation or host decision, then compare with the worked artifact.
• Explain why the contrasting alternative fails before attempting the changed inputs in Part IV.

PART III

Take a breather

Step back after the guided example. Look away from the screen, stretch, or reread your prediction. This is an optional learning pause, not a timer or an assessment gate.

When you return, try to name the lesson’s key idea without copying its wording. If that feels difficult, return to Part II and trace one line rather than restarting the entire lesson.

PART IV

Independent practice

Project context: Independent WillowScript application. Build a small, understandable change around rehearse the riskiest integration.

Repair a schedule rehearsal that accepts any two returned venues when the expected identifiers are north and east. Provide a counterexample with the same count but wrong membership.

What to produce

A noncircular evidence form and a two-row wrong-membership counterexample.

• State the intended behavior in a sentence before editing.
• Use only source-backed syntax and the host services whose contract you have been given.
• Record a normal case and a boundary or unavailable-resource case.
• Label hand predictions separately from anything actually measured in a supplied toolchain.

Syntax colors are a reading aid, not a compiler. The line you are editing stays uncolored until you move to a different line; capitalization is never changed. Drafts stay on this browser and code is not executed.

import wuix.widget;
import app;
domain Workspace {
    const application = Application({
        name: "Workspace",
        window: { title: "Dashboard", size: [1280, 800] },
        events: {
            "app.ready": fnc() -> void { console.log("Ready"); }
        }
    });
}

PART V

Self-check

Use this check to notice what to revisit. It does not award a private course grade, block another page or claim to verify compiled code. Every answer has a learning explanation.

You may keep exploring even if you are unsure. Use the hint, compare the trace, and revise your explanation.

PART VI

Recap & small task

Bring the idea back to the mod feature you are building. A useful recap connects the mechanism to a decision you can make in your own code.

• Repair a rehearsal that writes the expected answer into its evidence
• Rewrite the evidence sheet with distinct input, expectation, actual-result and comparison fields.
• Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Rewrite the evidence sheet with distinct input, expectation, actual-result and comparison fields.

This marks your personal practice record only. It is not a certification or an official workspace assessment.