System Tests

System Tests have been added to validate the global cache entities. The following table details each system test action.

Action Description
File permissions @ <HOST_NAME>:<PORT_NUMBER>

Checks for create and delete permissions within the participating nodes.

Note: Based on the number of participating nodes, file permission test for every individual nodes will be listed.
PD4ML Config check @ <HOST_NAME>:<PORT_NUMBER>

Checks for the PD4ML TTF Font Directory within the participating nodes.

Note: Based on the number of participating nodes, PD4ML Config check for every individual nodes will be listed.
Version Check Checks for the versions in all the participating nodes within the cluster, including the Nginx server.
webProxyInfo cache Checks for the number of participating Nginx servers.
databaseInfo cache Checks for the number of databases attached to the instance.
filestoreInfo cache Checks for the number of file storage attached to the instance.
componentProperties cache Checks for the number of production servers marked as Dedicated.
searchEngine cache Checks for the number of search servers attached to the instance.
passwordActivationContext cache Validates password value against the database and runtime cache.
componentStats cache Checks for the number of components participating in the cluster.
databaseStats cache Checks for the number of databases attached to the instance against the runtime cache.
prodRuntimeInfo cache Checks for the number of production nodes participating within a cluster.
storageStats cache Checks for the number of file storage attached to the instance against the runtime cache.
webProxyStats cache Checks for the number of Nginx servers attached to the instance against the runtime cache.
globalAuthenticationProfile cache Based on the authentication profile, validates password value against the database and runtime cache.
Cache instance [rb_global]

Lists out the cluster state, version and number of participating nodes along with <HOST_NAME>:<PORT_NUMBER> details.

Note: Based on the number of components dedicated to participating nodes, every component's Cache Instance details are listed individually.