Your build pipeline defines several tests that may fail when third-party applications are unavailable. Ensure the pipeline can still complete successfully if those third-party applications are unavailable. What should you do?

Configuring flaky tests allows the pipeline to tolerate intermittent test failures without failing the entire build. This is crucial when tests depend on external services that might be temporarily unavailable. The pipeline will mark these tests as "flaky" and continue execution, preventing unnecessary build failures while still providing visibility into potential issues. Parallel jobs improve execution speed but don't address test stability. Increasing the test pass percentage is a goal, not a configuration to handle external dependencies. The Requirements quality widget is for tracking requirements coverage, not for managing test execution behavior.