Re: Tips for testing

Great, thank you very much! On Monday, February 8, 2016, Maximilian Michels wrote: > Hi Stefano, > > Thanks for the pull request. > > You may use the following to only run tests from flink-runtime: > > mvn verify -pl flink-runtime > > Alternatively, change to the flink-runtime directory and run

Re: Tips for testing

Hi Stefano, Thanks for the pull request. You may use the following to only run tests from flink-runtime: > mvn verify -pl flink-runtime Alternatively, change to the flink-runtime directory and run "mvn verify" from there. This assumes Flink has been built and installed locally before. If not, M

Re: Tips for testing

Hi Maximilian, thanks for the tips. I've already opened a PR (here ). Is there a way from the command line to do what can be done with IntelliJ? I mean build only what's needed and run a specific test? I've tried `mvn test` but it skips the build phase an

Re: Tips for testing

Hi Stefano, 1) Please open a pull request. If the String depends on the locale, this looks like a bug. 2) "mvn clean install" is the way to go for the complete check. If you only want to run certain tests, selecting and running them from IntelliJ works pretty well. In addition, it is nice to push

Re: Tips for testing

Hi! I basically test with "mvn clean install" as well. Greetings, Stephan On Sat, Feb 6, 2016 at 10:31 PM, Stefano Baghino < stefano.bagh...@radicalbit.io> wrote: > Hi everybody, > > as I've recently started contributing to Flink, I'd like to ask you a few > tips on how you normally run the te

Tips for testing

Hi everybody, as I've recently started contributing to Flink, I'd like to ask you a few tips on how you normally run the tests to ensure that everything runs smoothly before pushing the code to CI. First, I'd like to point out two issues in particular I had: 1. some test suites (KMeansWithBro