Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Build a test to capture the FAMIX API problems with Java systems #632

Closed
seandenigris opened this issue Aug 3, 2015 · 4 comments
Closed

Build a test to capture the FAMIX API problems with Java systems #632

seandenigris opened this issue Aug 3, 2015 · 4 comments

Comments

@seandenigris
Copy link
Contributor

Originally reported on Google Code with 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.

Reported by tudor@tudorgirba.com on 2011-05-25 07:46:05
@seandenigris
Copy link
Contributor Author 

We now have VerveineJMooseFinderTest that capture the Moose Finder failures for the
test_src from VerveineJ.

Now, we just need to fix them :)

Reported by tudor@tudorgirba.com on 2011-05-25 08:57:00

@seandenigris
Copy link
Contributor Author 

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.

Reported by tudor@tudorgirba.com on 2011-05-25 10:32:05

@seandenigris
Copy link
Contributor Author

Reported by jannik.laval on 2011-06-23 19:43:30

  • Labels added: Milestone-4.6
  • Labels removed: Milestone-4.5

@seandenigris
Copy link
Contributor Author 

These are now fixed.

Reported by tudor@tudorgirba.com on 2011-07-01 21:30:24

  • Status changed: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@seandenigris