How to write a test class in Salesforce?
The key points while writing a test class are: You have to start your class with @isTest annotation, then only Salesforce will consider this class as test class. Keep your class as Private, and the best practice is to name your test class as your original Class or trigger Name + ‘Test’.
How to create test data for a test class?
Methods of your test class have to be static, void and testMethod keyword has to be used. Prepare your test data which needs to be existing before your actual test runs. There are multiple techniques of creating test data now a days, for example, setup method, static resources etc.
Why does Salesforce require 75% of code to be tested before deployment?
So, before deploying our code to production environment, Salesforce requires at least 75% of your code to be covered by our test classes whic. Salesforce has done that to make sure that our code doesn’t break in any situation in Production.
How do I pass a list to a test class?
Show activity on this post. You can either create a List<String> (or List<Id>) variable in your test class and pass it by reference, like any other parameter, or you can use literal initialization syntax.
How much of Apex code must be covered?
At least 75% of your Apex code must be covered by unit tests, and all of those tests must complete successfully. But this should not be our focus. We should aim for 100% code coverage, which ensures that you cover each positive and negative use case of your code to cover and test each and every branch of your code.
Is System.debug counted in Apex?
Calls to System.debug are not counted as part of Apex code coverage. Test methods and test classes are not counted as part of Apex code limit. So, no worries about writing long test class with more methods just to make sure that all your code branches are covered.
