Return to Answer

added 18 characters in body

Source Link

edited Jun 14, 2018 at 0:31

93.7k
14
90
166

Custom Settings are treated as data, not metadata, in test context, and as such are not visible during the test run.

If you need that setting available during the course of your unit test (in Apex or Flow), the test or its associated @testSetup method needs to create and insert the Custom Setting value.

Custom Settings are treated as data, not metadata, in test context, and as such are not visible during the test run.

If you need that setting available during the course of your unit test, the test or its associated @testSetup method needs to create and insert the Custom Setting value.

Custom Settings are treated as data, not metadata, in test context, and as such are not visible during the test run.

If you need that setting available during the course of your unit test (in Apex or Flow), the test or its associated @testSetup method needs to create and insert the Custom Setting value.

Source Link

created Jun 14, 2018 at 0:20

David Reed

93.7k
14
90
166

Custom Settings are treated as data, not metadata, in test context, and as such are not visible during the test run.

If you need that setting available during the course of your unit test, the test or its associated @testSetup method needs to create and insert the Custom Setting value.