Suite.properties

From TinyOS Wiki
Revision as of 16:04, 21 December 2007 by Dmoss (talk | contribs) (New page: The suite.properties file optionally exists in any directory. As TUnit traverses through sub-directories, it parses each suite.properties file it finds, creating rules to filter out Test ...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

The suite.properties file optionally exists in any directory. As TUnit traverses through sub-directories, it parses each suite.properties file it finds, creating rules to filter out Test Suites if they don't apply to the current combination of hardware being tested.

Keywords

  • @assertions: The number of assertions to queue up on the embedded side. As assertions are made, they cannot be spilled out over the serial port as fast as they are generated. The TUnit embedded library queues up assertions and multi-packet fail messages and sends them when it can. The default number of assertions is 5. If you bump this up, be aware that your RAM consumption will increase on your node.
  • @extra <any build/install extras>: (@extras also works) Add in any command line arguments for compiling. You can use this, for example, to pull in .extra files from support/make, or define compile flags with no spaces such as CFLAGS+=-DLOW_POWER_LISTENING or CFLAGS+=-I../library/to/include. @extra options get aggregated together as TUnit traverses into sub-directories.
  • @ignore <single target>: Ignore one or multiple platform targets that should never run this test.
  • @only <single target>: Specify one or multiple platform targets that apply to this test, and don't allow any others.
  • @minnodes <# nodes>: The minimum number of nodes this test will allow.
  • @maxnodes <# nodes>: The maximum number of nodes this test will allow.
  • @exactnodes <# of exact nodes>: The exact nodes required for this test to run.
  • @mintargets <# of minimum targets for heterogeneous network testing>: The minimum number of targets required for this test to run. For example, this could be used to ensure your test runs on a MicaZ and TelosB, testing the compatibility between the two.
  • @timeout <minutes>: Default is 1 minute.
  • @skip: Skip this test and any tests in sub-directories.


Available, but not put to use:

  • @author <author(s)>: Not used by TUnit in any meaningful way right now, this was intended to allow TUnit to create formal documentation on all the tests it has available.
  • @testname <optional testname>: Not used by TUnit in any meaningful way right now, this was intended to allow TUnit to create formal documentation on all the tests it has available.
  • @description <optional, multiline description>: Not used by TUnit in any meaningful way right now, this was intended to allow TUnit to create formal documentation on all the tests it has available.


Examples