nuttx-apps/testing
Zhe Weng 412505d286 ostest: Introduce basic work queue test
The test consists of two parts:
- A tester that tries to trigger wrong states of work queue
- A verifier that checks whether the wqueue is still working properly

The tester is trying to queue and cancel work several times with
priority lower/same/higher than the work queue.

Most wrong cases are likely to happen with high priority like:
- If `cancel` never decreases semcount, the count may keep growing
  and finally overflow
- If `cancel` is decreasing semcount too much, the `work_thread` may
  be waken up less times than expected

The lower/same priority testers are just added for covering other
unexpected situations.

The verifier is trying to queue some works and check they are called as
expected:
- Frist queue a 'sleep' worker, to let a work queue thread be in busy
  status and not waiting on sem, while other work queue thread(s) (if
  any) still waiting for sem. If sem is in wrong state, it may cause
  wrong behavior in either thread waiting/not waiting on the sem.
- Then queue a few count works, if the work queue(s) are still working
  properly, these works should finally be all called once.

Signed-off-by: Zhe Weng <wengzhe@xiaomi.com>
2023-03-22 12:56:01 +02:00
..
arch_libc Add Arch-specific libc test case. 2023-03-17 11:59:13 -03:00
cmocka testing/cmocka: update cmocka version and add patch 2023-02-17 23:44:30 +08:00
cpuload cpuload: add cpulad test case 2023-01-26 08:11:04 +02:00
crypto apps/testing/crypto/Makefile: fix nxstyle 2023-03-21 20:37:38 -03:00
cxxtest apps/testing/cxxtest/Makefile: fix nxstyle 2023-03-09 01:43:09 +08:00
drivertest drivertest/drivertest_uart: uart driver testcase 2023-02-24 17:13:06 +08:00
fatutf8 testing/fstest: add cleanup to fatutf8 2022-03-15 18:38:52 +08:00
fstest change strcpy to strlcpy 2023-02-22 23:09:55 +08:00
getprime Include missing headers throughout the repository 2023-03-07 09:58:13 +08:00
iozone Don't download tarballs if a local git repo found 2022-08-28 17:20:47 +08:00
irtest tesint/irtest: Include unistd.h to get close prototype 2023-02-05 20:41:37 +02:00
ltp apps/testing/ltp/Makefile: Fix mistakes in comments 2023-03-09 01:43:09 +08:00
mm fsutils/examples: Include unistd.h explicitly 2023-02-05 08:46:59 +02:00
monkey testing/monkey: add auto select uinput 2022-11-29 04:54:20 +08:00
mtd_config_fs apps/testing/mtd_config_fs/Makefile: fix nxstyle 2023-03-09 01:43:09 +08:00
nxffs zmodem: Move crc16.h and crc32.h from host to host/nuttx 2022-08-13 13:28:30 +03:00
ostest ostest: Introduce basic work queue test 2023-03-22 12:56:01 +02:00
scanftest testing/scanftest: fix nxstyle 2022-03-28 00:25:56 +08:00
sensortest Include missing headers throughout the repository 2023-03-07 09:58:13 +08:00
smart zmodem: Move crc16.h and crc32.h from host to host/nuttx 2022-08-13 13:28:30 +03:00
smart_test Fix the minor style issue 2022-10-16 19:07:16 +02:00
smp Typo fixes. 2022-01-06 10:30:41 +08:00
uclibcxx_test uclibcxx_test/Make.defs Fix mistakes in comments 2023-03-09 01:43:09 +08:00
unity apps/testing/unity/Make.defs: fix nxstyle 2023-03-09 01:43:09 +08:00
.gitignore Ensure all source code end with one and only one newline 2020-02-09 08:14:49 -06:00
Make.defs Makefiles: Mateusz Szafoni: update licenses to Apache 2021-06-07 21:35:33 -05:00
Makefile Makefiles: Mateusz Szafoni: update licenses to Apache 2021-06-07 21:35:33 -05:00
README.md Rewritten READMEs to Markdown 2020-07-25 01:01:51 -07:00

Testing

The apps/testing directory is used to build NuttX-specific tests and to include external testing frameworks.

There is overlap between what you will find in apps/examples and apps/testing in the sense that there are also tests in apps/examples as well. Those tests, however, can also be used to illustrate usage of a NuttX feature. Most of the tests in apps/testing, on the other hand, are pure tests with little value as usage examples.

cxxtest

This is a test of the C++ standard library. At present a port of the uClibc++ C++ library is available. Due to licensing issues, the uClibc++ C++ library is not included in the NuttX source tree by default, but must be installed (see the README.txt file in the uClibc++ download package for installation).

The uClibc++ test includes simple test of:

  • iostreams,
  • STL,
  • RTTI, and
  • Exceptions

Example Configuration Options

  • CONFIG_TESTING_CXXTEST=y Eanbles the example

Other Required Configuration Settings

Other NuttX setting that are required include:

  • CONFIG_HAVE_CXX=y
  • CONFIG_HAVE_CXXINITIALIZE=y
  • CONFIG_UCLIBCXX=y or CONFIG_LIBCXX=y

