Enum split doctype test skipped from CI because authored MDL fails mx check

[hjotha]

Source

Follow-up from ako's review on merged PR #364 (feat: support enum split microflow statements).

Problem

`mdl-examples/doctype-tests/enum_split_statement.test.mdl` uses the `.test.mdl` suffix, which `TestMxCheck_DoctypeScripts` (in `mdl/executor/roundtrip_doctype_test.go`) skips. That means CI never runs `mx check` against this fixture.

Renaming to `.mdl` surfaces two real Studio Pro validation errors that authored enum-split MDL currently produces:

```
[error] [CE0079] "The '(empty)' condition value should be configured in properties for an outgoing sequence flow."
at Decision '$Status'
[error] [CE0773] "Value must be of type Enumeration EnumSplitExample.Status."
at Sequence flow
```

The script is:

```mdl
split enum $Status
case Open, Pending
return true;
case Closed
return false;
else
return false;
end split;
```

CE0079 means the split's outgoing flows don't carry the `(empty)` case explicitly. CE0773 means one outgoing flow's `CaseValue` isn't typed as the enum. Both point at the builder emitting the wrong BSON shape for the default branch.

Expected behavior

The described-then-executed enum split passes `mx check` with zero errors, and the doctype fixture can be renamed to `.mdl` so CI catches regressions.

Proposed fix

1. Builder: set the `else` branch's `CaseValue` to an empty `EnumerationCase` marker (matching Studio Pro), not just an unset value.
2. Validator: confirm the default branch exists when at least one case is explicit.
3. Rename `enum_split_statement.test.mdl` → `enum_split_statement.mdl` once the build produces a valid MPR, so `TestMxCheck_DoctypeScripts` exercises it.

Related

• Reviewed in feat: support enum split microflow statements #364 by ako.
• Part of Microflow roundtrip stabilization for large-project audit findings #332 (microflow roundtrip stabilization tracker).

[github-actions]

Issue Triage

Summary
The issue reports that the generated enum‑split MDL fails mx check (CE0079 and CE0773), causing the doctype test to be skipped in CI, and proposes fixes to the builder, validator, and test file naming.

Checklist for bug report completeness

Required info	Present?	Details
mxcli version	❌	Not mentioned
Mendix version	❌	Not mentioned
Scenario (what the user was trying to do)	⚠️	Implicitly “running mx check on the fixture via CI”, but not explicitly stated
Expected output	✅	mx check should produce zero errors after the fix
Experienced output	✅	Errors CE0079 and CE0773 shown
AI bug report (session log or mxcli diag --bundle)	❌	Not provided

What’s missing
To help us reproduce and verify the issue, could you please add:

1. The version of mxcli you’re using (output of mxcli --version or commit/build info).
2. The Mendix version of the project you’re processing (e.g., 10.6.x, 9.24.x).
3. A brief description of the exact scenario (e.g., “running mx check locally on the fixture” or “CI job that invokes mx check”).
4. If possible, the session log or the output of mxcli diag --bundle for a run that reproduces the errors.

Once we have those details, we can investigate the builder behavior and confirm the fix. Thanks for bringing this to our attention!

---

Automated triage via OpenRouter — workflow source