summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/2_LaunchTheExample.md2
-rw-r--r--docs/WriteYourTests/Reference/0_BindingTestFunctions.md16
-rw-r--r--docs/WriteYourTests/Reference/1_BindingAssertFunctions.md16
3 files changed, 15 insertions, 19 deletions
diff --git a/docs/2_LaunchTheExample.md b/docs/2_LaunchTheExample.md
index 2186d53..e968f9a 100644
--- a/docs/2_LaunchTheExample.md
+++ b/docs/2_LaunchTheExample.md
@@ -3,7 +3,7 @@
To launch your tests, enter this command.
```bash
-afb-daemon --name afbd-test --port=1234 --workdir=package --ldpaths=/opt/AGL/lib64/afb:lib --token= -vvv --tracereq=common
+afb-daemon --name aft-aftest --port=1234 --workdir=package --ldpaths=/opt/AGL/lib64/afb:lib --token= -vvv --tracereq=common
```
On afb-daemon startup you should have all the app-framework config displayed:
diff --git a/docs/WriteYourTests/Reference/0_BindingTestFunctions.md b/docs/WriteYourTests/Reference/0_BindingTestFunctions.md
index da8f014..8da86da 100644
--- a/docs/WriteYourTests/Reference/0_BindingTestFunctions.md
+++ b/docs/WriteYourTests/Reference/0_BindingTestFunctions.md
@@ -89,14 +89,12 @@
received, you have to register the event with the test framework using
**_AFT.addEventToMonitor** function.
- Check if events has been correctly received in time (timeout in µs). An
- event name use the application framework naming scheme: **api/event_name**.
-
-* **_AFT.testGrpEvtNotReceived(testName, eventGrp, timeout, setUp, tearDown)**
+ The table has to have this format:
+ ```lua
+ eventGrp = {["api/event_name_1"]=1,["api/event_name_2"]=2,["api/event_name_3"]=5}
+ ```
+ As you can see, in the table, event names are table keys and the value stored are
+ the number of time that the events have to be received.
- Prior to be able to check that a group of event (a table of event) has not
- been received, you have to register the event with the test framework using
- **_AFT.addEventToMonitor** function.
-
- Check if event has not been correctly received in time (timeout in µs). An
+ Check if events has been correctly received in time (timeout in µs). An
event name use the application framework naming scheme: **api/event_name**. \ No newline at end of file
diff --git a/docs/WriteYourTests/Reference/1_BindingAssertFunctions.md b/docs/WriteYourTests/Reference/1_BindingAssertFunctions.md
index 1202976..918bd04 100644
--- a/docs/WriteYourTests/Reference/1_BindingAssertFunctions.md
+++ b/docs/WriteYourTests/Reference/1_BindingAssertFunctions.md
@@ -53,14 +53,12 @@
received, you have to register the event with the test framework using
**_AFT.addEventToMonitor** function.
- Check if events has been correctly received in time (timeout in µs).
- An event name use the application framework naming scheme: **api/event_name**.
-
-* **_AFT.assertGrpEvtNotReceived(eventGrp, timeout)**
+ The table has to have this format:
+ ```lua
+ eventGrp = {["api/event_name_1"]=1,["api/event_name_2"]=2,["api/event_name_3"]=5}
+ ```
+ As you can see, in the table, event names are table keys and the value stored are
+ the number of time that the events have to be received.
- Prior to be able to check that a group of event (a table of event) has not
- been received, you have to register the event with the test framework using
- **_AFT.addEventToMonitor** function.
-
- Check if events has not been correctly received in time (timeout in µs).
+ Check if events has been correctly received in time (timeout in µs).
An event name use the application framework naming scheme: **api/event_name**. \ No newline at end of file