This repository has been archived by the owner on Jan 5, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 12
Logging
Frank Niessink edited this page May 4, 2018
·
2 revisions
When HQ runs it prints logging on stdout. You can determine the log level using the --log
command line option. Run quality_report.py --help
to see the possible log levels.
The log levels have roughly the following meaning:
- CRITICAL: Fatal error, the report can't be created.
- ERROR: A source returned data that can't be parsed.
- WARNING: A source hasn't been configured or is unreachable.
- INFO: Progress information.
General
Metrics
- Accessibility metric
- Action log metrics
- Aggregated test coverage metrics
- CI server metrics
- Code quality metrics
- Issue tracker metrics
- OWASP dependency check metrics
- Performance test metrics
- Prediction metrics
- Risk log metrics
- System test metrics
- System test coverage metrics
- Unit test metrics
- Unit test coverage metrics
- Version control system metrics
Metric sources
- Bamboo test report
- Checkmarx
- Git
- GitLabCI
- History
- Jenkins
- Jenkins test report
- Jira Action List
- Jira backlog
- Jira filter
- Junit test report
- OJ Audit
- Robot Framework test report
- Sharepoint Planner
- SonarQube
- Trello
- Wekan
Contributing