What two things should be done to create the test data within the unit test with the least amount of code?

A developer created a trigger on the Account object and wants to test if the trigger is properly bulkified. The developer team decided that the trigger should be tested with 200 account records with unique names.

What two things should be done to create the test data within the unit test with the least amount of code?

Choose 2 answers
A . Use Test.loadData to populate data in your test methods.
B . Create a static resource containing test data.
C . Use the @isTest (isParallel=true) annotation in the test class.
D . Use the @isTest (seeAllData=true) annotation in the test class.

View Answer

Answer: A, B

Explanation:

To test the trigger with 200 account records with unique names using the least amount of code:

Option A: Use Test.loadData to populate data in your test methods.

Test.loadData allows you to load test data from a static resource (CSV file) into your test method. This approach minimizes code since you don’t have to write code to create each record.

Reference: "Test.loadData lets you populate test records by loading the contents of a CSV file into sObjects for

use in test methods."

― Apex Developer Guide: Using Test.loadData

Option B: Create a static resource containing test data.

The CSV file used with Test.loadData is stored as a static resource. This pairs with Option

A to provide the data needed for testing.

Reference: "Create a static resource that contains the .csv file for the records you want to load."

― Apex Developer Guide: Loading Test Data from Static Resources Why Other Options Are Incorrect:

Option C: The @isTest(isParallel=true) annotation is used to run tests in parallel but does not help in creating test data.

Option D: Using @isTest(seeAllData=true) allows access to existing org data, which is not recommended and does not help create unique test data with minimal code.