Issue 632 in moose-technology: Build a test to capture the FAMIX API problems with Java systems
Status: New Owner: tu...@tudorgirba.com Labels: Type-Defect Priority-Critical Component-Famix Milestone-4.5
New issue 632 by tu...@tudorgirba.com: Build a test to capture the FAMIX API problems with Java systems http://code.google.com/p/moose-technology/issues/detail?id=632
We need a test to drive this problem.
One solution is to take an MSE file produced by VerveineJ for the test_src and run the MooseFinderTests with it.
Comment #1 on issue 632 by tu...@tudorgirba.com: Build a test to capture the FAMIX API problems with Java systems http://code.google.com/p/moose-technology/issues/detail?id=632
We now have VerveineJMooseFinderTest that capture the Moose Finder failures for the test_src from VerveineJ.
Now, we just need to fix them :)
Comment #2 on issue 632 by tu...@tudorgirba.com: Build a test to capture the FAMIX API problems with Java systems http://code.google.com/p/moose-technology/issues/detail?id=632
fixed the tests on the local machine. This means that it should be safe (as long as the tests from VerveineJ cover the cases) to use group menu items on Java systems.
They still fail on the server, but that is probably because of the headless handling of morphic windows.
Updates: Labels: -Milestone-4.5 Milestone-4.6
Comment #3 on issue 632 by jannik.l...@gmail.com: Build a test to capture the FAMIX API problems with Java systems http://code.google.com/p/moose-technology/issues/detail?id=632
(No comment was entered for this change.)
Updates: Status: Fixed
Comment #4 on issue 632 by tu...@tudorgirba.com: Build a test to capture the FAMIX API problems with Java systems http://code.google.com/p/moose-technology/issues/detail?id=632
These are now fixed.
-
moose-technology＠googlecode.com