Skip to main content
Version: 1.14.0

3. Functional Testing and Debugging

3.1 Functional Testing​

The distribution kit contains a script for automatic check of OMNI Platform functionality. Specify the Platform URL http://<ingress.rules.gateway.host>, user email and run the command (a test lasts for about 1 minute):

./cli.sh platform test - <platform url> <user_email> –-show-trace

After running the script, the console will ask for a password. Enter the user password and press the Enter key. After the tests are completed successfully, the console will display the following text:

Test data prepared successfully
----------------------------------------------------------------------------------------------------
create_search_profile test started
create_search_profile test succeeded
----------------------------------------------------------------------------------------------------
Test data deleted successfully

3.2 Debugging​

If the service doesn't work correctly, you can get the logs by running the command below, where you need to set the pod name:

kubectl logs $POD_NAME

You can also get the logs of the previous launch attempt:

kubectl logs $POD_NAME --previous

Or through the Events section in the output of the command below:

kubectl describe pod $POD_NAME

3.3 Helpful Commands​

Installing OMNI Platform release:

./cli.sh platform install

Deleting OMNI Platform release:

./cli.sh platform uninstall

Starting the license server:

sudo service floatingserver start

Stopping the license server:

sudo service floatingserver stop