esp-idf/components/bt/test_apps/.build-test-rules.yml

# Documentation: .gitlab/ci/README.md#manifest-file-to-control-the-buildtest-apps

components/bt/test_apps/basic_unit_test:
  disable:
    - if: IDF_TARGET not in ["esp32", "esp32c3"]
      reason: Sufficient to run the tests on one chip of each architecture
  depends_components:
    - bt

components/bt/test_apps/memory_release:
  disable:
    - if: IDF_TARGET not in ["esp32", "esp32c2"]
    - if: CONFIG_NAME == "iram" and IDF_TARGET != "esp32c2"
    - if: CONFIG_NAME == "psram" and SOC_SPIRAM_SUPPORTED != 1
      reason: Sufficient to run the tests on one chip of each architecture
  depends_components:
    - bt
feat(bt): migrate the tests from unit-test-app 2023-09-21 12:31:40 -04:00			`# Documentation: .gitlab/ci/README.md#manifest-file-to-control-the-buildtest-apps`

change(bt): Modify test_app directory layout - Existing test app is put in a new subdirectory "basic_unit_test" 2024-03-29 00:30:45 -04:00			`components/bt/test_apps/basic_unit_test:`
feat(bt): migrate the tests from unit-test-app 2023-09-21 12:31:40 -04:00			`disable:`
			`- if: IDF_TARGET not in ["esp32", "esp32c3"]`
			`reason: Sufficient to run the tests on one chip of each architecture`
			`depends_components:`
			`- bt`
change(bt): Add a test for release bt .bss and .data memory to heap 1. use nimble host, initialize and then deinitialize bt stack in the test 2. support tests for different SoC targets and multiple configuration options 2024-03-29 00:46:04 -04:00
			`components/bt/test_apps/memory_release:`
			`disable:`
			`- if: IDF_TARGET not in ["esp32", "esp32c2"]`
			`- if: CONFIG_NAME == "iram" and IDF_TARGET != "esp32c2"`
			`- if: CONFIG_NAME == "psram" and SOC_SPIRAM_SUPPORTED != 1`
			`reason: Sufficient to run the tests on one chip of each architecture`
			`depends_components:`
			`- bt`