You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the API-module we find a class PerformanceTest which currently has this TODO:
// TODO Shall this call here also work against a MySQL backend? Seems this should be put into a real Integration Test.
So this should be moved to src/it/java in the respective module. It should then be triggered via the maven-failsafe plugin against one or more site-specific MySQL integration profiles, e.g. UKP or HHN.
The text was updated successfully, but these errors were encountered:
- Adds two different site-specific Maven profiles: `mysql-ukp` and `mysql-hhn`
- Adds Maven configuration for IT-setup (via maven-failsafe-plugin)
- Introduces the new src branch `src/it/java` in wikipedia.api module
- Moves and refactors existing code of `PerformanceTest` and `PerformanceTestPageIterator` to be executable in an IT environment
- Introduces `PerformanceIT` as a true integration test
- Adds MySQL/C3P0 dependencies in test scope to be capable of running against MySQL as if in a production setup
- Corrects integration-test profile setup. By default ITs are switched off now, as regular devs need a build that is passing
- A working mvn commandline (locally or on CI servers) should now add `-Pjacoco -Pintegration-test -Pmysql-ukp`
In the API-module we find a class
PerformanceTest
which currently has this TODO:So this should be moved to
src/it/java
in the respective module. It should then be triggered via the maven-failsafe plugin against one or more site-specific MySQL integration profiles, e.g. UKP or HHN.The text was updated successfully, but these errors were encountered: