From f19da5cbe2b2d52f42acec333960a1d2686f9435 Mon Sep 17 00:00:00 2001 From: Don Gagne Date: Sat, 29 Sep 2018 09:27:10 -0700 Subject: [PATCH] Fix unit test for new planned home position behavior --- src/MissionManager/MissionControllerTest.cc | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/src/MissionManager/MissionControllerTest.cc b/src/MissionManager/MissionControllerTest.cc index de06cccff..b6b4793c9 100644 --- a/src/MissionManager/MissionControllerTest.cc +++ b/src/MissionManager/MissionControllerTest.cc @@ -135,9 +135,8 @@ void MissionControllerTest::_testAddWaypointWorker(MAV_AUTOPILOT firmwareType) QCOMPARE((MAV_CMD)simpleItem->command(), MAV_CMD_NAV_TAKEOFF); QCOMPARE(simpleItem->childItems()->count(), 0); - // If the first item added specifies a coordinate, then planned home position will be set - bool plannedHomePositionValue = firmwareType == MAV_AUTOPILOT_ARDUPILOTMEGA ? false : true; - QCOMPARE(settingsItem->coordinate().isValid(), plannedHomePositionValue); + // Planned home position should always be set after first item + QVERIFY(settingsItem->coordinate().isValid()); // ArduPilot takeoff command has no coordinate, so should be child item QCOMPARE(settingsItem->childItems()->count(), firmwareType == MAV_AUTOPILOT_ARDUPILOTMEGA ? 1 : 0); -- 2.22.0