Additional uClibc++/libcxx settings may be required in your build environment.

fstest

This is a generic file system test that derives from testing/nxffs. It was created to test the tmpfs file system, but should work with any file system provided that all initialization has already been performed prior to starting the test.

This test a a general test for any file system, but includes some specific hooks for the SPIFFS file system.

  • CONFIG_TESTING_FSTEST Enable the file system example.
  • CONFIG_TESTING_FSTEST_MAXNAME Determines the maximum size of names used in the filesystem.
  • CONFIG_TESTING_FSTEST_MAXFILE Determines the maximum size of a file.
  • CONFIG_TESTING_FSTEST_MAXIO Max I/O, default 347.
  • CONFIG_TESTING_FSTEST_MAXOPEN Max open files.
  • CONFIG_TESTING_FSTEST_MOUNTPT Path where the file system is mounted.
  • CONFIG_TESTING_FSTEST_NLOOPS Number of test loops. default 100.
  • CONFIG_TESTING_FSTEST_VERBOSE Verbose output.

mm

This is a simple test of the memory manager.

nxffs

This is a test of the NuttX NXFFS FLASH file system. This is an NXFFS stress test and beats on the file system very hard. It should only be used in a simulation environment! Putting this NXFFS test on real hardware will most likely destroy your FLASH. You have been warned.

ostest

This is the NuttX qualification suite. It attempts to exercise a broad set of OS functionality. Its coverage is not very extensive as of this writing, but it is used to qualify each NuttX release.

The behavior of the ostest can be modified with the following settings in the boards/<arch>/<chip>/<board>/configs/<config>/defconfig file:

  • CONFIG_NSH_BUILTIN_APPS Build the OS test example as an NSH built-in application.

  • CONFIG_TESTING_OSTEST_LOOPS Used to control the number of executions of the test. If undefined, the test executes one time. If defined to be zero, the test runs forever.

  • CONFIG_TESTING_OSTEST_STACKSIZE Used to create the ostest task. Default is 8192.

  • CONFIG_TESTING_OSTEST_NBARRIER_THREADS Specifies the number of threads to create in the barrier test. The default is 8 but a smaller number may be needed on systems without sufficient memory to start so many threads.

  • CONFIG_TESTING_OSTEST_RR_RANGE During round-robin scheduling test two threads are created. Each of the threads searches for prime numbers in the configurable range, doing that configurable number of times. This value specifies the end of search range and together with number of runs allows to configure the length of this test it should last at least a few tens of seconds. Allowed values [1; 32767], default 10000.

  • CONFIG_TESTING_OSTEST_RR_RUNS During round-robin scheduling test two threads are created. Each of the threads searches for prime numbers in the configurable range, doing that configurable number of times.

smart SMART File System

This is a test of the SMART file system that derives from testing/nxffs.

  • CONFIG_TESTING_SMART Enable the SMART file system example.

  • CONFIG_TESTING_SMART_ARCHINIT The default is to use the RAM MTD device at drivers/mtd/rammtd.c. But an architecture-specific MTD driver can be used instead by defining CONFIG_TESTING_SMART_ARCHINIT. In this case, the initialization logic will call smart_archinitialize() to obtain the MTD driver instance.

  • CONFIG_TESTING_SMART_NEBLOCKS When CONFIG_TESTING_SMART_ARCHINIT is not defined, this test will use the RAM MTD device at drivers/mtd/rammtd.c to simulate FLASH. In this case, this value must be provided to give the number of erase blocks in MTD RAM device. The size of the allocated RAM drive will be: CONFIG_RAMMTD_ERASESIZE * CONFIG_TESTING_SMART_NEBLOCKS.

  • CONFIG_TESTING_SMART_MAXNAME Determines the maximum size of names used in the filesystem.

  • CONFIG_TESTING_SMART_MAXFILE Determines the maximum size of a file.

  • CONFIG_TESTING_SMART_MAXIO Max I/O, default 347.

  • CONFIG_TESTING_SMART_MAXOPEN Max open files.

  • CONFIG_TESTING_SMART_MOUNTPT SMART mountpoint.

  • CONFIG_TESTING_SMART_NLOOPS Number of test loops. default 100.

  • CONFIG_TESTING_SMART_VERBOSE Verbose output.

smart_test SMART File System

Performs a file-based test on a SMART (or any) filesystem. Validates seek, append and seek-with-write operations.

  • CONFIG_TESTING_SMART_TEST=y
Author: Ken Pettit
  Date: April 24, 2013

Performs a file-based test on a SMART (or any) filesystem. Validates seek, append and seek-with-write operations.

Usage:

  flash_test mtdblock_device

Additional options:

  --force                     to replace existing installation

smp

This is a simple test for SMP functionality. It is basically just the pthread barrier test with some custom instrumentation.

unity

Unity is a unit testing framework for C developed by ThrowTheSwitch.org:

http://www.throwtheswitch.org/unity