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

In test extension points are not always found #77

Open
opcoach opened this issue Dec 10, 2018 · 2 comments
Open

In test extension points are not always found #77

opcoach opened this issue Dec 10, 2018 · 2 comments

Comments

@opcoach
Copy link
Owner

opcoach commented Dec 10, 2018

In the class TestExtensionGeneration the checkSampleExtensinoPointStillPresent fails randomly.

It seems to depend on the refresh of the workspace... like if the workspace refresh was not finished when the initGenModel is done.

In initGenModel, we must wait for the workspace update (because we generate new extensions and probably the extension point copy is not possible at this time).

@opcoach
Copy link
Owner Author

opcoach commented Dec 10, 2018

2 solutions :

  • Increase the time delay in com.opcoach.genmodeladdon.core.GenerateDevStructure.refreshWorkspace(). -> to 5 seconds ?
  • Synchronize the jobs and wait of the end for the refresh (may be by catching an event ? ).

@opcoach opcoach closed this as completed in 6dcf492 Jan 2, 2019
@opcoach opcoach reopened this Jan 3, 2019
@opcoach
Copy link
Owner Author

opcoach commented Jan 3, 2019

The fix commit fails if we install GMA in an Eclipse instance (it is always waiting for refresh (launch with -consoleLog)), while it works well in JUnit tests...
Strange...
Must change this and can not deliver the next release with this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant