Unit tests and integration tests distinction

[bva]

With gradle plugin, we have three tasks for tests, one for integration tests (systemtest) and two others for unit testing of perl and java (GWT) code (unittest & test).

Solely purpose of unit tests is to make them run as fast as possible, and independent from working environment (Flow Server & Agent).

For integration testing (which use EF & Agent), we have separate tests, which are based on ntest framework, and which we are actively using in our CI procedures.

I've made modifications to support java-based system tests in or new CI system, but please, note, that system tests is more preferred way for us to do integration testing. So, in future, please, use ntest framework. Ask me, if you have any questions on how to setup CI tests with ntest.

[urvashisingh]

@bva Vitaliy, Could you provide exact steps for running the java-based system tests in the CL builds?
Is there an expected location for the files required for running the system tests? Should the location for the java/groovy test classes for system tests be registered under a different sourceset in build.gradle?

[bva]

@urvashisingh

Sure. I need:

1. As per Dockerfile for CI procedure #39, Dockerfile for deploying server-side components (Chef server).
2. List of rpm packages that i need to install on agent machine (CentOS 7)
3. Sample of Configurations.json file, as it's not clear, what 'user environment specific arguments' i should change in that file.

[bva]

Java tests in this plugin uses EF server & agent (that's what we have in CI), and Chef. But, we don't have Chef environment to run them. Hence, first we need to setup working environment. For external applications we use docker, and for agents we use prebuilt VM image with CentOS. That's why we need first two steps to be done before talking about test configuration files.