- 2Installing Flosum
- 3Setting up Flosum integration user
- 4Connecting sandboxes to Flosum
- 5Setting up users in Flosum
- 6Setting org permissions
- 7Decide on naming convention
- 8Initialize the repository
- 9Setting up workflow permissions Application Development Flow
- 10Pulling changes from dev sandboxes
- 11Branching strategy
- 12Conflict and Merge strategy
- 13Static Code Analysis
- 15Regression testing
- 16Reference Architecture Integrations
- 18TFS/Azure Devops
- 19Git Integrations Compliance & Governance
- 20Compliance & Governance
Static Code Analysis is an essential tool for quality software development. Since Flosum stores all the Salesforce related code of your Org, it makes sense to integrate it with a Code Analysis tool to ensure the quality of your code.
Currently, Flosum supports code analysis for Apex classes, triggers and VisualForce pages.
Automated code scan is run on each commit to branch. For each branch 2 fields are displaying the status of review process and number of found issues:
If the number of issues > 0, then the attachment is created with the name Review-<Date of review> and detail description of problematic components (with number of line and short explanatory text):
classes/ClassOne.cls:24: Avoid DML statements inside loops
Total 43 rules for Apex code (split into 6 categories: Best Practices, Code Style, Design, Error Prone, Performance, Security) and 2 rules for VisualForce’s markup are supported, the latest actual list can be found on:
Please go this link to setup this integration.