Tips and tricks:

Anti-Bug Testing

Imagine: You have been working on a gorgeous new functionality in Salesforce. Of course, you are proud of yourself. You expect the compliments flowing towards you after the deployment of the functionality.

But unfortunately, you only receive feedback about bugs: We can’t find the ‘new’ button anymore, customers are getting a wrong price, or customers can see othes customers cases.

Well, let’s do something about it.

Enemy of bugs

It takes time to find the cause and to solve the software bugs. Time you’d rather spend on interesting new functionality. That is why we advise you to use an instect killer, in the form of a testing process. Because that is the enemy of bugs!

Easiest, fastest, cheapest?

As shown in the table below, the earlier you start testing in the process, the easier, cheaper and faster it will be to solve bugs. The testing process always starts with unit testing. Afterwards, API tests can be used for functional tests. Last in the process are user interface tests. Once in production, chances are low for new bugs to appear. So you can focus on solving more interesting problems.

#	Testing Process	Time & money needed to solve bugs
1	Unit tests	Easy peasy lemon squeezy 🍋
2	API tests	Piece of cake 🍰
3	UI tests	No rocket science 🚀
4	In production	Costs an arm and a leg 💸

1

Unit Test

With a unit test, you are testing a tiny bit of your code. This code-level testing is very fast and therefor the base of our testing process.

TIP! You probably already are familiar with unit testing or Apex tests if you are a Salesforce developer. If not, please checkout Trailhead for useful trailmixes on unit testing.

2

API Test

Unlike unit tests, with API you can check the business logic of the system. Using API tests, you can easily test different scenario’s. Like creating a lead with specific values, and reading the lead afterwards to check if your assignment rule is working well. Best use is to cover the most critical Salesforce processes in API tests first.

TIP! A pro would also make sure to run these API tests automatically before every deployment from your developer org to your testing or acceptance org. This can easily be done using a test automation tool.

Read about CI/CD

3

UI Test

You’d better check your changes manually in the user interface before deploying to production. You should use these tests to check whether the user can see the right things at the right place in the interface. For example testing whether a user can access the contact information that is necessary to him or her. UI tests are the most time consuming, this is why they are last in the testing process.

TIP! While testing manually, a testing boss would simultaneously automate these tests. You can use the automated tests for regression purposes. You think testing and automating simultaneously is impossible? No it isn’t. It’s simple once you are using the right test automation tools.

Read about automation

4

In Production

Once your software has been deployed, you won’t have to spend your time solving bugs!

Stay posted

Not right now, just give me some music 2 dance →