Test Execution Notes

This page has notes for different systems that perform test execution.


 * test API
 * host/target abstraction
 * kernel installation / provisioning
 * file operations
 * console access
 * command execution
 * test retrieval, build, deployment
 * test execution:
 * ex: 'make test'
 * runtest.sh?
 * test phases?

Does this include test scheduling? (no)

Does this include test building (no) - see Test Building notes

= board-local test APIs =

test script names and locations
Every test is in a directory

APIs
Provided by board library: fuego_board_function_lib.sh

Is a library of shell functions.

board-side functions:
 * set_init_manager
 * detect_logger_service
 * exec_service_on_target
 * detect_active_eth_device
 * get_service_status

host-side functions: See http://fuegotest.org/wiki/Test_Script_APIs

test variables
Provided in environment variables, prefixed by test name:
 * ex: FUNCTIONAL_HELLO_ARGS
 * ex:

Required minimum Linux command set
Tools builtin or on the PATH
 * cat, df, find, free, grep, head, logger, logread, mkdir, mount, ps, rm ,rmdir, sync, tail, tee, touch, true, umount, uname, uptime, xargs, [

Required command arguments:
 * mkdir -p, rm -rf, grep -f,

Tools at specific paths:
 * /sbin/reboot, /bin/true, /sbin/route

Data files:
 * /var/log/messages, /var/log/syslog
 * /proc/interrupts, /proc/drop_caches, /proc/oom_score_adj

(optional)
 * proc/config.gz

Require arguments: