Checking your code in Salesforce Developer Console
Once installed and configured, your Quality Clouds Live Check for Salesforce extension lets you check and improve your code with best practices from our rulesets.
You can check the following types of CEs: Classes, Triggers, Pages, Components, Objects, Reports.
Checking code
Every time you wish, you can run a check on the file you are working on.
→ To check your code
- Once in the Salesforce Developer Console open the file you want to check.
- Right-click on the file, and choose Run Live Check. Once the check is finished, you get a notification.
Check the issues detected in the Chrome extension window.
Working on issues
For all the issues found in the check you can consult the following:
- Line of code
- Issue type and link to best practice
- Impact area
- Time to fix
→ To work on issues
- You can filter by impact area to see issues of most importance to you, for example High severity issues for Security.
- For each of the issue, you can check more about it by clicking the i icon in the Issue type column. This opens our documentation site with best practice information.
- Choose the issue you want to work on, and check the line of code on which the issue occurs.
- You can now go back to your Developer Console file and fix the issue as needed.
Working with issues from Quality Gates
This is an add-on to Quality Clouds. See our solutions and pricing for more information: https://www.qualityclouds.com/contact/.
Quality Gate is a mechanism for preventing any new technical debt from coming into the platform. It helps you in creating and implementing a strategy for dealing with technical debt in your platform. When you enable a quality gate on your instance, you create a baseline of issues to work from, and you define which new issues can be created while dealing with the debt (accepted). The baseline can be set to a date in time, by default, all existing issues are baselined to today.
Issues baseline is a snapshot of your platform quality issues taken after a recent full quality scan or activation date scan. It is the total number of issues - subdivided into corresponding numbers of issues by each impact area - and a point in time at which you want to start restricting any new issues coming into the platform. The numbers are split in two categories:
- FAIL: existing issues that are required to be fixed (they are above the radar of the accepted issues configured).
- PASS: existing issues that are not required to be fixed (the are below the radar of the accepted issues configured).
See more about how to set up Quality Gates.
Once you have set up a Quality Gate on your org, you'll see that the issues reported are divided into two categories:
- Issues- all the new issues added after you have baselined your platform. These issues should be fixed before you promote the update set.
- Baseline issues - all the existing issues you have decided to accept as your existing technical debt.
If there are any new issues detected, the Quality Gates is alerting you that these should be fixed first by displaying the following message:
Quality Gate does not allow code with any new issues. Make sure you solve these first.
