From 1bac7c2b2a91166d42cb56e8c937d6a116d3b46b Mon Sep 17 00:00:00 2001 From: Ghostkeeper Date: Fri, 12 May 2017 16:32:55 +0200 Subject: [PATCH] Don't register registry at ContainerStack class any more The fixture does this for us automatically now. It's not entirely neat since this is not cleaned up afterwards, but it does make sense to put it there in the fixture, logically. Contributes to issue CURA-3427. --- tests/Settings/TestCuraContainerRegistry.py | 1 - 1 file changed, 1 deletion(-) diff --git a/tests/Settings/TestCuraContainerRegistry.py b/tests/Settings/TestCuraContainerRegistry.py index 268ad7fb90..ad79f74dd4 100644 --- a/tests/Settings/TestCuraContainerRegistry.py +++ b/tests/Settings/TestCuraContainerRegistry.py @@ -119,7 +119,6 @@ def test_addContainerBadSettingVersion(container_registry, definition_container) ]) def test_loadTypes(filename, output_class, container_registry): #Mock some dependencies. - UM.Settings.ContainerStack.setContainerRegistry(container_registry) Resources.getAllResourcesOfType = unittest.mock.MagicMock(return_value = [os.path.join(os.path.dirname(os.path.abspath(__file__)), "stacks", filename)]) #Return just this tested file. def findContainers(container_type = 0, id = None):