Minix Man Pages

Man Page or Keyword Search:
Man Architecture
Apropos Keyword Search (all sections) Output format
home | help
KYUA.CONF(5)                BSD File Formats Manual               KYUA.CONF(5)

     kyua.conf -- Configuration file for the kyua tool

     syntax(int version);

     Variables: architecture, platform, test_suites, unprivileged_user.

     The configuration of Kyua is a simple collection of key/value pairs
     called configuration variables.  There are configuration variables that
     have a special meaning to the runtime engine implemented by kyua(1), and
     there are variables that only have meaning in the context of particular
     test suites.

     Configuration files are Lua scripts.  In their most basic form, their
     whole purpose is to assign values to variables, but the user has the
     freedom to implement any logic he desires to compute such values.  The
     general structure of a configuration file is:


           -- Assign internal variables.
           architecture = 'foo'
           platform = 'bar'

           -- Assign test-suite variables.  All of these must be strings.
           test_suites.NetBSD.file_systems = 'ffs ext2fs'
           test_suites.X11.graphics_driver = 'vesa'

   File versioning
     Every kyua.conf file starts with a call to syntax(int version).  This
     call determines the specific schema used by the file so that future
     backwards-incompatible modifications to the file can be introduced.

     Any new kyua.conf file should set version to '2'.

   Runtime configuration variables
     The following variables are internally recognized by kyua(1):

         Name of the system architecture (aka processor type).

         Name of the system platform (aka machine type).

         Name or UID of the unprivileged user.

         If set, the given user must exist in the system and his privileges
         will be used to run test cases that need regular privileges when
         kyua(1) is executed as root.

   Test-suite configuration variables
     Each test suite is able to recognize arbitrary configuration variables,
     and their type and meaning is specific to the test suite.  Because the
     existence and naming of these variables depends on every test suite, this
     manual page cannot detail them; please refer to the documentation of the
     test suite you are working with for more details on this topic.

     Test-suite specific configuration variables are defined inside the
     test_suites dictionary.  The general syntax is:

           test_suites.<test_suite_name>.<variable_name> = <value>

     where test_suite_name is the name of the test suite, variable_name is the
     name of the variable to set, and value is a value.  The value can be a
     string, an integer or a boolean.

         Sample configuration file.


BSD                            February 9, 2013                            BSD