top of page
Vanessa Torpedo SonarQube 1C:BSL - CONTROL 1C CODE AND METADATA QUALITY - DO NOT CREATE PROBLEMS FOR YOUR CUSTOMER
What is it used for?
Each Commit in the 1C repository
Once the programmer has placed his code in the central repository, the monitoring server receives an alert about this event and starts all the necessary control tasks. The author of the changes receives a list of tasks for correction, if the audit revealed issues.
A single control window for manager
Release manager and the project manager, as well as the customer (if he wants) always see a clear picture of the current code base before the official release and deployment to production. Therefore you can make a conscious decision whether to ship release of 1C configuration or not.
Constantly increasing the checking rules count
Rules can be set up by your architect using XPath expressions - the usual tool for any professional 1C developer. Rules are also released continuously by the plugin authors, including the ones based on the requirements of 1C:Compatible status.
Unique features
Full management control - Calculation of project tech debt in man-hours in order to plan the budget for
refactoring
Release Management of 1C configuration - Control of each version based on the quality threshold - check if software is ready for release
Code coverage by the automated checkings - Refactoring risk assessment based on the code coverage from unit
and scenario tests
Copy-paste code - A complete picture of the duplications of code with the ability to quickly navigate between modules to view methods that require allocation to libraries
Code complexity - search of the most confusing areas that require greater maintenance costs in order to refactor them
Continuous checkings - Checking of each commit to 1C or DCVS repository with definition of code author. Personal recommendations for refactoring are also given.
Plugin abilities
1C LANGUAGES AS OBJECTS (AST) - Object model of 1C:Enterprise internal language with the ability of creating complex checks with HTML description of correction method. It also includes a 1C query language as it is the most common source of programmer errors.
NTEGRATION WITH AUTOMATED TESTING RESULTS (CODE COVERAGE) - Each line of code is checked for quality, duplication, complexity and participating in BDD and TDD automated checks. You can distinguish the code which is bad and you will know whether it can be safely refactored.
NTEGRATION TO POPULAR CODE EDITORS (LINTERS) - When using Eclipse or Visual Studio Code programmer receives checking results immediately: bad code doesn't get into a central repository.
SonarQube can solve these problems
-
Quality control threshold allows planning the terms and the costs two times better
-
Continuous analysis code coverage eliminates 95% of bugs on production
-
SonarQube increases the level of motivation and responsibility in your team
Vanessa Torpedo SonarQube
in our projects
Cloud server
15 000 rub per month
Approximately 250 $
(The first payment for two months period)
+ Connect up to 7 projects
+ NDA for source code
+ Monitoring
+ Update
- Ability to run on their own servers
- LDAP authentication
Your own server
200 000 rub
Approximately 3.335 $
50.000 rub per year (835 $ per year) - Updates and Support
+ Deployment in your own infrastructure
+ Unlimited number of projects
+ Writing your own rules using XPath
+ Creating your own quality profile
+ Unified authentication
+ Constant updates
+ Premium support
+ Filtering of 1C subsystems
bottom of page