Community
Participate
Working Groups
Steps to reproduce: - Create a profile with OCL constraints and a model which has the profile applied. Make sure one constraint is violated. - Right-click on the diagram, and select Validation->Validate Model (or subtree, or …) -> nothing will happen - Right-click on the model explorer and do the same -> Everything works fine.
Shoudl be fixed with commit fecb208e71175b1109aa28ffe16a779155381148. Can you please re-check (allow some time for the build)
(In reply to Ansgar Radermacher from comment #1) > Shoudl be fixed with commit fecb208e71175b1109aa28ffe16a779155381148. Can > you please re-check (allow some time for the build) Seems to work now! Given this used to work fine in Kepler: would it be possible to create a unit test for these kinds of scenarios?
Juan, can you please have a look, if its possible to test which handler is called in the context menu of an element (within model explorer and diagram).
(In reply to Ansgar Radermacher from comment #3) > can you please have a look, if its possible to test which handler is called > in the context menu of an element (within model explorer and diagram). That seems like an internal detail. IMHO there should be tests of the user experience. i.e. Open Diagram. Validation->Validate Model Check that Model Validation view is visible. Check that the Model Validation has the expected entries - correct number and severity per element - correct text I generally check correct text by rebinding the original templates thereby giving some immunity to evolution of messages.
