Model validation within workflow execution
Description
Environment
Test Case Description
Test step | Expected result | |
|---|---|---|
| 1 | Clone MinimumExample test project from the Examples repository using tool of choice and import project into Palladio.
or: File → New → Other… → New Palladio Project - Sirius → enter name → Next > → Create … using one of the initiator templates. → Minimum Example Template | A project "Minimum Example" is available in the project explorer. |
| 2 | Open allocation model, remove the contained AllocationContext from the model’s resource container and save the edited model. | The allocationContext is not allocated to any resource container |
| 3 | Start simulation by executing launch configuration MinimumExample | The simulation is paused by displaying the following warning message to the user: Message: The 'eachAssemblyContextWithinSystemHasToBeAllocatedExactlyOnce' invariant is violated on 'org.palladiosimulator.pcm.allocation.impl.AllocationImpl@63e23ee1{file:/C:/dev/workspaces/runtime-sandbox-modeling-2020-12-palladio-testing-day/de.uka.ipd.sdq.codegen.simucominstance/model/platform/resource/Minimum_Project/default.allocation#_JiPBICHdEd6lJo4DCALHMw}' |
is blocked by
Activity
Dominik Werle January 11, 2022 at 1:08 PM
warnings about constraint are shown before running. can be ignored via the dialog. works for both LPG and Pivot.
Martina Rapp November 26, 2021 at 9:36 AM
Reinvestigate issue
validation works but dialog is not opened and displayed (Dominik)
Dominik Werle November 26, 2021 at 8:20 AMEdited
The simulation run fails with a NullPointerException
Simulation is not paused and no warning message is displayed.
Both in the new invalidated model the simulation displays the warning
I used Eclipse and installed from the nightly update site. Then, the normal checked out model reports the same warning. It does not report an warning for the normal model, when changing the OCL delegate from Pivot to LPG.
Floriment Klinaku January 29, 2021 at 8:21 AM
Using the Palladio Drop.
Invalidated the model through the tree editor. In the output a warning is shown “[Worker-12: Launching New_configuration] WARN : Found validation problems in the models”, however, the simulation is not paused and a warning message as described in the test case does not appear.
Details
Details
Assignee
Nicolas BoltzReporter
Martina RappPriority
Major
The test case checks model validation within a user workflow execution.
When the user starts a Simulizar simulation, the executed workflow internally runs a model validation job prior to the actual simulation job. If the simulated model contains any modeling errors, the system notifies the user with a dedicated warning message. The message states the violated invariant(s) and the affected model element(s).