Cukinia is designed to help Linux-based embedded firmware developers run simple validation tests on their firmware.

Cukinia integrates well with embedded firmware generation frameworks such as Buildroot and Yocto, and can be run manually or by your favourite continuous integration framework.

Cukinia works if it offers the following value:

• It is very simple to use
• It requires no dependencies other than busybox
• It helps developers creating better software

cukinia [config file]

To run Cukinia, create a configuration describing your tests, and invoke it. By default, cukinia reads /etc/cukinia/cukinia.conf. Alternatively, a config file can be passed to cukinia as its argument.

A cukinia config file supports the following statements:

• cukinia_user <username>: Validates that user exists
• cukinia_process <pname> [user]: Validates that process runs (optional user)
• cukinia_python_pkg <pkg>: Validates that Python package is installed
• cukinia_test <expr>: Validates that test(1) expression is true
• cukinia_http_request <url>: Validates that url returns a 200 code
• cukinia_cmd <command>: Validates that arbitrary command returns true
• cukinia_mount <source> <mount point> [options]: Validate the presence of a mount on the system
• cukinia_symlink <link> <target>: Validate the target of a symlink
• not: Can prefix any test to invert the issue it will produce
• verbose: Can prefix any test to preserve stdout/stderr
• as <string>: Can prefix any test to change its textual description

• cukinia_conf_include <files>: Includes files as additional config files
• cukinia_run_dir <directory>: Runs all executables in directory as individual tests
• cukinia_log <message>: Logs message to stdout

• logging prefix "string": prefix logs with "string"

• $cukinia_tests: number of tests attempted
• $cukinia_failures: number of tests that failed

# Ensure our basic users are present
cukinia_user appuser1
cukinia_user appuser2

# This should always be the case
cukinia_test -f /etc/passwd

# If this user exists, then something went wrong
not cukinia_user baduser

# Those config snippets are deployed by our packages
cukinia_conf_include /etc/cukinia/conf.d/*.conf

# Is our embedded webservice up?
as "Checking webapp" cukinia_http_request http://localhost:8080/sanitycheck

# Run executable tests for myapp1
cukinia_run_dir /etc/cukinia/myapp1.d/

# Check for root mounting point on / in read write mode
cukinia_mount sysfs /sys rw

# Check the link interfaces point to /tmp/interfaces
cukinia_symlink /etc/network/interfaces /tmp/interfaces

# End
cukinia_log "ran $cukinia_tests tests, $cukinia_failures failures"

A config file is actually a POSIX shell script that is sourced by cukinia, so any logic can be used in a test file scenario. This is useful for example to make certain groups of tests depend on preliminary checks:

if cukinia_test -x /usr/bin/myapp; then
	cukinia_user myuser
	cukinia_process myapp myuser
	cukinia_http_request http://localhost:8080/testme
else
	cukinia_log "$(_colorize red "myapp not found :(")"
fi

Cukinia is released under the Apache 2 license. In addition, it is available under the GNU General Public License, version 3.