Ensure Build Pipeline Success with Unavailable Third-Party Applications
Question
You are creating a build pipeline in Azure Pipelines.
You define several tests that might fail due to third-party applications.
You need to ensure that the build pipeline completes successfully if the third-party applications are unavailable.
What should you do?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.D
Requirements traceability is the ability to relate and document two or more phases of a development process, which can then be traced both forward or backward from its origin. Requirements traceability help teams to get insights into indicators such as quality of requirements or readiness to ship the requirement. A fundamental aspect of requirements traceability is association of the requirements to test cases, bugs and code changes.
https://docs.microsoft.com/en-us/azure/devops/pipelines/test/requirements-traceabilityTo ensure that the build pipeline completes successfully if third-party applications are unavailable, you can use the following approach:
B. Configure flaky tests
Flaky tests are tests that fail sporadically, even when the code under test has not changed. Flaky tests can be caused by a variety of factors, such as environmental issues, timing issues, or concurrency issues. To deal with flaky tests, you can configure them in Azure Pipelines so that they are retried automatically when they fail.
To configure flaky tests in Azure Pipelines, you can use the following steps:
Open your build pipeline in Azure Pipelines.
Click on the "Tests" tab.
Locate the tests that might fail due to third-party applications.
Click on the "..." button next to the test and select "Edit".
In the "Edit Test" dialog, select the "Retry" tab.
Enable the "Retry on failure" option and set the number of retries to a suitable value.
Save your changes.
By configuring flaky tests, you can ensure that the build pipeline completes successfully even if the third-party applications are unavailable. When a flaky test fails, it will be retried automatically, and if it passes on a subsequent attempt, the build pipeline will continue. If the flaky test continues to fail after the configured number of retries, the build pipeline will fail.
A. Configure the build pipeline to use parallel jobs: This option is not relevant to the problem statement as it does not address the issue of failing tests due to third-party applications.
C. Increase the test pass percentage: This option is also not relevant to the problem statement as it does not address the issue of failing tests due to third-party applications.
D. Add the Requirements quality widget to your dashboard: This option is not relevant to the problem statement as it is related to tracking and monitoring of requirements quality, and does not address the issue of failing tests due to third-party applications.
