docs(STONEINTG-900): Document the standardized test result outputs for end users

Signed-off-by: Jiri Sztuka <[email protected]>

Author: jsztuka

modules/testing/images/vulnerabilities.png

@@ -10,6 +10,7 @@
 **** xref:integration/choosing-contexts.adoc[Choosing when to run certain Integration Tests]
 **** xref:integration/accessing-private-repositories.adoc[Accessing Pipelines and Tasks in Private Repositories]
 **** xref:integration/periodic-integration-tests.adoc[Triggering Periodic Integration Tests]
+**** xref:integration/standardized-outputs.adoc[Standardized outputs]
 **** Snapshots
 ***** xref:integration/snapshots/working-with-snapshots.adoc[Working with Snapshots]
 ***** xref:integration/snapshots/override-snapshots.adoc[Creating an override snapshot]

modules/testing/nav.adoc

@@ -219,3 +219,16 @@ When the new build is finished, complete the following steps in the {ProductName
 . On the *Details* page, see if the test succeeded for that component. Select the other tabs to view more details.
 
 .. If you used our example script, switch to the *Logs* tab and verify that the test printed “Hello world!”.  
+
+== Standardized test result
+
+In examples above, you can see TEST_OUTPUT result being used as standardized output. This is a tekton result test outcome in json format.
+TEST_OUTPUT example:
+----
+{"result":"SUCCESS","timestamp":"2025-04-02T01:45:00+00:00","note":"Task clair-scan completed: Refer to Tekton task result SCAN_OUTPUT for vulnerabilities scanned by Clair.","namespace":"default","successes":1,"failures":0,"warnings":0}
+----
+
+For more information about standardized tekton results in konflux, please visit
+link: https://konflux-ci.dev/architecture/ADR/0030-tekton-results-naming-convention.html[Tekton Results Naming Convention]
+or
+xref:testing:integration/standardized-outputs.adoc[Standardized outputs]

modules/testing/pages/integration/creating.adoc

@@ -0,0 +1,23 @@
+= Standardized outputs
+
+Konflux is using standardized outputs in various places, this part of docs will provide more detail information about it.
+Each one of the results described below is rendered in the UI, you simply click on task name and panel with details is showed
+containing all results from the task. 
+
+== TEST_OUTPUT
+
+Each tekton task in build pipelinerun provides TEST_OUTPUT result [json] that sumarizes its outcome. It's then being evaluated by Conforma team whether the product can be released or not.
+
+This result type can be also used in integration test pipelines and tasks where it can be parsed by the integration service when deciding the outcome of the integration test. This means you can use it to fail individual test tasks by emitting this result instead of failing the task and stopping the entire pipeline. With this approach it is possible to run multiple tests within the same pipeline and pass or fail them individually.
+
+== SCAN_OUTPUT
+
+This one is located within build definition task clair scan. SCAN_OUTPUT result[json] is displayed in different manner than TEST_OUTPUT, but it serves the same purpose.
+It additionaly displays found vulnerabilities, patched(RHSA fix) and unpatched ones.
+
+image::vulnerabilities.png[role="border" alt="Vulnerabilities"]
+
+== IMAGES_PROCESSED
+
+Result[json] for multiple images (i.e. multi-arch images), primary function to disambiguate the image references corresponding to the other Tekton results.
+