For many Salesforce developers, the development and the release of quality code is their highest aim. Yet, this aim is not always the easiest of feats to accomplish. The present reality is that a developer is unable to determine if his/code will correctly validate before committing it into a branch. What ends up happening is that sometimes, subpar code is committed into a branch and then deployed only for the developer to discover that the code is not up to the standard. This means that the developer must rework the code. Doing this comes at cost of time and effort.

Establishing a rigorous standard for code review and validation can seem like a herculean task for most Salesforce development teams. However, imagine a world where you can enforce a validation of code at the point of check-in. Better yet, let’s paint a picture of such a world because this is what AutoRABIT’s 4.1 release is offering. A team manager can enforce a practice of code review within the team. With a code analyzer, such as PMD, installed in the Salesforce environment, he/she can establish pre-validation rules against which every line of code is assessed. It is only when the code is up to the established standard that a developer can checked-in code to a branch. Therefore, prior to moving code to a branch, a developer can execute a deployment. With the aid of a code analyzer, he/she can generate a line by line report about the health of their code. Armed with this report, the developer can identify errors in the code and could either return to their source to rework the code or might discover that his/her code is perfect and give the report to his/her manager for approval to move the code to a feature or integration branch.

AutoRABIT 4.1 puts power back into the hands of developers and team managers. Team leads and managers now have control over what kinds of code gets moved into different environments. Code analysis reports are generated early in the development cycle that explain to him/her the different features that are getting deployed. He/she has intelligence into code coverage, he/she can determine if the code is up to the established standard. For the developer, this means that he/she can recheck his work before submitting it the manager. For the team manager, it means that no bad code is moving from environment to environment. In the final analysis, the new gated check-in framework and code review support for version control commit lends accountability, transparency and traceability to the development process as it is possible to determine who moved code, when and where.

Leave A Comment

Recent Posts