diff options
Diffstat (limited to 'docs/WriteYourTests/Reference/1_BindingAssertFunctions.md')
| -rw-r--r-- | docs/WriteYourTests/Reference/1_BindingAssertFunctions.md | 16 |
1 files changed, 7 insertions, 9 deletions
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 |