search

afarran / swm2m_avl_tests

Feature tests of AVL agent
0 stars 0 forks source link

LongDriving (MIN 29): event is generated 30 seconds later than it should according to maxDrivingTime setting #30

Open ArturMalyszewicz opened 9 years ago

ArturMalyszewicz commented 9 years ago

LongDriving message is sent 30 second later than it should according to settings.

Steps to reproduce:

  1. Simulate terminal stationary
  2. Set maxDrivingTime (PIN 20) to 4 minutes
  3. Simulate terminal moving - LongDriving timer start counting
  4. After 4 minutes and 30 seconds event is generated (even if there are no other messages sent meanwhile - terminal is not busy)

The same is for other settings - i.e. for maxDrivingTime = 1 event is generated after 1 minute and 30 seconds.

That is not a big deal from the real-life point of view (maxDrivingTime will be set to hours then) but in tests this causes a lot of trobules (there is a need to minimize time of running every TC so we are operating on single minutes).

afarran commented 9 years ago

AVL checks periodically while in Moving state whether there has been a LongDriving event or not. The checking period is 60 seconds. So the LongDriving message could be as late as 60 seconds. I will make this as an enhancement request, but in the meantime provide a workaround and add a TODO: comment in the code to optimize it better in the future.

TroyManary commented 9 years ago

Argus 21620