Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 360116 - [Model Explorer] Papyrus ModelExplorer should be covered with JUnit Test
Summary: [Model Explorer] Papyrus ModelExplorer should be covered with JUnit Test
Status: RESOLVED DUPLICATE of bug 379150
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 0.8.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-06 11:45 EDT by Vincent Lorenzo CLA
Modified: 2012-05-23 06:33 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vincent Lorenzo CLA 2011-10-06 11:45:00 EDT 
I noticed that we often get regressions concerning the actions in the ModelExplorer. So we need JUnit tests to avoid this kind of problems.
In a first time, I think that the most critical actions are Delete and Rename.
The JUnit should tests : 
	- the enabled/disabled of the handler for the actions
	- when it is possible, we should execute the handler to verify that the action is correctly executed
	- when it is possible, we should test undo and redo too
Comment 1 Vincent Lorenzo CLA 2011-10-06 11:48:38 EDT 
In R5743 (branch) a first commit for the plugin oep.modelexplorer.test
The JUnit tests succeeded on branch (not yet tested on trunk).
Currently, the Rename and the Delete actions are tested. For the moment, we test the handler activation, but not the execution of the command (excepted for Delete UML Element).
Comment 2 Vincent Lorenzo CLA 2011-10-12 09:01:33 EDT 
In R5795 : new project : oep.papyrus.test.common which will provide common methods for JUnit tests
Comment 3 Remi Schnekenburger CLA 2012-05-23 06:33:49 EDT 
Duplicate of the bug 379150.

*** This bug has been marked as a duplicate of bug 379150 ***