Skip to main content
QMSQMS
QMS
  • Welcome to your QMS
  • Quality Manual
  • Procedures
    • GP-001 Control of documents
    • GP-002 Quality planning
    • GP-003 Audits
    • GP-004 Vigilance system
    • GP-005 Human Resources and Training
    • GP-006 Non-conformity, Corrective and Preventive actions
    • GP-007 Post-market surveillance
    • GP-008 Product requirements
    • GP-009 Sales
    • GP-010 Purchases and suppliers evaluation
    • GP-011 Provision of service
    • GP-012 Design, redesign and development
      • Deprecated
      • Templates
        • T-012-004 Software version release
        • T-012-005 Design change control
        • T-012-006 _Product name_ life cycle plan and report_YYYY_nnn
        • T-012-007 Formative evaluation plan_YYYY_nnn
        • T-012-008 Formative evaluation report_YYYY_nnn
        • T-012-009 Validation and testing of machine learning models_YYYY_nnn
        • T-012-010 Device backup verification_YYYY_nnn
        • T-012-012 Customers product version control_YYYY_nnn
        • T-012-013 Design stage review
        • T-012-014 Summative evaluation plan_YYYY_nnn
        • T-012-015 Summative evaluation report YYYY_nnn
        • T-012-016 Software usability test guide
        • T-012-017 Integration test review
        • T-012-019 SOUP
        • T-012-020 Predetermined Change Control Plan
        • T-012-021 Product Design Phase 1 Checklist
        • T-012-022 Software Design Phase 2 Checklist
        • T-012-023 Software Development Plan
        • T-012-024 Software Candidate Release Phase 3 Checklist
        • T-012-025 Software Verification Phase 4 Checklist
        • T-012-026 Product Validation Phase 5 Checklist
        • T-012-028 Software Requirement Specification
        • T-012-029 Software Architecture Description
        • T-012-030 Software Configuration Management Plan
        • T-012-031 Product Requirements Specification
        • T-012-033 Software Tests Plan
        • T-012-034 Software Test Description
        • T-012-035 Software Test Run
        • T-012-037 Labeling and IFU Requirements
        • T-012-038 Verified Version Release
        • T-012-039 Validated Version Transfer
        • T-012-040 Documentation level FDA
        • T-012-041 Software Classification 62304
        • T-012-042 Regulatory Requirement
        • T-012-043 Traceability Matrix
      • GP-012 [Old version] Design, Redesign and Development
      • Specific procedures
    • GP-013 Risk management
    • GP-014 Feedback and complaints
    • GP-015 Clinical evaluation
    • GP-016 Traceability and identification
    • GP-017 Technical assistance service
    • GP-018 Infrastructure and facilities
    • GP-019 Software validation plan
    • GP-020 QMS Data analysis
    • GP-021 Communications
    • GP-022 Document translation
    • GP-023 Change control management
    • GP-024 Cybersecurity Risk Management
    • GP-025 Usability and Human Factors Engineering
    • GP-027 Corporate Governance
    • GP-028 AI Development
    • GP-029 Software Delivery And Comissioning
    • GP-050 Data Protection
    • GP-051 Security violations
    • GP-052 Data Privacy Impact Assessment (DPIA)
    • GP-100 Business Continuity (BCP) and Disaster Recovery plans (DRP)
    • GP-101 Information security
    • GP-200 Remote Data Acquisition in Clinical Investigations
    • GP-026 Market-specific product requirements
    • GP-110 Esquema Nacional de Seguridad
  • Records
  • Legit.Health Plus Version 1.1.0.0
  • Legit.Health Plus Version 1.1.0.1
  • Licenses and accreditations
  • External documentation
  • Public tenders
  • Procedures
  • GP-012 Design, redesign and development
  • Templates
  • T-012-033 Software Tests Plan

T-012-033 Software Tests Plan

Change history​

RevisionSummaryDate

Test identification​

Testing phases​

Instructions

Provide a general description of the testing phases to verify all the requirements of AI Labs software. Include the types of tests that will be performed, such as unit tests, integration tests, system tests, and acceptance tests.

Test progression​

Instructions

Outline the progression of tests from unit level to system level. Describe how each phase builds on the previous one, ensuring that all requirements are covered.

Data recording, post-processing and analysis​

Instructions

Describe how test data will be recorded, processed, and analyzed. Include details on tools or methods used for data collection and analysis, as well as how results will be documented.

Test identification and content​

Instructions

Describe the elements that each test will include, such as an unique identifier, description, traceability of the SRS requirements.

Defect identification and content​

Instructions

Describe how defects will be identified and recorded during testing, including the information that will be captured for each defect.

Test environment​

Unit test and integration test​

Instructions

Describe the environment in which unit and integration tests will be conducted. Include details on hardware, software, and any specific configurations required for these tests. Include also the personnel involved in the testing process.

Verification test​

Instructions

Describe the environment for verification tests, including any specific hardware or software configurations needed to ensure that the software meets its requirements. Include also the personnel involved in the testing process.

Planned tests​

Planned unit and integration tests​

Instructions

Describe where are defined the planned unit and integration tests and what happens if some of them are failed.

Unit and integration tests coverage​

Instructions

Provide a description of where is stored the unit and integration tests coverage report, including the tools used to generate it. If no coverage report is available, state that clearly.

Planned verification tests​

Instructions

Describe where are defined the planned verification tests and what happens if some of them are failed. Include details on how these tests will ensure that the software meets its requirements and functions correctly within the system.

Test cases​

Instructions

Provide a table with three columns: Key, Summary, and Description. List each verification test performed, assigning a unique key to each test. The Summary should briefly state the purpose of the test, while the Description should provide more detailed information about the test's objectives, procedures, and expected outcomes.

KeySummaryDescription
Previous
T-012-031 Product Requirements Specification
Next
T-012-034 Software Test Description
  • Change history
  • Test identification
    • Testing phases
    • Test progression
    • Data recording, post-processing and analysis
    • Test identification and content
    • Defect identification and content
  • Test environment
    • Unit test and integration test
    • Verification test
  • Planned tests
    • Planned unit and integration tests
      • Unit and integration tests coverage
    • Planned verification tests
      • Test cases
All the information contained in this QMS is confidential. The recipient agrees not to transmit or reproduce the information, neither by himself nor by third parties, through whichever means, without obtaining the prior written permission of Legit.Health (AI LABS GROUP S.L.)