Age | Commit message (Collapse) | Author | Files | Lines |
|
You must not specify the _AFT.exitAtEnd in your LUA files if you want
to be able to chain test verb calls. Else it will exit during the file which
has specified the exitAtEnd call.
Change-Id: I73ce0014d162dbecea443454f85a0e0373345a23
Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
|
|
This will launch every verbs defined in the test configuration file
instead of only the hardcoded launch_all_tests verbs
Change-Id: I95f2714054403899424ae5f567903cfa0bbd49f4
Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
|
|
This commit adds a test that ensures that the timeout waiting
an event expires correctly and that we correctly wait for the
indicated time.
Change-Id: I70c5aaf8d66588b4073cb772163d20344fdaf77c
Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
|
|
On a target, the binder process name is taken from the widget "id",
now the native launcher script also launches the binder using the widget "id".
As the controller searches its configuration file using the binder process middle name
we need to differentiate between both "id" otherwise the wrong configuration file is used.
The commit renames configuration file according to the new "id".
Change-Id: I4a596dd1d54201a671bb68bf9aca6904286322c6
Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
|
|
Using aftest and aft-aftest api name to self test was
difficult because of searching file using the binder process
name which could be the same although api name were diffirent.
Change-Id: Id14e30024f0b98c29feed5b707ab9dc8b74d3552
Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
|
|
Change-Id: I57ac01794ea92e235cb105acb22ab44f5566268b
Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
|
|
Because may the users doesn't set to exit the binder at the end
in the LUA so it has to be killed by the script. Then every case
are covered.
Change-Id: I3967b296ca8eafc65bb8109c57d2b8b2de582583
Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
|
|
For native build and test purposes you need to start 2
bindings to be able to test correctly the afb-test binding.
The first one will answer on the main API name afTest and the
second to launch the test.
This is the closest test case similar to a test on a target
board.
Change-Id: I6b961c0e41cdd3eef387b7f5156ed334e8f6c3de
Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
|
|
Remove the debug log messages.
Display the results of tests at the end.
Change-Id: I38ec1a6807a8e7de483545fd3346327fe1847f73
Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
|
|
Also separate helloWorld example binding test from self aft tests
Change-Id: I5b7c48b38cc6629c3edc97d280d7f9228451b337
Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
|