[
https://jira.jboss.org/jira/browse/JBIDE-4495?page=com.atlassian.jira.plu...
]
Denis Golovin commented on JBIDE-4495:
--------------------------------------
Try to use validator reporter to check if there is or there is no errors. That would make
test more stable. Markers are created in asyncExec after validation is finished and that,
I suspect, is reason why these tests fail sometimes.
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.M4
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