Ladybug tests

MANUAL_TEST.md

@@ -13,10 +13,14 @@ Ladybug is tested by [automated tests](./README.md#cicd). These automated tests
   - [Configure Frank!Runner to run backend - Nexus release](#configure-frankrunner-to-run-backend-nexus-release)
   - [Start up - Nexus release](#start-up-nexus-release)
 - [Tests](#tests)
+  - [Test 5: Version numbers](#test-5-version-numbers)
   - [Test 10: Debug tab tree view, layout of checkpoints](#test-10-debug-tab-tree-view-layout-of-checkpoints)
   - [Test 20: Views in the debug tree](#test-20-views-in-the-debug-tree)
   - [Test 30: Authorization](#test-30-authorization)
   - [Test 40: Stubbing](#test-40-stubbing)
+  - [Test 50: Toast messages](#test-50-toast-messages)
+  - [Test 60: Rerun and compare](#test-60-rerun-and-compare)
+  - [Test 70: Low-level error should be shown](#test-70-low-level-error-should-be-shown)
 
 # Preparations
 
@@ -91,6 +95,10 @@ In this case, the `build.properties` files you have in subdirectories of `work/f
 
 # Tests
 
+### Test 5: Version numbers
+
+**Step 10:** Open ladybug. Check whether the version numbers of the ladybug backend and the ladybug frontend are shown somewhere.
+
 ### Test 10: Debug tab tree view, layout of checkpoints
 
 **Step 10:** In the Frank!Framework, use "Test a Pipeline" to run adapter "processXml" with input message `<person>Jan Smit</person>
@@ -99,16 +107,20 @@ In this case, the `build.properties` files you have in subdirectories of `work/f
 **Step 20:** In the Frank!Framework, use "Test a Pipeline" to run adapter "processXml" with input message `<person2>Jan Smit</person2>
 `.
 
-**Step 30:** In Ladybug (on port 4200), go to the Debug tab. Press the refresh button to refresh the table of reports. Check that the following are true:
+**Step 30:** In Ladybug, go to the Debug tab. Press the refresh button to refresh the table of reports. Check that the following are true:
 
 * The last two reports have in their "Name" column the value `Pipeline processXml`.
 * The second-last report is green to indicate success.
 * The last report is red to indicate failure.
 
-**Step 40:** Open the second-last report (the successful one). It should appear in the tree view below the table. Check that at least the following nodes exist with the shown indentation:
+**Step 40:** Open the second-last report (the successful one). It should appear in the tree view below the table.
+
+**Step 43:** Check that not the root node of the report but the child node right below that is selected by default.
+
+**Step 46:** Check that at least the following nodes exist with the shown indentation:
 
 * Directory icon `Pipeline processXml`.
-  * Right arrow `Pipeline processXml`.
+  * Right arrow `Pipeline processXml` (selected by default, **step 43**).
     * Right arrow `Pipe validate`.
       * Information `Pipe validate`.
       * Left arrow `Pipe validate`.
@@ -228,3 +240,41 @@ TODO: Then continue writing this test.
 **Step 50:** Restart the FF! and rerun the two reports. The one with stubbed senders should succeed. The one without stubbing should fail.
 
 **Step 60:** Stop the FF! and undo the change to `<ladybug-test>/manual-test/configurations/processXml/getName.xsl`.
+
+### Test 50: Toast messages
+
+**Step 10:** Go to the debug tab and select a report. Press the delete button.
+
+**Step 20:** There should appear a toast message to the bottom right saying "data loaded!". Click that toast message before it disappears.
+
+**Step 30:** A larger window should appear with the toast message in it and possibly more detailed information.
+
+### Test 60: Rerun and compare
+
+**Step 10:** Run Adapter1a. Copy the resulting report to the test tab. Press edit. Change the message of the last checkpoint. Save.
+
+**Step 20:** In the test tab, rerun the edited report. It should produce a negative result (red message to the right).
+
+**Step 30:** Press compare.
+
+**Step 40:** There should be two tree views, one to the left and one to the right. At both sides, all nodes except the last should be black. The last node at both sides should be red.
+
+**Step 50:** Check that the node comparison algorithm is "Path".
+
+**Step 60:** Select nodes on the left and on the right. Each time a node is selected on one side, the corresponding node should be selected on the other side.
+
+**Step 70:** For each selection of nodes, check that the corresponding values are shown to the bottom. Check that if the values on both sides are different, the differences are highlighted.
+
+**Step 80:** Change the node comparison algorithm to "None". Select nodes to the left and to the right. Check that selecting a node on one side does not affect the other side.
+
+### Test 70: Low-level error should be shown
+
+This test should be executed with the ladybug test webapp. The maintainers of Ladybug know how to start this, so documenting the required preparations is postponed.
+
+**Step 10:** Start the ladybug test webapp and create a report.
+
+**Step 20:** Stop ladybug.
+
+**Step 30:** Locate the directory that holds the stored ladybug reports (should be a subdir of `data`). Rename it.
+
+**Step 30:** Restart ladybug. Check that an error message is shown.