validations_common.tests.callback_plugins.test_validation_json module

test_validation_json

Tests for validation_json callback plugin.

class validations_common.tests.callback_plugins.test_validation_json.TestValidationJson(*args: Any, **kwargs: Any)

Bases: validations_common.tests.base.TestCase

setUp()

test_callback_instantiation()

Verifying that the CallbackModule is instantiated properly. Test checks presence of CallbackBase in the inheritance chain, in order to ensure that folowing tests are performed with the correct assumptions.

test_getattribute_invalid()

Attempting to call __getattribute__ method with invalid attribute name should result in exception.

test_getattribute_valid_listed(mock_record_task_result)

All of the listed attribute names are checked. The __getattribute__ method returns a partial, the args supplied to it are stored a tuple.

test_getattribute_valid_unlisted(mock_record_task_result)

Since the validation_json.CallbackModule defines it’s own __getattribute__ method, we can’t use dir to safely check the name of attributes individually, as dir itself uses the __getattribute__ method. Instead we check if the namespace of the CallbackBase class is a subset of validation_json.CallbackModule namespace.

test_new_play(mock_play, mock_play_name, mock_play_uuid)

From the callback point of view, both Play and Task are virtually identical. Test involving them are therefore also very similar.

test_new_task(mock_task, mock_task_name, mock_task_uuid)

From the callback point of view, both Play and Task are virtually identical. Test involving them are therefore also very similar.

test_record_task_result(mock_secondsToStr, mock_time)

Method CallbackModule._record_task_result works mostly with dicts and performs few other calls. Therefore the assertions are placed on calls to those few functions and the operations performed with supplied MagicMock objects.

test_v2_playbook_on_handler_task_start(mock_task, mock_new_task)

CallbackModule methods v2_playbook_on_task_start and v2_playbook_on_handler_task_start are virtually identical. The only exception being is_conditional parameter of the v2_playbook_on_task_start, which isn’t used by the method at all. Therefore both of their tests share documentation. In order to verify methods functionality we first append a dummy result at the end of CallbackModule.result list. Simple dictionary is more than sufficient.

test_v2_playbook_on_no_hosts_matched(mock_open, mock_json_dumps)

test_v2_playbook_on_play_start(mock_play, mock_new_play)

test_v2_playbook_on_start(mock_loader, mock_path_splitext, mock_path_basename)

test_v2_playbook_on_stats(mock_open, mock_json_dumps)

test_v2_playbook_on_task_start(mock_task, mock_new_task)

CallbackModule methods v2_playbook_on_task_start and v2_playbook_on_handler_task_start are virtually identical. The only exception being is_conditional parameter of the v2_playbook_on_task_start, which isn’t used by the method at all. Therefore both of their tests share documentation. In order to verify methods functionality we first append a dummy result at the end of CallbackModule.result list. Simple dictionary is more than sufficient.

test_val_task()

_val_task and _val_task_host methods are virtually identical. Their tests are too.

test_val_task_host()

_val_task and _val_task_host methods are virtually identical. Their tests are too.

validations_common.tests.callback_plugins.test_validation_json.is_iso_time(time_string)

Checks if string represents valid time in ISO format, with the default delimiter. Regex is somewhat convoluted, but general enough to last at least until the 9999 AD.

Returns

True if string matches the pattern. False otherwise.