This page will be used to collect information about test standards.
- https://tools.ietf.org/html/rfc2119 - IETF MUST, SHALL, MAY, etc. wording standards
A survey of existing test systems was conducted in the Fall of 2018. The survey and results are here: Test Stack Survey
Here are some things we'd like to standardize in open source automated testing:
Terminology and Framework
- Test nomenclature - See the Test Glossary
- CI loop diagram
Below is a diagram for the high level CI loop:
The boxes represent different processes, hardware, or storage locations. Lines between boxes indicate APIs or control flow, and are labeled with letters. The intent of this is to provide a reference model for the test standards.
See the document...
The test definition is the set of attributes, code, and data that are used to perform a test. A test definition standard would specify things like the following:
- fields - the data elements of a test
- file format (json, xml, etc.) - how a test is expressed and transported
- meta-data - data describing the test
- visualization control - information used for visualization of results
- instructions - executable code to perform the test
See Test Definition Project for more information about a project to harmonize test definitions across multiple test systems.
- how to specify test dependencies
- ex: assert_define ENV_VAR_NAME
- ex: kernel_config
- types of dependencies
Test Execution API (E)
- test API
- host/target abstraction
- kernel installation / provisioning
- file operations
- console access
- command execution
- test retrieval, build, deployment
- test execution:
- ex: 'make test'
- test execution:
- test phases
If a program uses Makefile to build and install the software under test, then it should provide the following Makefile targets, to support testing of the software.
See https://www.gnu.org/software/make/manual/make.html#Goals (section "9.2 Arguments to Specify the Goals")
- test package format
- meta-data for each test
- test results
- baseline expected results for particular tests on particular platforms
Test package format
This is a package intended to be installed on a target (as opposed to the collection of test definition information that may be stored elsewhere in the test system)
- data files (audio, video)
- monitor results (power log, trace log)
See Test Results Format Notes for details and miscellaneous notes
The results format is the output from the test and creates is part of the interface between the test program and the test execution layer (or test harness).
The main thing that the format communicates is the list of testcases (or metrics, in the case of benchmarks) and the result of the testcase (pass, fail, etc.)
- test log output format
The Linux kernel kselftest uses TAP as the preferred output format.
- what tests can be skipped (this is more part of test execution and control)
- what test results can be ignored (xfail)
- min required pass counts, max allowed failures
- thresholds for measurement results
- requires testcase id, number and operator
- environment variables used to create an SDK build environment for a board
- environment variables used for
- location of kernel configuration (used for dependency testing) KCONFIG_PATH (adopted by LTP)
- default name of test program in a target package (run-test.sh?)
- this should be part of the test definition