Before we deploy to production, we should test our changes in a range of scenarios. Those test scenarios aim to cover different edge cases, so we can be confident that our changes behave correctly.
Those edge cases typically arise from diversity in our data. Behavior often varies between different record types or picklist values. When seeding our sandboxes, we need coverage across these picklists and record types so that we have test data for each scenario.
Gearset automatically samples for coverage
When you set up an OR filter on an object, Gearset will automatically include a sample of records with each value, to maximize coverage in the deployment.
In this example Gearset will deploy up to:
100
Accountrecords withIndustry = Construction100
Accountrecords withIndustry = Energy100
Accountrecords withIndustry = Technology
Additional filters on an object are treated as "AND" filters, and apply across all samples.
In this example Gearset will deploy up to:
100
Accountrecords withIndustry = ConstructionandNumberOfEmployees > 100100
Accountrecords withIndustry = EnergyandNumberOfEmployees > 100100
Accountrecords withIndustry = TechnologyandNumberOfEmployees > 100
Limitations
If your source org doesn't contain any records for a particular value, no records with that value will be deployed to the target org.
If you use more than one "OR" filter on an object, Gearset may not give you coverage across all values in those filters.
In this example, Gearset may deploy 300
Accountsrecords withIndustry = ConstructionandBillingCountry = United States.