Skip to content

Test report html

Unit Test Report Documentation

This document outlines the generation and location of unit test reports for the nikted-had-shared and composeApp modules of the HAD client application.

Purpose

Unit tests are a fundamental part of our software development process, ensuring that individual code units or components function as designed. The reports generated from these tests provide an objective record of test execution and results, a critical requirement for compliance with IEC 62304, particularly in the verification of software units.

Modules Under Test

  • nikted-had-shared: This module contains shared logic and data models used across different parts of the application. Unit tests for this module verify the correctness of core business logic, data handling, and utility functions, ensuring these foundational components are reliable.
  • composeApp: This module is the main application module, primarily responsible for the user interface and application-level logic. Its unit tests focus on verifying the behavior of UI components, view models, and other app-specific functionalities.

Test Execution and Reporting

Our unit tests are automated and executed via the Gradle build system. This ensures that tests are run consistently as part of our continuous integration (CI) pipeline.

The test reports are generated automatically upon the completion of test execution. These reports include detailed information on:

  • The total number of tests run.
  • The number of tests that passed, failed, or were skipped.

  • Detailed information on any test failures, including stack traces and error messages.

  • Location of Reports

The generated unit test reports are archived and accessible at the following link:

This link provides access to the latest test reports, allowing for easy review and verification of our software's quality status.