MPS 2026.2 EAP1 improves test reporting, node selection, and startup configuration for DSL workbenches

MPS 2026.2 EAP1 introduces two key improvements to editor testing. First, node-matching rules allow engineers to declare which containment roles, properties, or references should be ignored during test execution. Second, per-node markers let engineers annotate individual nodes in the result fixture to suppress false failures. Both features address brittle tests by eliminating irrelevant mismatches and providing clearer failure messages that identify the exact node and cell responsible. This reduces the need for manual fixture adjustments and speeds up debugging by removing the need to reproduce failures in a debugger.

The Find Usages tool window now supports grouping results by virtual package, a feature enabled by default. This mirrors the structure of the Project pane, where virtual folders nest under dotted package names like com.example.ui. The change simplifies navigation in large models by organizing usage results under folder nodes that match the virtual package hierarchy. Engineers can toggle this grouping alongside existing options like module or model, but other tool windows such as Model Checker or Refactoring View retain their default grouping settings. The improvement targets productivity in projects with many virtual folders.

Node selection in the MPS editor becomes more intuitive with the updated Select Up action. When the caret is inside a list of nodes, such as a sequence of statements, Select Up now selects all sibling nodes before moving to the parent. This intermediate step makes operations like copying or pasting groups of nodes faster and more reliable. The behavior is consistent even when the current selection is already a range of nodes, providing a predictable path from individual nodes to their containing structure. The change addresses common editing tasks without requiring new keyboard shortcuts.

Startup configuration in MPS 2026.2 aligns more closely with the IntelliJ Platform. The build tooling now separates the platform-provided boot classpath from MPS-specific extensions, exposing additional JVM arguments in the startup script configuration. This separation allows MPS distributions to inherit the boot classpath and JVM options from the matching IntelliJ Platform build, reducing manual maintenance when integrating platform updates. The generated launchers also apply platform access options more precisely, adding OS-specific packages only to the corresponding launcher. This reduces the risk of startup problems caused by outdated or inconsistent configurations across macOS, Linux, and Windows.