Build-Level Merging in SmartUI

---

info

This guide explains how to effectively merge builds in SmartUI for granular control over your visual regression testing workflow.

Build-Level Merging

Build-level merging provides granular control over specific builds, allowing you to merge individual build results and manage your visual regression testing at a more detailed level.

Merge Command

npx smartui merge build --source <source-build> --target <target-build>

Merge Process

1. Build Selection: Identifies the source and target builds
2. Content Merge: Merges the visual regression results
3. Status Update: Updates build statuses
4. Confirmation: Provides merge confirmation

Example Workflow

# Merge specific builds
npx smartui merge build --source build-123 --target build-456

# Merge with status update
npx smartui merge build --source build-123 --target build-456

Merge Behavior

1. Build Merging: Merges the source build into the target build
2. Status Updates: Updates the new merged build status to "approved"
3. Content Updates: Updates target build with merged content
4. Confirmation: Provides detailed merge confirmation
5. Build Naming:
   • For branch merges: merged-branch/<source>-<target>
   • For build merges: merged-build/<sourcebuildname>-<targetbuildname>

Build Merge Strategies

1. Build Promotion Strategy

Scenario: Promoting specific builds across environments

# 1. Merge staging build to production
npx smartui merge build --source staging-build-123 --target prod-build-456


### 2. Feature Build Strategy

**Scenario**: Managing feature-specific builds

```bash
# 1. Merge feature build into main build
npx smartui merge build --source feature-build-789 --target main-build-101


### 3. Hotfix Build Strategy

**Scenario**: Managing hotfix builds

```bash
# 1. Create hotfix build
npx smartui capture --name hotfix-build-202

# 2. Merge into production build
npx smartui merge build --source hotfix-build-202 --target prod-build-456

Best Practices

1. Build Management:

   • Use meaningful build names
   • Document build purposes
   • Regular cleanup of old builds

2. Merge Planning:

   • Plan merges in advance
   • Document merge strategies
   • Establish approval processes

Getting Help

If you encounter any issues with build merging in SmartUI, please contact our support team at support@lambdatest.com.