68e0c50211
This introduces the default language to use for building, deploying and evaluating testcases on real hardware in the automation framework. To be able to filter testcases out based on .config values, we split the build process into generating the configuration file, filtering and then the actual building. The configuration step is done first, to be able to skip as soon as possible. This file is in the top level as the test runner will look for defaults in parent directories. Note that the default's entry in tests/.tcdefaults takes advantage of the fact that all: - the test cases under tests/ print standarized strings for success or failure. - the tc_util.h kernel header will print the passed runid if specified when finalizing the testcase. We will make sure it is found to deem the TC succesful, ensuring that the right image is flashed and verified. Change-Id: If40b226aef9583f7ce4064405d9334de379f2b00 Signed-off-by: Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com>
11 lines
400 B
Plaintext
11 lines
400 B
Plaintext
# Define the timeout for receiving a result; a testcase might override
|
|
# this with another value
|
|
#
|
|
# @var timeout 20
|
|
#
|
|
# All testcases in here print either of this, so we look for said message
|
|
#
|
|
# ^eval console-rx %(console)s::fail PROJECT EXECUTION FAILED
|
|
# @eval console-rx %(console)s:%(timeout)s PROJECT EXECUTION SUCCESSFUL
|
|
# @eval console-rx %(console)s:%(timeout)s RunID: %(runid)s:%(tchash)s
|