adopted new KeePassKit behaviour for updateToNode on test

Signed-off-by: michael starke <michael.starke@hicknhack-software.com>
This commit is contained in:
michael starke
2015-10-05 16:27:57 +02:00
parent 3b24904f7e
commit 9ca87ba2b9

View File

@@ -340,10 +340,8 @@
XCTAssertFalse(_undoManager.canUndo, @"Undo stack is empty");
XCTAssertFalse(_undoManager.canRedo, @"Redo stack is empty");
KPKEntry *invalid = [_tree createEntry:_tree.root];
KPKEntry *copy = [_entryA copy];
XCTAssertThrows([_entryA updateToNode:invalid], @"Updating to a wrong node is not allowed");
XCTAssertEqualObjects(_entryA, copy, @"Entry a has no changes after updateToNode was called with wrong node argument");
XCTAssertThrows([_entryA updateToNode:_groupA], @"Updating Entry to Group is not possible");
XCTAssertThrows([_groupA updateToNode:_entryA], @"Updating Group to Entry is not possible");
XCTAssertFalse(_undoManager.canUndo, @"Undo stack is empty after failed update");
XCTAssertFalse(_undoManager.canRedo, @"Redo stack is empty after failed update");