Testing, Debugging, and Deployment Practice Questions (PD1)

Question 1

A developer writes a test class with two test methods. The first method creates an Account and inserts it. The second method queries for Accounts and expects to find the record created in the first method. However, the second method fails because no Account is found. The developer wants both methods to share the same test data. What should the developer do to resolve this issue?

Add the @isTest(SeeAllData=true) annotation to the test class so both test methods share inserted records Move the Account creation into a public helper method and call it from each test method before querying Declare the Account as a static variable in the test class so both test methods reference the same instance Move the Account creation into a method annotated with @TestSetup so both test methods can access it

Correct Answer: Move the Account creation into a method annotated with @TestSetup so both test methods can access it

The @TestSetup annotation designates a method that runs once before all test methods in the class, and the data it creates is available to every test method via database queries, then rolled back after each method completes.

Using SeeAllData=true exposes org data but does not share data between test methods since each method still runs in its own transaction context. A static variable would not persist the database insert across methods because each test method gets its own database transaction that is rolled back. Calling a helper method from each test would create separate records per method rather than sharing one record.

Key concept tested: understanding @TestSetup for shared test data across test methods.

Question 2

Which of the following best describes why Salesforce recommends using Test.startTest() and Test.stopTest() in unit tests?

They enable asynchronous test execution and allow parallel processing of multiple test methods They reset governor limits and also commit all DML operations to the database permanently They establish a new transaction context that bypasses sharing rules during test execution They reset governor limits so the code under test runs with a fresh set of limits

Correct Answer: They reset governor limits so the code under test runs with a fresh set of limits

Test.startTest() and Test.stopTest() provide a fresh set of governor limits for the code executed between them, ensuring that test data setup does not consume limits needed by the actual code under test.

Committing DML permanently is incorrect because test data is rolled back after test execution by default. Enabling parallel processing is incorrect because these methods control governor limit context, not test parallelism. Bypassing sharing rules is incorrect because these methods have no effect on sharing rules; sharing is controlled by with sharing or without sharing keywords.

Key concept tested: governor limit management in Apex unit tests using Test.startTest() and Test.stopTest().

Question 3

How many times can Test.startTest() be called within a single test method in Apex?

Exactly once per test method Once for synchronous code and once for asynchronous code Up to three times per test method if separated by Test.stopTest() calls Twice per test method when testing different contexts

Correct Answer: Exactly once per test method

Test.startTest() can only be called exactly once per test method, and it must be paired with exactly one Test.stopTest() call; calling it more than once in the same test method will result in a System.LimitException.

Multiple calls separated by stopTest are not allowed since the framework enforces a single startTest/stopTest pair per method. Testing different contexts or separating synchronous and asynchronous code does not grant additional invocations; all code between the single startTest and stopTest pair gets a fresh set of governor limits, and any asynchronous operations within that block are executed synchronously at stopTest.

The key concept tested is understanding the governor limit reset mechanism and the one-time-only constraint of Test.startTest() per test method.

Testing, Debugging, and Deployment

PD1 - Testing, Debugging, and Deployment Example Questions

Question 1

Question 2

Question 3

Code on the Salesforce Platform