Allow EMF Tests to run in p2 build #167
Comments
ndoschek
added a commit
that referenced
this issue
Jan 10, 2023
Due to the update of the mockito versions, we are now able to run the emf tests again also in the p2 build If emf.tests are running via p2 the test resources are saved differently, hence let's execute tests on resources in a .temp directory to avoid having git changes on each p2 build. Resolves #167
ndoschek
added a commit
that referenced
this issue
Jan 11, 2023
Due to the update of the mockito versions, we are now able to run the emf tests again also in the p2 build If emf.tests are running via p2 the test resources are saved differently, hence let's execute tests on resources in a .temp directory to avoid having git changes on each p2 build. Resolves #167
ndoschek
added a commit
that referenced
this issue
Jan 11, 2023
Due to the update of the mockito versions, we are now able to run the emf tests again also in the p2 build If emf.tests are running via p2 the test resources are saved differently, hence let's execute tests on resources in a .temp directory to avoid having git changes on each p2 build. Resolves #167
ndoschek
added a commit
that referenced
this issue
Jan 11, 2023
Due to the update of the mockito versions, we are now able to run the emf tests again also in the p2 build If emf.tests are running via p2 the test resources are saved differently, hence let's execute tests on resources in a .temp directory to avoid having git changes on each p2 build. Resolves #167
ndoschek
added a commit
that referenced
this issue
Jan 12, 2023
Due to the update of the mockito versions, we are now able to run the emf tests again also in the p2 build If emf.tests are running via p2 the test resources are saved differently, hence let's execute tests on resources in a .temp directory to avoid having git changes on each p2 build. Resolves #167
ndoschek
added a commit
that referenced
this issue
Jan 12, 2023
Due to the update of the mockito versions, we are now able to run the emf tests again also in the p2 build If emf.tests are running via p2 the test resources are saved differently, hence let's execute tests on resources in a .temp directory to avoid having git changes on each p2 build. Resolves #167
ndoschek
added a commit
that referenced
this issue
Jan 12, 2023
- Update to mockito 4.9.0 - Due to the update of the mockito versions, we are now able to run the emf tests again also in the p2 build - New version is not available via orbit, consume missing via org.eclipse.emfcloud.modelserver.tests bundle - Add mockito dependency libs to tests bundle - If emf.tests are running via p2 the test resources are saved differently, hence let's execute tests on resources in a .temp directory to avoid having git changes on each p2 build. Resolves #167
ndoschek
added a commit
that referenced
this issue
Jan 13, 2023
- Update to mockito 4.9.0 - Due to the update of the mockito versions, we are now able to run the emf tests again also in the p2 build - New version is not available via orbit, consume missing via org.eclipse.emfcloud.modelserver.tests bundle - Add mockito dependency libs to tests bundle - If emf.tests are running via p2 the test resources are saved differently, hence let's execute tests on resources in a .temp directory to avoid having git changes on each p2 build. Resolves #167
ndoschek
added a commit
that referenced
this issue
Jan 13, 2023
- Update to mockito 4.9.0 - Due to the update of the mockito versions, we are now able to run the emf tests again also in the p2 build - New version is not available via orbit, consume missing via org.eclipse.emfcloud.modelserver.tests bundle - Add mockito dependency libs to tests bundle - If emf.tests are running via p2 the test resources are saved differently, hence let's execute tests on resources in a .temp directory to avoid having git changes on each p2 build. Resolves #167
ndoschek
added a commit
that referenced
this issue
Jan 13, 2023
- Update to mockito 4.9.0 - Due to the update of the mockito versions, we are now able to run the emf tests again also in the p2 build - New version is not available via orbit, consume missing via org.eclipse.emfcloud.modelserver.tests bundle - Add mockito dependency libs to tests bundle - If emf.tests are running via p2 the test resources are saved differently, hence let's execute tests on resources in a .temp directory to avoid having git changes on each p2 build. Resolves #167
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently we do not build the
org.eclipse.emfcloud.modelserver.emf.teststests when building for p2 (mvn clean verify -Pp2) as there was some issue with Mockito not being able to mock certain classes. Running the tests from Eclipse, however, works fine.The goal of this task is to ensure that the tests can also be run with the p2 maven build.
The text was updated successfully, but these errors were encountered: