DaaSJavaApiCore tests¶

Some of these tests require the Administrator to do something. This is shown as:

Administrator: <must do this task and here are the detailed commands to be used>

Publisher tests¶

The below 8 tests are specifically designed to test the Publisher Object in the DaaS Java API code.

Note

These are Unit Tests and, as such, test the integrity of the Java API package in isolation._

1. hasSubscribers_returns_false_if_publisher_has_no_subscribers()

If the list of subscribers in the publisher is empty then return false. (The "subscriber" is the KX Refinery Tickerplant)

Test outcome = False to pass.

2. hasSubscribers_returns_true_if_publisher_has_subscribers()

If the list of subscribers in the publisher is not empty then return true.

Test outcome = True to pass.

3. publish_data_cannot_contain_non_char_arrays()

The publisher can only publish one row at a time, the test contains an array of 2 syms, therefore should fail.

Test outcome = Argument Exception, which results in a pass for the test.

4. publish_data_can_contain_char_arrays()

This test checks that the publisher can publish data containing char arrays (which are the equivalent of Strings in kdb+/q) Test outcome = No Exception, which results in a pass for the test.

5. table_parameter_cannot_be_empty()

The publisher has a table parameter which is the destination of the data, if this is empty ('') the publisher should not work.

Test outcome = Argument Exception, which results in a pass for the test

6. table_parameter_cannot_be_null()

The publisher has a table parameter which is the destination of the data, if this is null the publisher should not work.

Test outcome = Argument Exception, which results in a pass for the test

7. waitForSubscribers_returns_false_if_subscription_added_after_timeout()

The publisher has a wait for subscribers method that has a timeout, this test checks if a subscriber is added after the timeout is invoked.

Test outcome = False is returned as subscriber added after timeout, which results in a pass for the test.

8. waitForSubscribers_returns_true_if_subscription_added_before_timeout()

The publisher has a wait for subscribers method that has a timeout, this test checks if a subscriber is added before the timeout is invoked.

Test outcome = True is returned as subscriber added before timeout, which results in a pass for the test.

Query results tests¶

The below 6 tests are specifically designed to test the Query Results Object in the DaaS Java API code:

Note

These are Unit Tests and, as such, test the integrity of the Java API package in isolation._

9. cannot_pass_a_null_parameter()

The Query Result object has a flip parameter which is the representation of a table. If this is null the Query Result should not work.

Test outcome = Argument Exception, which results in a pass for the test

10. column_name_ordering_is_preserved()

The Query Result object has column names that are exposed by the flip object. This ordering should be preserved as per the flip object.

Test outcome = True (x3), which results in a pass for the test

11. column_type_ordering_is_preserved()

The Query Result object has column types that are exposed by the flip object, these types (inc ordering) should be preserved as per the flip object.

Test outcome = True (x3), which results in a pass for the test

12. getColumnType_method_works()

The Query Result object has column type method which returns the type of the column in question. This is then checked after exposure from the flip object to make sure they are the same (order is not essential).

Test outcome = True (x3), which results in a pass for the test

13. indexers_work_as_expected()

The Query Result object has Indexers which are methods of pulling out data using arrays to retrieve data in multiple ways (cell/row/etc). This test checks that the values visible dependant on passing (string, int) or (int, int) are as expected.

Test outcome = True (x4), which results in a pass for the test

14. works_with_empty_flip()

This test makes sure that if an empty flip object is returned, the API does not error.

Test Outcome = True (x2) number rows and columns = 0 and no exceptions generated, which results in a pass for the test

Service tests¶

The below 14 tests are specifically designed to test the Service Object in the DaaSAPICore code:

15. can_run_getTicks_query()

The Service object has a runQuery method to run basic q functions that are available in the Gateway. This test proves the q function can be run from the API.

Test Outcome = number of rows greater than 0 and no exceptions are produced, which results in a pass for the test. Assumption is that there are >0 rows in the q Function if the HDB is working properly.

The default values supplied with the package will look for the following data in the HDB:

These may need to be changed depending on the data in the Kx Refinery system being connected to :

"symList" = "AZN.L"
"dataType" = "trade"
"startDate" = Date(1551312000000l)
"endDate" = Date(1551312000000l)
"assetClass" = "equity"

16. cannot_create_service_with_invalid_host()

The Service object has the ability to be instantiated with the details that exist in the app.config. This test is to show that if an invalid host is used, an exception is thrown.