Which assertion would a developer use to verify that a method returns exactly the expected integer value?

System.assertEquals(expectedValue, actualValue);

System.assertNotEquals(expectedValue, actualValue);

System.debug(expectedValue, actualValue);

System.assert(expectedValue, actualValue);

A developer is writing a unit test for a trigger that sets the `Description` field on an Account to 'Processed' after insert. Which assertion correctly verifies the trigger's behavior?

`System.assertNotEquals(null, insertedAccount.Description);`

`System.assertEquals(insertedAccount.Description, 'Processed');`

`System.assertEquals('Processed', insertedAccount.Description);`

`System.assert(insertedAccount.Description != null);`

A developer is writing a test class for a trigger that runs on Account and creates related Opportunities. The test class has multiple test methods that each need the same Account and Opportunity setup. Which approach is most efficient and reliable?

Create a static variable in the test class to hold the data and reuse it across test methods.

Create a `@testSetup` method that inserts the Account and Opportunity, and let each test method query for the data.

Use `Test.startTest()` and `Test.stopTest()` to create the data in each test method.

Insert the Account and Opportunity in each test method individually.

A developer created a custom controller for a Visualforce page that has a method `getAccounts()` returning a list of Account records. The developer needs to write a unit test for this controller. Which test approach is correct?

Insert test data, then call `getAccounts()` without instantiating the controller.

Use `Test.setCurrentPage()` to set the page, then call `getAccounts()` and assert the page reference.

Instantiate the controller, call `getAccounts()`, and assert that the returned list is not null and contains the expected records.

Use `System.assertEquals` to compare the controller instance to the expected list.

Why is it important to test a trigger with a list of multiple records (bulk scenario)?

To ensure the trigger handles more than one record at a time without exceeding governor limits

To avoid the need for assertions

To test the trigger's error handling for invalid records

SalesforceCertified Platform Developer I

Domain 5Objective 2

Describe How to Write Unit Tests for Triggers, Controllers, and Classes. PLATFORM-DEVELOPER-I Practice Questions (Page 1)

Part of the TESTING domain, which accounts for 12% of the PLATFORM-DEVELOPER-I exam.

22questions here

5free pages

8concepts

12%of the exam

Questions 1–5

1foundation · easy
Which assertion would a developer use to verify that a method returns exactly the expected integer value?
Select an answer first
2application · medium
A developer is writing a unit test for a trigger that sets the `Description` field on an Account to 'Processed' after insert. Which assertion correctly verifies the trigger's behavior?
Select an answer first
3application · medium
A developer is writing a test class for a trigger that runs on Account and creates related Opportunities. The test class has multiple test methods that each need the same Account and Opportunity setup. Which approach is most efficient and reliable?
Select an answer first
4application · medium
A developer created a custom controller for a Visualforce page that has a method `getAccounts()` returning a list of Account records. The developer needs to write a unit test for this controller. Which test approach is correct?
Select an answer first
5foundation · easy
Why is it important to test a trigger with a list of multiple records (bulk scenario)?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to PLATFORM-DEVELOPER-I

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Salesforce. “PLATFORM-DEVELOPER-I” is a trademark of its owner, used for identification only.