[JBoss JIRA] Created: (JBIDE-4495) Refactor SeamValidatorTest
by Alexey Kazakov (JIRA)
Refactor SeamValidatorTest
--------------------------
Key: JBIDE-4495
URL: https://jira.jboss.org/jira/browse/JBIDE-4495
Project: Tools (JBoss Tools)
Issue Type: Task
Components: QA, Seam
Reporter: Alexey Kazakov
Assignee: Daniel Azarov
Fix For: 3.1.0.M3
It's a pain to debug SeamValidator tests now. There is a very big project with a lot of files. Each test (~100 asserts) change these files to test some particular case. So each test depends on work which previous ones did. If we want to see a state of the project before some test runs we have to figure out what all previous tests did with the project.
So what we should do there:
- Each test should restore a project state. Each test should start work with the same original project.
- Divide big methods with dozens asserts to separate test methods. Otherwise first failure dosn't give next asserts a chance to be run.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 1 month
[JBoss JIRA] Created: (JBIDE-3915) jBPM Eclipse plugin can't save graphical view if gpd.xml is marked as read only
by Hedley Proctor (JIRA)
jBPM Eclipse plugin can't save graphical view if gpd.xml is marked as read only
-------------------------------------------------------------------------------
Key: JBIDE-3915
URL: https://jira.jboss.org/jira/browse/JBIDE-3915
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.1.0
Environment: Windows xp
Eclipse 3.3.2
jPDL Eclipse plugin v3.1.3 SP2
Reporter: Hedley Proctor
Usually when you get files out of a source control system, they will be marked as read only. So if you are editing a Java file in Eclipse, you will get a dialog box coming up asking you to make the file writable. Now consider what happens with jBPM:
Most likely you will check in the gpd.xml file. Otherwise, other people trying to view your processdefinition.xml file will not get a very viewable image. (Everything will appear in the top left.)
When you start editing your processdefinition.xml file, the picture you see will be updated. Everything will appear to be fine. However, none of the changes are saved to the gpd.xml file. When you shutdown Eclipse and restart, the gpd.xml will be out of step with the processdefinition.xml.
I think this could be fixed fairly easily with a couple of lines of code that check the writable status of the gpd.xml file and change it if necessary. Obviously the workaround is just to manually change the write flag, but it is a bit of a "gotcha" and can lead to work being lost if you don't know to do that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 1 month