Salesforce Exam DEX-450 Topic 8 Question 83 Discussion

Actual exam question for Salesforce's DEX-450 exam

Question #: 83
Topic #: 8

A developer at AW Computing is tasked to create the supporting test class for a programmatic customization that leverages records stored within the custom object,

Pricing Structure c. AW Computing has a complex pricing structure for each item on the store, spanning more than 500 records.

hich two approaches can the developer use to ensure Pricing _Structure__c records are available when the test class is executed?

Choose 2 answers

AUse a Test Date Factory class.

BUse the @raTeat (seeAllData=true) annotation.

CUse the Test. leadtear{} method,

DUse without shering on the class declaration.

Show Suggested Answer

Suggested Answer: A, C

by Tiera at Feb 08, 2024, 11:01 PM

Limited Time Offer

25%

Off

Get Premium DEX-450 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Carissa

1 years ago

I have used the @testSetup annotation in the past to ensure test data is available. It's another approach to consider.

upvoted 0 times

...

Whitley

1 years ago

I'd be careful with @isTest(seeAllData=true) - that can lead to some tricky test data issues down the line. A and C seem like the safer bets here.

upvoted 0 times

Velda

11 months ago

Definitely, we should avoid using @isTest(seeAllData=true) to prevent test data issues.

upvoted 0 times

...

Micaela

12 months ago

Yeah, I think using Test.startTest{} method is also a safe option.

upvoted 0 times

...

Roslyn

12 months ago

I agree, using a Test Data Factory class is a good approach.

upvoted 0 times

...

Marvel

1 years ago

I believe using the Test.loadData{} method is also a valid option to ensure Pricing Structure records are available.

upvoted 0 times

...

Carmela

1 years ago

I agree with Felicidad, utilizing a Test Data Factory class is a recommended practice.

upvoted 0 times

...

Felicidad

1 years ago

I think using a Test Data Factory class would be a good approach.

upvoted 0 times

...

Jackie

1 years ago

Haha, 'without shering on the class declaration'? I think that one's a typo, folks. Let's go with A and C - can't go wrong with good old test data factories!

upvoted 0 times

Amie

12 months ago

Yeah, using a Test Data Factory class and the Test.loadData{} method is a solid approach for this scenario.

upvoted 0 times

...

Casandra

1 years ago

I agree, test data factories are always reliable for ensuring records are available.

upvoted 0 times

...

Estrella

1 years ago

Hmm, I'm not sure about using @isTest(seeAllData=true) - I heard that's not a recommended practice these days. Maybe stick to the data factories or Test.loadData{}.

upvoted 0 times

Kallie

1 years ago

Yeah, data factories are definitely more reliable for test classes.

upvoted 0 times

...

Pamella

1 years ago

I agree, using Test.loadData{} is a safer option.

upvoted 0 times

...

Vilma

1 years ago

That's a good point, Yuette. It's important to consider all options to make sure the test class runs smoothly.

upvoted 0 times

...

Rachael

1 years ago

A and C look like good options to me. Using the Test.loadData{} method seems like the most straightforward way to get the Pricing_Structure__c records loaded for the test class.

upvoted 0 times