Skip to content

v0.21.0

Choose a tag to compare

@github-actions github-actions released this 11 Nov 15:08
189a37d

Added

  • bca bundle: everything as one artifact. One folder and one ZIP file
    with a manifest: validation (the health check), the simulation, a snapshot
    of every process test, the layered documentation with the view, narrative
    pages when a model is set up, and the test results (--test-results,
    JUnit or xUnit XML) and build outputs (--include) it is given.
    bundle.json names the commit, every step with its result, and every file
    with its hash. Exit code 1 when a step failed; the bundle is written all
    the same. MCP tool bc_atlas_bundle. See The bundle.
  • Simulate on recordings. With simulation.recordings (or
    --recordings) the agents perform the recordings of Business Central as
    well. What really ran says what it takes: Execute on the pages,
    codeunits, and reports on the call stacks, and the table right of every
    read and write. A recording with the title of a process test adds what
    really ran to that test; any other recording is a process of its own, so
    a process can be simulated before anyone wrote a UI test for it.
  • Snapshots from the source. bca simulate --snapshots <folder> (or
    simulation.snapshotDir) writes one fact snapshot per process test in the
    schema of the recordings: its steps as phases, what each step needs as
    technical steps, and who performs it.
  • A run of the simulation, step by step. A run shows how the result
    came about: one person performs the assigned process tests, and each step
    shows where the person is. The picture is built by it: it starts with the
    person, every step adds the process test and the objects it needs, and
    where the person is stopped the step says which permission is missing and
    what to add. In the view under Simulate › Run, step by step; in the
    terminal and for agents as the stories run:<person> of bca view and
    bc_atlas_view; in bca layers and bca bundle as one page per run
    with its picture. The new lens Run is the canvas of all runs.
  • Simulate and build in one place. The Simulate menu of the view builds
    the bundle (in VS Code), and the bundle has the step Runs, step by
    step
    .
  • Simulate in the view says what stops it. The menu lists the findings
    of the simulation at the top, each one click from the person or the
    process test it is about, and Start from the process tests writes the
    company the tests describe as the start of your own.