Page History
The BMA allows to configure its rules according to modelling conventions that have been made at your project. To do so, follow these steps:
- Changing the parameters of rules requires logging in. The default SonarQube credentials are "admin", "admin".
- After choosing the tab "Quality Profiles", the built in Blueriq Rules Profile should appear in the list.
- From SonarQube version 6.7, it is no longer possible to manually change built in profiles. Therefore we suggest you make your own copy of the Blueriq rules profile and make this the default one.
- By clicking on one of the active rules, for instance the parameterized "Decision table gap/overlap analysis" rule, a detailed overview of the specific rule is presented.
- When clicking on the change button, the parameters are presented and editable.
- After changing the parameters, you have to run a new analysis in order to see the effect of the changes.
Parameters in rules
All Blueriq specific rules can be viewed in an overview through the Rules tab, optionally by filtering on Language Blueriq at the right of the screen:
...
Some of the Blueriq specific rules take in parameters during analysis. These parameterized rules use default values, but if needed these default values can be overridden through SonarqubeSonarQube's web interface . This requires logging in first. The default Sonarqube credentials are admin admin. After logging in, rules can be deactivated by clicking the deactivate button at the right of the overview.
By clicking on one of the active rules, for instance the parameterized flows-should-not-contain-too-many-elements-rule, an detailed overview of the specific rule is presented:
When clicking on the change button on the right, the parameters are presented and editable:
as described above. The parameterized rules are:
BMA rule: Flows should not contain many complex elements
BMA rule: Flows should not contain too many elements
BMA rule: Element names should comply with a naming convention
BMA rule: Flows should fit the default viewport
BMA rule: Decision table gap and overlap analysis
BMA rule: Aggregates should not contain too many metadata elements