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’.
Full Answer
What are the limitations of @istest annotation in Salesforce?
Test class and method default access is private ,no matter to add access specifier . 14. classes with @isTest annotation can't be a interface or enum . 15. Test method code can't be invoked by non test request . 16. Stating with salesforce API 28.0 test method can not reside inside non test classes . 17.
What is @testvisible annotation in Salesforce?
@Testvisible annotation to make visible private methods inside test classes. 18. Test method can not be used to test web-service call out . Please use call out mock . 19. You can't send email from test method.
What is Test class in Salesforce testing?
Test class in salesforce Testing is an important part of SDLC. 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 can we run unit test in Salesforce?
We can run unit test by using Salesforce Standard UI,Force.com IDE ,Console ,API. 26. Maximum number of test classes run per 24 hour of period is not grater of 500 or 10 multiplication of test classes of your organization.
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.
