No Code Changes Policy

This policy empowers organizations to strategically handle builds without code alterations.

• Understand the reason: Analyze the common reasons for creating builds without code changes (e.g., configuration updates, test modifications).

• Make informed decisions: Choose between:

  • Run all tests: If most non-code-change builds involve significant configuration or test updates (e.g., new test suite or major changes in existing tests).

  • Skip all tests: If these builds are primarily for minor changes (e.g., test name adjustments) or lack a clear pattern.

Important!

• Tailor policy settings based on your build patterns.

• Evaluate savings after using TIA for a while. If "Run All" is frequently used and savings are low, consider adjusting for efficiency.

Setting the Policy

• Define a default policy: Apply to all apps and test stages with TIA enabled via the SeaLights Settings / TIA page.

• Customize for specific needs: Tailor the policy for individual apps, branches, and test stages through the Settings page or the Test Optimization - Build Breakdown page (using the TIA configuration button).

By leveraging both pre-defined and customizable policies, you can ensure SeaLights Test Optimization delivers recommendations that perfectly align with your unique testing strategy.