SDK Integration Tests

The Kount RIS Java SDK comes with a suite of integration tests, covering the various request modes and service behavior. Some of the internal SDK functionality is also covered by those test cases.

Each Kount client, upon negotiating an NDA, is going to receive the following configuration data:

• RIS server URL
• Merchant ID
• API key
• Configuration key used within the SDK

Setting configuration key

In order to run the set of integration tests, it is required to correctly configure the key as a system variable for the compile/build process. We've provided two options to configure it locally:

• editing the sdk-integration-tests/pom.xml. This option is suitable for multiple tests running (although this could be considered as DDoS attack by the RIS server and therefore ignored). Uncomment the following lines in the pom.xml:
  • <!--config.key>configuration key here</config.key-->

   <!--build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-surefire-plugin</artifactId>
        <version>2.20</version>
        <configuration>
          <systemPropertyVariables>
            <kount.config.key>${config.key}</kount.config.key>
          </systemPropertyVariables>
        </configuration>
      </plugin>
    </plugins>
  </build-->

• add extra parameters to the Maven command line when running (OK for one-time test)
  mvn -U clean install -DargLine="-Dkount.config.key='configuration key here'"

If everything is configured correctly, the Maven command end message should say Success.

⚠️ If characters like ", \``, or '` are present in the configuration key value, those need to be escaped on the command line.

Basic Connectivity Test

Within the test suite, there's a test class named com.kount.ris.BasicConnectivityTest. Inside, there are two test cases, expecting predefined results (check the Predictive Response section). This class can easily be edited with your personal merchant data in order to test correct connectivity to the RIS server.
Fields that need to be modified are:

• MERCHANT_ID
• SERVICE_URL
• the location of the API key (best set as a resource file)

The configuration key value is set as described above.

If you want to run the tests from within the IDE, the configuration key needs to be set as a VM argument in the corresponding run configuration.

-Dkount.config.key="configuration key here"