feat(STONEINTG-901): added debugging page for integration tests

docs/modules/ROOT/pages/how-tos/_nav.adoc

@@ -17,6 +17,7 @@
 **** xref:how-tos/testing/integration/adding.adoc[Adding an integration test]
 **** xref:how-tos/testing/integration/creating.adoc[Creating a custom integration test]
 **** xref:how-tos/testing/integration/editing.adoc[Editing integration tests]
+**** xref:how-tos/testing/integration/debugging.adoc[Debugging an integration test]
 **** xref:how-tos/testing/integration/rerunning.adoc[Rerunning an integration test]
 **** xref:how-tos/testing/integration/override-snapshots.adoc[Creating an override snapshot]
 ** xref:how-tos/metadata/index.adoc[Inspecting provenance and attestations]

docs/modules/ROOT/pages/how-tos/testing/integration/debugging.adoc

@@ -0,0 +1,36 @@
+= Debugging Integration Tests
+
+In the event of an integration test scenario failing, there are a number of steps to take in order to debug the issue before rerunning the test in question. These steps are outlined below.
+
+
+.Prerequisites
+- You have a snapshot that has completed all build-time tests. These must be completed before attempting to debug the failed test.
+
+- You have access to the {ProductName} UI in order to view the logs of the failed test.
+
+.Procedure
+
+. Identify the IntegrationTestScenario that has failed
+    * Open the {ProductName} and navigate to Application/your_application_name/activity
+    * Select "Pipeline Runs" under "Activity By"
+    * Your view should look similar to the below image.
+
++
+image::activityview.png[role="border" alt="Activity View"]
+
+. Click on the pipeline run that has a status of "Failed". This will take you to a detailed view of the failed run. 
+
+. Examine the "Log Snippet" section on the right side of this page. It contains the most recent error returned by the integration test. For more comprehensive logs, click on "See Logs". See the below image for reference.
+
++
+image::testfailed.png[role="border" alt="Test Failed"]
+
+. In this example the output suggests that the pipelineRun is missing an expected parameter, "username". To edit the integration test, follow the procedure provided xref:/how-tos/testing/integration/editing.adoc[here].
+
+. Rerun the test by following the steps xref:/how-tos/testing/integration/rerunning.adoc[here].
+
+. Once the test has been rerun, verify that the test has passed by checking the "Pipeline Runs" tab in the {ProductName} console. The status of the test should now be "Succeeded". See the below image for reference.
+
++
+image::successfulretest.png[role="border alt="Successful Retest"]
+

docs/modules/ROOT/pages/how-tos/testing/integration/rerunning.adoc

@@ -18,6 +18,8 @@ See also xref:/how-tos/configuring/rerunning.adoc[Retriggering build pipelines].
 +
 image::snapshot.png[role="border" alt="IntegrationTestScenario Snapshot"]
 
+. To rerun within the UI, click on the three vertical dots on the right side of the details page mentioned above. From the expanded menu, select "Rerun". Alternatively, follow the below steps to rerun via the CLI.
+
 . Label the snapshot with `test.appstudio.openshift.io/run`, assigning the scenario name you wish to rerun as its value.
 
 +