AOCL LAPACK Testsuite: Added YAML files for all the available APIs (#219)

AOCL LAPACK Test-suite: Added YAML files for all the available APIs

Added new yaml files for all the existing APIs in main test
for generating API wise ctests

Author: Nikku, Deepika

test/main/CMakeLists.txt

@@ -1,5 +1,5 @@
 ###############################################################################
-# Copyright (C) 2022-2025, Advanced Micro Devices, Inc. All rights reserved.
+# Copyright (C) 2022-2026, Advanced Micro Devices, Inc. All rights reserved.
 ###############################################################################
 if(WIN32)
     project(test_libFLAME_main)
@@ -179,7 +179,6 @@ if(BUILD_TEST)
         message(WARNING "Test generation failed: ${GEN_ERROR}")
     else()
         message(STATUS "Generated API validation tests in ${TEST_OUTPUT_DIR}")
-        message(STATUS "Test generation output:\n${GEN_OUTPUT}")
     endif()
     # Include generated test files from build directory
     file(GLOB YAML_TEST_FILES "${TEST_OUTPUT_DIR}/*_tests.cmake")
@@ -188,7 +187,6 @@ if(BUILD_TEST)
             get_filename_component(API_NAME ${TEST_FILE} NAME_WE)
             string(REPLACE "_tests" "" API_NAME ${API_NAME})
             include(${TEST_FILE})
-            message(STATUS "Included API validation tests for ${API_NAME}")
         endforeach()
     else()
         message(WARNING "No API validation test files generated")

test/main/ReadMe.txt

@@ -52,6 +52,8 @@ After `make` is complete, an executable named `test_lapack.x` is created.
 There are different ways to use the executable to perform different tests as given
 below.
 
+NOTE: PyYAML is required for YAML parsing and YAML‑based test generation.
+
 1. Config file based tests
 
    In this method, input parameters to APIs are taken from config files present in
@@ -491,16 +493,21 @@ NOTE:
    Tests are automatically generated during CMake configuration when BUILD_TEST=ON.
    Generated files are in <build_dir>/test/main/validation_ctests/*_tests.cmake
 
+   Dependency:
+   YAML‑based CTest generation depends on the PyYAML package for YAML parsing.
+   Ensure that PyYAML is installed on your system.
+
    For manual generation:
      $ cd test/main/validation_ctests
      $ python3 auto_generate_tests.py --api getrf /tmp/output
      $ python3 auto_generate_tests.py --all /tmp/output
 
    Running tests:
      # Filter by label (case-insensitive for API name and group)
-     $ ctest -L GETRF        # Run all getrf tests
-     $ ctest -L short        # Run all tests with small or medium size
-     $ ctest -L GETRF -L small  # Run small GETRF tests (use multiple -L flags)
-     $ ctest -L precision_d  # Run all double precision tests
+     $ ctest -L yaml_generated  # Run all the ctests generated from yaml files
+     $ ctest -L GETRF           # Run all getrf tests
+     $ ctest -L medium          # Run all tests with small_size or medium_size (medium group)
+     $ ctest -L precision_d     # Run all double precision tests
+     $ ctest -L getrf -R medium # Run all GETRF medium size tests
 
-   NOTE: For detailed documentation, see test/main/validation_ctests/README.md
+   NOTE: For detailed documentation, see test/main/validation_ctests/ReadMe.txt

test/main/validation_ctests/README.md test/main/validation_ctests/ReadMe.txttest/main/validation_ctests/README.md renamed to test/main/validation_ctests/ReadMe.txt

@@ -1,3 +1,5 @@
+# Copyright (C) 2026, Advanced Micro Devices, Inc. All rights reserved.
+
 ##########################################################################################
 Validation CTests - YAML-Based Test Generation
 ##########################################################################################
@@ -10,7 +12,7 @@ to define test cases in YAML format, which are then automatically converted to C
 test files during the build process.
 
 The validation_ctests directory has the following contents:
-   1. README.md - This file
+   1. ReadMe.txt - This file
    2. auto_generate_tests.py - Python script that generates CMake test files from YAML
    3. auto_generate_label_groups.yaml - Global label group definitions and size threshold configuration
    4. <API>.yaml - Test definitions for each API. Each API has its own YAML file.
@@ -26,6 +28,11 @@ The test generation workflow follows this pattern:
 3. CMake Integration: Tests are generated at configure time in the build directory
 4. CTest Execution: Generated tests are executed via CMake's CTest framework
 
+## Dependency
+
+   YAML‑based CTest generation depends on the PyYAML package for YAML parsing.
+   Ensure that PyYAML is installed on your system.
+
 ## YAML File Format
 
 Each API has its own YAML file (e.g., getrf.yaml, syev.yaml). The structure follows
@@ -62,8 +69,8 @@ Filter tests:
    $ ctest -L getrf        # Lowercase also works (both cases supported)
 
    # Multiple labels (use multiple -L flags, not semicolon)
-   $ ctest -L GETRF -L small    # Tests with both GETRF and small labels
-   $ ctest -L avx2 -L precision_d  # AVX2 tests with double precision
+   $ ctest -L GETRF -L small_size    # Tests with both GETRF and small_size labels
+   $ ctest -L LIN -L precision_d  # LIN tests with double precision
 
 ### Label Groups
 
@@ -72,36 +79,30 @@ all API files. This avoids manually adding multiple labels to each test.
 
 Example in auto_generate_label_groups.yaml:
    label_groups:
-     postsubmit: [avx2, avx512]
+     postsubmit: [small_size, medium_size, large_size]
 
 When any test uses the "postsubmit" label, it automatically includes both "postsubmit"
-and its constituent labels (avx2, avx512). This allows managing labels centrally for
+and its constituent labels (small_size, medium_size, large_size). This allows managing labels centrally for
 multiple API files without editing each file individually. API-specific label_groups can
 override global groups if needed.
 
 ### Automatic Size-Based Labeling
 
-Tests are automatically assigned size labels (small, medium, large) based on parameter
+Tests are automatically assigned size labels (small_size, medium_size, large_size) based on parameter
 values defined in auto_generate_label_groups.yaml. Group labels (e.g., "short") are then automatically
 assigned to tests matching certain size criteria.
 
 Configuration in auto_generate_label_groups.yaml:
    size_thresholds:
      parameter: max  # Check 'n', 'm', or 'max' (max of m and n)
      small: 16      # n < 16 or max(m,n) < 16
-     medium: 100    # 16 <= n < 100 or 16 <= max(m,n) < 100
-     # large is automatically assigned if >= medium threshold
+     medium: 256    # 16 <= n < 256 or 16 <= max(m,n) < 256
+     # large_size is automatically assigned if >= medium threshold
 
    auto_assign_groups:
-     short: [small, medium]  # Automatically add "short" label to tests with small or medium size
+     short: [small_size]  # Automatically add "short" label to tests with small_size
 
-Benefits:
-- Zero manual edits: Tests automatically get size and group labels based on parameters
-- Centralized configuration: All thresholds in auto_generate_label_groups.yaml
-- Works across all API files automatically
-- Flexible: Can define different thresholds for different parameters
-
-Example: A test with m=16, n=16 automatically gets "medium" and "short" labels without
+Example: A test with m=16, n=16 automatically gets "medium_size" and "short" labels without
 any manual editing in the API YAML file.
 
 
@@ -116,7 +117,7 @@ To add tests for a new API, follow these steps:
    Check test/main/src/test_<api>.c to determine the correct parameter order.
 
 3. Define Test Paths
-   Add test cases covering different code paths: single element, small/large sizes,
+   Add test cases covering different code paths: single element, small_size/large_size sizes,
    architecture-specific optimizations (AVX2, AVX512), and edge cases.
 
 4. Verify Generation
@@ -148,10 +149,13 @@ For manual generation:
    $ python3 auto_generate_tests.py --all /tmp/output
 
 Run tests:
+   # Run all the tests generated from yaml files
+   $ ctest -L yaml_generated
+
    # Filter by label (case-insensitive for API name and group)
    $ ctest -L GETRF        # Matches tests with GETRF label
    $ ctest -L getrf        # Also matches (both cases supported)
-   $ ctest -L GETRF -L small  # Multiple labels (use multiple -L flags)
+   $ ctest -L GETRF -L small_size  # Multiple labels (use multiple -L flags)
    $ ctest -L avx2         # Architecture-specific tests
 
    # Filter by test name regex (uppercase API name)
@@ -161,7 +165,7 @@ Run tests:
    # Combined filtering
    $ ctest -L GETRF -R ".*kernel.*"  # GETRF tests with "kernel" in name
 
-## Example
+## Example of generated ctests
 
 Generated CMake test files are in
 <build_dir>/test/main/validation_ctests/getrf_tests.cmake after configuration.
@@ -170,4 +174,4 @@ Generated CMake test files are in
 
 The test generation is integrated into the CMake build system via test/main/CMakeLists.txt.
 Tests are generated at configure time in the build directory and are not committed to
-the source tree.
+the source tree.

test/main/validation_ctests/auto_generate_label_groups.yaml

@@ -1,25 +1,31 @@
+# Copyright (C) 2025-2026, Advanced Micro Devices, Inc. All rights reserved.
+
 # Global Label Groups Configuration
+
 # Define label groups here that can be used across all API YAML files
 # When a test uses a group label (e.g., "postsubmit"), it automatically includes
-# all labels defined in the group (e.g., [avx2, avx512])
+# all labels defined in the group.
 
 label_groups:
-  # Example: postsubmit group includes architecture-specific optimization labels
-  postsubmit: []
+  presubmit:  [small_size, medium_size]
+  postsubmit: [small_size, medium_size, large_size]
 
-# Size threshold definitions for automatic labeling
-# Tests are automatically assigned size labels (small, medium, large) based on
+# Size threshold definitions for automatic labeling:
+# Tests are automatically assigned size labels (small_size, medium_size, large_size) based on
 # parameter values. The parameter to check is specified below.
+
 size_thresholds:
   # Parameter to check: 'n', 'm', or 'max' (checks max of m and n)
   parameter: max
+
   # Threshold definitions: value < threshold
-  small: 16      # n < 16 or m < 16 or max(m,n) < 16
-  medium: 100   # 16 <= n < 100 or 16 <= m < 100 or 16 <= max(m,n) < 100
-  # large is automatically assigned if >= medium threshold
+  small:  16     # n < 16 or m < 16 or max(m,n) < 16
+  medium: 256    # 16 <= n < 256 or 16 <= m < 256 or 16 <= max(m,n) < 256
+  # large_size is automatically assigned if >= medium threshold
 
-# Auto-assign group labels based on size labels
+# Auto-assign group labels based on size labels:
 # Group labels are automatically added to tests that have matching size labels
 auto_assign_groups:
-  short: [small, medium]  # Automatically add "short" label to tests with small or medium size
-
+  short:  [small_size] # Automatically add "short" label to tests with small_size
+  medium: [small_size, medium_size] # Automatically add "medium" label to tests with small_size or medium_size
+  long:   [small_size, medium_size, large_size] # Automatically add "long" label to all the tests