Community
Participate
Working Groups
The Diagram View Synchronization (canonical edit-policy) feature implemented in bug 433206 needs JUnit test coverage. The best way to do this in the long term is to add synchronization tests to the Papyrus Diagram Tests Generation Framework, currently prototyped and under review in Gerrit: https://git.eclipse.org/r/38587 That Gerrit change already has an initial generation of synchronization tests for top-level nodes, but it is not yet complete. In addition, I am proposing to take that test generation framework in a slightly different direction, so a new separate work item is warranted.
New Gerrit change created: https://git.eclipse.org/r/45831 WARNING: this patchset contains 131690 new lines of code and may require a Contribution Questionnaire (CQ) if the author is not a committer on the project. Please see:https://wiki.eclipse.org/Project_Management_Infrastructure/Creating_A_Contribution_Questionnaire
The latest update on the Gerrit patch: Patch set 6 completes the specification of generation of view synchronization tests, adding the following scenarios: * synchronize child label nodes in label compartments of top shapes * synchronize child shape nodes in shape compartments of top shapes * synchronize connections between shapes * synchronize connections between shapes where the source owns the semantic link All synchronization tests for the Class Diagram are generated as a demonstration because this diagram has the most fully specified tests (covers all cases). Note that this test suite, like the creation-from-palette suite, has the problem of the cross-product of all conceivable creation of child nodes in top nodes doesn't make sense. Likewise the cross-product of all conceivable creation of links between pairs of shapes. We still need to solve that test-case filtering problem for all test suites.
New Gerrit change created: https://git.eclipse.org/r/50462
New Gerrit change created: https://git.eclipse.org/r/53600
Gerrit change https://git.eclipse.org/r/53600 was merged to [master]. Commit: http://git.eclipse.org/c/papyrus/org.eclipse.papyrus.git/commit/?id=5b46f47b24f3afd8218cabf1834c850abbc51773
The generation of JUnit tests for the diagrams, including model-view synchronization tests, is now integrated in the master branch (for Neon release). A new weekly build runs the generated tests for all diagrams: https://hudson.eclipse.org/papyrus/job/Papyrus-Master-Generated-Tests/
@Camille, @Rémi: Do we want or need to implement this test generation on the Mars maintenance branch, too? I'm not sure that we would want to run test jobs for both branches ...
I'm not going to merge this to Mars maintenance. It will have to be sufficient that these tests run (and mostly fail, currently) on master for Neon.