Apex Test Classes in Salesforce

The developers write various Apex Test Classes in Salesforce which confidently help in unit testing. It helps developers to find bugs in code and fix them to deliver better-quality code to their clients and users. 

Salesforce users can create their apex test classes in Salesforce; these test classes cover over 75% of the code. If there are no issues with Salesforce Dashboard during production, then this is what we do. They initiate the testing for different types of Apex i.e., Batch, Queueable, Future Apex, Visualforce Controller, and also extensions.

 Apex Test Class

• In Salesforce, Apex test classes basically check that all logic is operating as it should, through positive or negative testing. When the admin deploys any specific code at the final production, test classes will not be there. 
• Most of the code covers Apex test classes in Salesforce. It means that more than half of the testing is done by the test classes themselves.
• Its functioning is very similar to Python testing in that a just-in-time compiler tests the written code.
• If we aim at 100% code coverage, which ensures that we cover each positive and negative use case of our code. We also have to cover and test each and every branch of our code.
• Also calls to the System. debug doesn’t count as part of Apex code coverage.
• However, the test methods and test classes are significant doesn’t count as any part of the Apex code limit. 
• So, users have no worries about writing long test classes with more methods just to make sure that all their code branches are with cover.
• Every trigger developers are trying to deploy must have at least 1% coverage. But yes overall coverage of our products after getting our deployed code should be 75%, otherwise. Salesforce won’t let us deploy our code.

Where can we write Test classes?

We can use any of the tools, by which we can write Test Classes

1. Developer console
2. Salesforce User Interface, setup — apex classes —create or open existing test class
3. Visual studio code
4. Any IDE tool.

Key points to keep in mind while writing a test class are:

1. We have to start our class mainly with @isTest annotation, then only Salesforce will specifically consider this class as a test class.
2. Keep our class Private, and the best practice is to name our test class as our original Class or trigger Name + ‘Test’.
3. The methods of our test class must be static, and void, and the testMethod keyword must be useful there.
4. Prepare our test data which needs to be existing before our actual test runs. There are multiple techniques for creating test data nowadays, for example, set-up methods, static resources, etc. 
5. Use Test.startTest() and Test.stopTest() to make sure that the actual testing of our code happens with the fresh set of governer limits. These methods help us to reset our governor limits just before our actual code of testing executes.
6. Once our test code runs between Test.startTest() and Test.stopTest(), we must use assert statements to test. To know whether our actual code is executing correctly and giving the results as expected. In your case, if you are testing whether the book’s price has been set to 90 or not. If this simple statement returns false, then our test class will fail and will let us know. That something is not correct in your code, and you have to fix your original code.
7. Because we are testing a simple trigger, we could not show the testing using negative use cases, but in an ideal type of world, we should write multiple methods in our test class, a few should test our positive use cases, and others should test our negative test cases.

Creating Apex Test Classes in Salesforce

Steps:

1. To Open up the Salesforce Dashboard
2. Search Apex Classes.
3. Click and select the new Apex Class.
4. Add Test Class definition in this.
5. The syntax is shown there.
6. The code depends upon and looks like the Object and Trigger we created in Salesforce Account.
7. Now we can run this code in the developer’s console. Run this code to test in the console.
8. We can select the test class that we want to run.
9. By adding all the methods, click Add Selected. After that click Run.
10. The test result will be displayed. 

Hence Test class is created here.

Benefits

1. Apex test classes mainly focus on and help in troubleshooting.
2. It performs no.of tests in no time.
3. Test classes ensure what users desire and what they need.
4. It makes users more productive in Salesforce production.
5. It increases customer satisfaction and trust by delivering high-quality apps to package subscribers.
6. It also reduces buffering time and bug costs.

Conclusion

In TriColor Initiatives, our Salesforce developers do testing work executed by the test classes. Therefore, understanding how our developers develop test classes is interesting to know to the one who wishes to test the logic for Apex triggers, Apex classes, Visualforce Controller, Queueable Apex, Future Apex, Visualforce Extensions, and Batch Apex.