esp-idf/components/fatfs/test_apps
Sudeep Mohanty 9605f9be3f Merge branch 'contrib/github_pr_12800' into 'master'
feat(freertos): Added new Kconfig option CONFIG_FREERTOS_NUMBER_OF_CORES

Closes IDFGH-11693 and IDF-8785

See merge request espressif/esp-idf!28505
2024-02-20 15:21:47 +08:00
..
flash_ro feat(freertos): Introduced new Kconfig option CONFIG_FREERTOS_NUMBER_OF_CORES 2024-02-09 09:11:28 +01:00
flash_wl fix(storage): cleanup storage examples/test_apps sdkconfigs 2024-02-12 10:57:46 +01:00
sdcard fix(storage): cleanup storage examples/test_apps sdkconfigs 2024-02-12 10:57:46 +01:00
test_fatfs_common feat(freertos): Introduced new Kconfig option CONFIG_FREERTOS_NUMBER_OF_CORES 2024-02-09 09:11:28 +01:00
.build-test-rules.yml build: bypass build issues 2024-01-10 15:34:50 +01:00
README.md fatfs: add missing readme file for the test apps 2022-10-10 12:15:56 +02:00

fatfs component target tests

This directory contains tests for fatfs component which are run on chip targets.

See also test_fatfs_host directory for the tests which run on a Linux host.

Fatfs tests can be executed with different diskio backends: diskio_sdmmc (SD cards over SD or SPI interface), diskio_spiflash (wear levelling in internal flash) and diskio_rawflash (read-only, no wear levelling, internal flash). There is one test app here for each of these backends:

  • sdcard — runs fatfs tests with an SD card over SDMMC or SDSPI interface
  • flash_wl - runs fatfs test in a wear_levelling partition in SPI flash
  • flash_ro - runs fatfs test in a read-only (no wear levelling) partition in SPI flash

These test apps define:

  • test functions
  • setup/teardown routines
  • build/test configurations
  • pytest test runners

The actual test cases (many of which are common between the test apps) are defined in the test_fatfs_common component.