From d69f16c537db03e17b8d41ec681b12fb8fd866ac Mon Sep 17 00:00:00 2001 From: "gtrivedi@redhat.com" Date: Tue, 14 May 2024 13:10:53 +0530 Subject: [PATCH] Moved content for integration tests --- .../how-tos/testing/integration/adding.adoc | 47 ++++++++++++++++++- 1 file changed, 46 insertions(+), 1 deletion(-) diff --git a/docs/modules/ROOT/pages/how-tos/testing/integration/adding.adoc b/docs/modules/ROOT/pages/how-tos/testing/integration/adding.adoc index ff9fc0bc..0a4b67da 100644 --- a/docs/modules/ROOT/pages/how-tos/testing/integration/adding.adoc +++ b/docs/modules/ROOT/pages/how-tos/testing/integration/adding.adoc @@ -1 +1,46 @@ -= Adding an integration test \ No newline at end of file += Adding an integration test + +In {ProductName}, you can add integration tests to verify that the individual components of your application integrate correctly, forming a complete and functional application. {ProductName} runs these integration tests on the container images of components before their deployment. + +.Prerequisites + +* You have created an application in {ProductName}. + +.Procedure + +Complete the following steps in the {ProductName} console: + +. Open an existing application and go to the *Integration tests* tab. + +. Select *Add integration test*. + +. In the *Integration test name* field, enter a name of your choosing. + +. In the *GitHub URL* field, enter the URL of the GitHub repository that contains the test you want to use. +. Optional: If you want to use a branch, commit, or version other than the default, specify the branch name, commit SHA, or tag in the *Revisions* field. + +. In the *Path in repository* field, enter the path to the `.yaml` file that defines the test you want to use. +. Optional: To allow the integration tests to fail without impacting the deployment and release process of your application, you can choose to select *Mark as optional for release*. + ++ +NOTE: By default, all integration test scenarios are mandatory and must pass. A failing integration test marks the application snapshot as failed, preventing its deployment and release. However, if you have selected *Mark as optional for release*, a failure in this test won't hinder the deployment and release of the application snapshot. + +. Select *Add integration test*. + +. Start a new build for any component you want to test. + +.. For components using the default build pipeline, go to the *Components* tab, select the three dots next to the name of the component, and select *Start new build*. + +.. For components with an upgraded build pipeline, make a commit to their GitHub repository. + +.Verification + +When the new build is finished: + +. Go to the *Integration tests* tab and select the highlighted name of your test. + +. Go to the *Pipeline runs* tab of that test and select the most recent run. + +. On the *Details* page, you can see if the test succeeded for that component. Navigate to the other tabs for more details. + +