geonode.tests.test_utils

Classes

TestCopyTree
TestFixupShp
TestSetAttributes
TestSupportedTypes	A class whose instances are single test cases.
TestRegionsCrossingDateLine	A class whose instances are single test cases.

Module Contents

class geonode.tests.test_utils.TestCopyTree

Bases: geonode.tests.base.GeoNodeBaseTestSupport

test_backup_of_root_files_with_modification_dates_meeting_less_than_filter_criteria(patch_isdir, patch_listdir, patch_getmtime, patch_shutil_copy2)

Test that all root directories whose modification dates meet the ‘data_dt_filter’ less-than iso timestamp are backed-up successfully

test_skipped_backup_of_root_files_with_modification_dates_not_meeting_less_than_filter_criteria(patch_isdir, patch_listdir, patch_getmtime, patch_shutil_copy2)

Test that all root directories whose modification dates do not meet the ‘data_dt_filter’ less-than iso timestamp are not backed-up

test_backup_of_root_files_with_modification_dates_meeting_greater_than_filter_criteria(patch_isdir, patch_listdir, patch_getmtime, patch_shutil_copy2)

Test that all root directories whose modification dates do not meet the ‘data_dt_filter’ greater-than iso timestamp are backed-up successfully

test_skipped_backup_of_root_files_with_modification_dates_not_meeting_greater_than_filter_criteria(patch_isdir, patch_listdir, patch_getmtime, patch_shutil_copy2)

Test that all root directories whose modification dates do not meet the ‘data_dt_filter’ less-than iso timestamp are not backed-up

test_backup_of_child_directories(patch_isdir, patch_listdir, patch_getmtime, patch_shutil_copytree, path_os_exists)

Test that all directories which meet the ‘ignore criteria are backed-up’

class geonode.tests.test_utils.TestFixupShp

Bases: geonode.tests.base.GeoNodeBaseTestSupport

test_fixup_shp_columnnames()

class geonode.tests.test_utils.TestSetAttributes

Bases: geonode.tests.base.GeoNodeBaseTestSupport

setUp()

test_set_attributes_creates_attributes()

Test utility function set_attributes() which creates Attribute instances attached to a Dataset instance.

class geonode.tests.test_utils.TestSupportedTypes(methodName='runTest')

Bases: unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

test_should_append_additional_type_if_config_is_provided()

test_should_replace_the_type_id_if_already_exists()

class geonode.tests.test_utils.TestRegionsCrossingDateLine(methodName='runTest')

Bases: unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

test_region_across_dateline_do_not_intersect_areas_outside()

test_region_wkt_multipolygon_if_across_idl()