Home
- If you are a user and you have discovered a bug → please report it here create a new bug report
- If you are a user and you would like to request a new feature → please request a new feature
- If you want to be a contributor who wants to help developing Quality-time → please refer to the developer manual
- If you are an operator or DevOps engineer who want to deploy Quality-time → please refer to the deployment manual
- If you want to understand the software architecture and how each component works → please refer to software manual
- If you are a user and would like to understand the basics about reports and metrics → refer to user reference manual
- If you are a user and you need advice on good practices on how to configure reports and metrics, refer to this wiki!
Although the official documentation thoroughly describes how to deploy, develop, and configure Quality-time, newcomers may still find it challenging to begin using the tool effectively. This wiki complements the official documentation by offering practical guidance on how to get started, apply team agreements and ways of working, and incorporate non-functional quality targets into quality reports. Although this wiki is primarily maintained by employees of the Dutch government organisation ICTU, it is intended to be neutral, just like Quality-time itself. It is designed for use by any organisation involved in the development of bespoke software.
When starting with an empty report refer to the Getting started with a new report guide. When already having a report and wanting to make it more effective, refer to Using the missing metrics metric or the Configuring Metrics guide.
Most application dashboards and monitoring tools are designed for use during runtime or in production environments. Quality-time is distinct in that it monitors software quality and the associated quality assurance processes during development. It integrates data from sources within and related to the build pipeline, repository, and project tracking board.
For software development teams and their wider organisations, consistently delivering high-quality software that meets defined quality standards can be a challenging task. While integrating scanning tools into the pipeline is relatively straightforward, consolidating their outputs and acting effectively on the identified issues is a more difficult challenge. Quality-time supports development teams by helping prioritise quality issues that require immediate attention, as well as those that can be addressed in the longer term.
Quality-time collects data from various sources within the development pipeline, focusing on the software development phase of a project.
It monitors quality across three core categories:
- Software Quality — focusing on non-functional requirements (NFRs)
- Quality of the Development Environment — including development (DEV) and test (TST) stages
- Quality Assurance by the Team — reflecting team practices and quality care
Quality-time delivers value by providing:
- Clear, executable actions based on team-configured thresholds
- A consolidated view of critical information
- Near real-time metrics, available 24/7
- Support for managing and reducing technical debt
- Customisable notifications and alerting rules
