Agenda: Tip 1. Model the DQMH Model for your App (12:59) Tip 2. Use Multiple Event Handling Loops (21:50) Tip 3. Helper Loops (26:38) Tip 4. Create State Machine Inside MHL Case (30:30) Tip 5. Add Classes To DQMH Modules (35:18) Tip 6. Minimize Unscripted Code in API Tester (44:10) Tip 7. Use API Testers As App Launcher (45:35) Tip 8. Use Separate EHL for Request and Wait for Reply Event Tests (54:06)
I don’t understand how the queue is full of pending “Aquire” messages. It appears it is 1:1, every Aquire message is immediately de-queued on the next iteration. The worst I can see is one more Aquire is executed after “Stop” is enqueued, but stop is next in line. Oh, wait, another “Aquire” gets enqueued after the “Stop” therefore the acquiring stops for one loop and then starts again. Maybe I do understand, but it should be explained differently. The queue is not “full” of messages.
