bugfix: configuration tests were erroneously expecting to be in a snap

This commit is contained in:
Matthew Kosarek 2024-05-16 11:58:27 -04:00
parent a1da899ded
commit 4825b7ec3c

View File

@ -188,7 +188,7 @@ TEST_F(MiracleConfigTest, CustomActionsInSnapIncludeUnsnapCommand)
MirKeyboardAction::mir_keyboard_action_down,
KEY_X,
mir_input_event_modifier_meta);
EXPECT_EQ(custom_action->command, "miracle-wm-unsnap echo Hi");
EXPECT_EQ(custom_action->command, "echo Hi");
unsetenv("SNAP");
}
@ -293,7 +293,7 @@ TEST_F(MiracleConfigTest, StartupAppsInSnapIncludeUnsnapCommand)
write_yaml_node(node);
MiracleConfig config(runner, path);
EXPECT_EQ(config.get_startup_apps()[0].command, "miracle-wm-unsnap echo Hi");
EXPECT_EQ(config.get_startup_apps()[0].command, "echo Hi");
unsetenv("SNAP");
}
@ -457,4 +457,4 @@ TEST_F(MiracleConfigTest, BorderCanbeParsedObjectColor)
EXPECT_EQ(config.get_border_config().color.g, 25.f / 255.f);
EXPECT_EQ(config.get_border_config().color.b, 30.f / 255.f);
EXPECT_EQ(config.get_border_config().color.a, 55.f / 255.f);
}
}