DevTools: Implement undo, redo operations for the DOMStorage views.

LayoutTests/inspector/storage-panel-dom-storage-undo-redo-expected.txt

Index: LayoutTests/inspector/storage-panel-dom-storage-undo-redo-expected.txt
diff --git a/LayoutTests/inspector/storage-panel-dom-storage-undo-redo-expected.txt b/LayoutTests/inspector/storage-panel-dom-storage-undo-redo-expected.txt
new file mode 100644
index 0000000000000000000000000000000000000000..a1bde738336d4ed27a72b264e19428654407e0dd
--- /dev/null
+++ b/LayoutTests/inspector/storage-panel-dom-storage-undo-redo-expected.txt
@@ -0,0 +1,74 @@
+This test checks the undo/redo operations are performed correctly on the DOM storage views
+
+
+Running: initialize
+Initialized localStorage and sessionStorage by clearing entries.
+
+Running: undoLocalStorageWithEmptyStack
+LocalStorage contents:[]
+
+Running: redoLocalStorageWithEmptyStack
+LocalStorage contents:[]
+
+Running: localStorageUndoInterlacedWithAddition
+LocalStorage contents:[a1=b1]
+LocalStorage contents:[a1=b1,a3=b3]
+LocalStorage contents:[a1=b1]
+
+Running: addLocalStorageEntries
+LocalStorage contents:[a1=b1,a2=b2]
+
+Running: undoLocalStorageLastAddition
+LocalStorage contents:[a1=b1]
+
+Running: undoSessionStorageWithEmptyStack
+SessionStorage contents:[]
+
+Running: redoSessionStorageWithEmptyStack
+SessionStorage contents:[]
+
+Running: undoLocalStorageBeyondBounds
+The entry a1=b1 is removed and any attempt to undo beyond it shouldn't cause any failure!
+LocalStorage contents:[]
+
+Running: addSessionStorageEntries
+SessionStorage contents:[p1=q1,p2=q2,p3=q3,p4=q4]
+
+Running: redoLocalStorageBeyondBounds
+The entry a1=b1 and a2=b2 is added back and any attempt to redo beyond it shouldn't cause any failure!
+LocalStorage contents:[a1=b1,a2=b2]
+
+Running: undoSessionStorageLastAddition
+SessionStorage contents:[p1=q1,p2=q2,p3=q3]
+
+Running: modifyLocalStorageValues
+LocalStorage contents:[a1=x1,a2=x2]
+
+Running: undoLocalStorageModifications
+LocalStorage contents:[a1=b1,a2=b2]
+
+Running: redoSessionStorageLastAddition
+SessionStorage contents:[p1=q1,p2=q2,p3=q3,p4=q4]
+
+Running: redoLocalStorageModifications
+LocalStorage contents:[a1=x1,a2=x2]
+
+Running: modifySessionStorageEntriesKey
+SessionStorage contents:[m1=q1,m2=q2,m3=q3,m4=q4]
+
+Running: undoLocalStorageModifications
+LocalStorage contents:[a1=b1,a2=b2]
+
+Running: undoSessionStorageKeyModifications
+SessionStorage contents:[p1=q1,p2=q2,p3=q3,p4=q4]
+
+Running: validateMaxUndoRedoStackDepth
+Undo/redo stack depth limit is 20
+Performing 40 actions
+LocalStorage contents:[a10=b10,a11=b11,a12=b12,a13=b13,a14=b14,a15=b15,a16=b16,a17=b17,a18=b18,a19=b19,a1=b1,a20=b20,a2=b2,a3=b3,a4=b4,a5=b5,a6=b6,a7=b7,a8=b8,a9=b9]
+Performing undo operation three times the depth i.e. 60 times but only last 20 operations are undone
+LocalStorage contents:[a10=b10,a1=b1,a2=b2,a3=b3,a4=b4,a5=b5,a6=b6,a7=b7,a8=b8,a9=b9]

[apavlov, 2013/08/05 09:07:15]

How can we validate that this is the correct content of the storage after all
the undo's? You set a1=b1 and a2=b2, while these key-value pairs are already
present in the storage. Should we perhaps perform 40 actions to set xN=yN, so
that they will be distinguishable from the pre-existing key-value pairs?

[vivekg_samsung, 2013/08/05 09:39:49]

Done.

+
+Running: clearDOMStorageAndFinish
+Finished DOMStorage undo/redo tests and cleared localStorage and sessionStorage entries.
+