Skip to content

DHI Testing Guideline

Groups Initials
Driver/Owner NIRE
Task Force SKSH, KBAL, TOKO
Stakeholders WUW, OAR, ELST, MOFA, AHEL, JGR, KTH, SAJO
Application Context MIKE Software, Digital Solutions and Enabling Technology, Client Projects

1 Purpose

The purpose of this guideline is to establish foundational testing principles and practices that ensure consistent quality standards across DHI’s diverse application portfolio, while maintaining flexibility in testing approaches to tailor to specific context of each application. The guideline also establishes baseline testing responsibilities for teams without dedicated QA as it defines testing steps to be included in delivery workflows.

2 Scope

This section describes the scope of the testing guideline. The scope excludes rigid development methodologies, one-size-fits-all testing processes, implementation timelines, and team-specific operational procedures.

The scope of this guideline covers the following areas:

  • Universal quality standards for all applications
    This section defines the baseline set of quality benchmarks that DHI digital solutions must meet, including functionality, performance, security, and documentation quality.

  • Types and levels of Testing
    This section outlines which types and levels of testing DHI recognizes and supports across all products, even if teams select which ones to use per project.

  • Role definitions and responsibilities
    This section defines accountability across Architecture Board, Technical Leads, Product Owners, DevOps Teams, developers, and QA engineers related to planning, designing, executing, and signing off tests at each stage.

  • Testing methodology selection criteria
    This section defines the set of criteria to be used to determine which testing approaches and levels are appropriate for any given digital solution in DHI. The criteria include project/solution size, exposure and complexity, requirements stability, team expertise, and available resources.

  • Test environment strategy
    This section addresses how testing environments are set up and managed to support reliable testing (dev, testing, staging, pre-prod) for different types of testing.

  • Test Data Management
    This section defines how DHI handles test data. This includes using safe and realistic data for testing, keeping test data consistent and reusable across environments, ensuring data is available when needed for automated and manual tests, and ensuring sensitive or personal data is protected.

  • Risk-based testing and prioritisation
    This section defines how teams identify high-risk features, and how test scope is prioritized based on business and technical risk. This promotes smarter test coverage, especially with limited time and resources.

  • Tool selection and standardization
    This section documents the approved set of tools for test management, automation, and documentation across all applications for a standardized process. It also defines the process and criteria for evaluating and adopting new tools so that changes are governed and consistent.

  • Quality gates and approval processes
    This section defines which testing phases have quality gates (e.g., pre-merge, pre-release) and who signs off based on what criteria.

  • Metrics, Reporting, and Continuous Improvement
    This section defines KPIs, reporting mechanisms, and how test outcomes improve future processes. This is essential for learning loops and quality tracking.