Whether running the webMethods code validation as part of the Enterprise Integration DevOps process, or by calling the built-in REST API or through the user interface, FlowMastr detects and reports any code discrepancies within seconds. The scope of the validation is flexible and can be a set of packages, a single package or even a single service.
The initial result of the FlowMastr validation is a concise summary stating the overall quality and, most importantly, a decision whether or not the Integration Server assets in scope pass or fail. These summaries are both human and machine readable and can be used to determine the next step in your DevOps process.
On demand, FlowMastr generates a quality report, listing an extensive inventory of assets, detailed information on quality and convention policy violations and, if applicable, comparison with previous validations of the same assets. Additional reports are available informing you on quality trends per asset, per team or per individual developer to support growth of your teams.
FlowMastr ships fully configured and ready to use. The included rules and conventions, based on field experience and current industry standards, form a quality baseline that you can modify and align to your company’s needs. Depending on your requirements, FlowMastr can perform any combination of available validations immediately. Return on investment starts at first use.
By performing static analysis of source code, faulty or discouraged code constructs are detected and reported on, detailing the individual occurrences down to the visual Flow service line number.
Although aspects such as variable naming or pipeline debugging generally do not cause technical problems, they may cause privacy, security, durability, efficiency, performance or other concerns. Addressing non-compliance to conventions and guidelines helps safeguard readability and maintainability of code.
As most code is generally interdependent on other code or on platform facilities, it helps to understand these interdependencies as early as possible. By detecting such (to other services, documents, user accounts, connections, etc.) and by checking target environments for their availability, deployment problems can be anticipated and avoided.
With the continuous evolution of the underlying platform, code is changed, deprecated or replaced. To ensure future-proofing, FlowMastr maintains a registry of platform deprecations that can be extended with deprecations in your own software. Prevent issues due to known changes in upcoming releases. Ensure compatibility with newer versions of the platform and your own foundation packages.
Including open source libraries in solutions is a common practice but were you aware that not all open source licenses are the same? By detecting such libraries and adding the license information to our reports, you are made aware of any potential legal complications from using these libraries. FlowMastr will also check whether there are new versions available, while at it.
Flowmastr
IDENTITIES
Each type of asset that is supported for analysis by FlowMastr has its own identity. This identity determines which validations can be performed on it. You can configure custom identities to support additional asset types, e.g. custom adapter services, or to differentiate between assets with the same identity but with different quality requirements.
ENRICHMENT
Configure rules for enriching asset information using source code to extend and enhance the asset attributes available for validation, such as adding the cyclomatic complexity of a Flow service or detecting SQL injection vulnerabilities in adapter services. Built-in and custom attributes can both be used in validation policies.
TRANSFORM
Transformation rules can be configured to change the representation of asset attribute values in preparation for validation, simplifying the validation policies configurations. Supporting both regular expressions and XPath 2.0, these rules are used, amongst other things, to derive the assets’ fully qualified namespace from its physical path.
VALIDATION
All out-of-the-box validations are configuration-driven and can be overridden to either modify their behaviour or to change the severity of violations when detected. Adding new validations is also a matter of extending the configuration. For the furthest outlying cases, FlowMastr itself can be extended with new types of validations using the built-in Java 1.8 SDK.
DEPRECATION
The built-in registry that tracks deprecations of the webMethods platform services, documents and libraries can be extended to include deprecations of assets in your own packages or third-party libraries. By adding the package versions and asset namespaces to the registry, dependency issues due to upcoming changes in your own future releases can be anticipated and avoided.
REPORTING API
Reports comprising an inventory of assets with violations and remediation hints can be attached to DevOps tickets. information on delivery and team quality can be consulted continuously. Or simply connect to the Reporting API from your data warehouse or CI/CD analytics platform for more reporting freedom.
Subscribe
Reliable
Research shows that on average developers spend 42% of their time on technical debt and maintenance, of which a third finds its origin in bad code and poor code quality, resulting in an overhead cost of approximately $2.41 trillion annually*.
Investing in quality assurance software not only helps preventing poor code but also provides insight into the quality of your delivery team and educates developers through zero-tolerance appraisal and continuous reiteration of good practices.
Contact Us
info@centipod.nl
+31 (0)6 233 866 45