|
1 |
| -= Adding an integration test |
| 1 | += Adding an integration test |
| 2 | + |
| 3 | +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. |
| 4 | + |
| 5 | +.Prerequisites |
| 6 | + |
| 7 | +* You have created an application in {ProductName}. |
| 8 | +
|
| 9 | +.Procedure |
| 10 | + |
| 11 | +Complete the following steps in the {ProductName} console: |
| 12 | + |
| 13 | +. Open an existing application and go to the *Integration tests* tab. |
| 14 | + |
| 15 | +. Select *Add integration test*. |
| 16 | + |
| 17 | +. In the *Integration test name* field, enter a name of your choosing. |
| 18 | + |
| 19 | +. In the *GitHub URL* field, enter the URL of the GitHub repository that contains the test you want to use. |
| 20 | +. 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. |
| 21 | + |
| 22 | +. In the *Path in repository* field, enter the path to the `.yaml` file that defines the test you want to use. |
| 23 | +. 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*. |
| 24 | + |
| 25 | ++ |
| 26 | +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. |
| 27 | + |
| 28 | +. Select *Add integration test*. |
| 29 | + |
| 30 | +. Start a new build for any component you want to test. |
| 31 | + |
| 32 | +.. 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*. |
| 33 | + |
| 34 | +.. For components with an upgraded build pipeline, make a commit to their GitHub repository. |
| 35 | + |
| 36 | +.Verification |
| 37 | + |
| 38 | +When the new build is finished: |
| 39 | + |
| 40 | +. Go to the *Integration tests* tab and select the highlighted name of your test. |
| 41 | + |
| 42 | +. Go to the *Pipeline runs* tab of that test and select the most recent run. |
| 43 | + |
| 44 | +. On the *Details* page, you can see if the test succeeded for that component. Navigate to the other tabs for more details. |
| 45 | + |
| 46 | + |
0 commit comments