Tooling in SQAaaS
The SQAaaS has built-in support for widely-used tools used within open source communities. Both the Pipeline as a Service and Quality Assessment and Awarding modules rely on these tools, with the main difference that the latter selects transparently the most appropriate set of tools based on the characteristics of the input asset.
Open source tools for quality analysis#
Validating some of the defined quality criteria requires the support of specific tools, based commonly on the programming language/s in use. Examples range from testing frameworks and linters to style checkers. The table below summarizes the current tools supported by the SQAaaS platform:
Source code#
Code Management (QC.Man, QC.Acc) |  |
|---|
Licensing (QC.Lic) |  |
|---|
| Python | Golang | Ruby | Java | Javascript | JSON | Dockerfile | |
|---|---|---|---|---|---|---|---|
Code Style (QC.Sty) |  flake8 |  staticcheck |  rubocop |  checkstyle |  stylelint |  jsonlint |  hadolint |
Security Static Analysis (QC.Sec) |  bandit |  gosec |  brakeman |
| Markdown | reStructuredText | |
|---|---|---|
Documentation (QC.Doc) |  markdownlint |  restructuredtext-lint |
Code Metadata (QC.Met) |  Citation File Format |  CodeMeta |
|---|
(Micro)Services#
| Infrastructure Manager | Elastic Cloud Computing Cluster | |
|---|---|---|
Deployment (SvcQC.Dep) |  im-client |  ec3 |
Research data#
FAIR (QC.FAIR) |  FAIR-eva |  F-UJI |
|---|