search

afarran / swm2m_avl_tests

Feature tests of AVL agent
0 stars 0 forks source link

Log service: dataLogEntries message contains no entries after applying log filter (by sending setDataLogFilter) #36

Open ArturMalyszewicz opened 9 years ago

ArturMalyszewicz commented 9 years ago

Applying filter with defined timeStart and timeEnd does not work correctly: messages that have EventTime inside specified period are not included in dataLogEntries message.

Steps to reproduce:

  1. In timestamp#1 configure loggingPositionsInterval to 5 seconds
  2. Wait for 50 seconds - to timestamp#2
  3. Send setDataFilter containing timeStart = timestamp#1 and timeEnd = timestamp#2
  4. Send getDataLogFilter message and wait for dataLogEntries response
  5. Check the content of dataLogEntries - entryList field is empty (LoggedPosition entries are expected)

That also applies to other messages. Trace output is uploaded in TraceOutputsHelperFolder.

Version of firmware: IDP-680_800_v4.3.5.8338

ArturMalyszewicz commented 9 years ago

The problem is in the TestFramework - issue does not apply to hardware.

ArturMalyszewicz commented 9 years ago

TC related to this issue is in PeriodicReports module: test_LoggedPosition_ForTerminalInMovingStateAndLoggingPositionsIntervallGreaterThanZero_LoggedPositionMessageSavedPeriodically

Steps to reproduce:

  1. configure loggingPositionsInterval to 20 seconds, simulate terminal in first position in Speeding and IgnitionOn state;
  2. wait until report is saved in log;
  3. simulate terminal in second position (different than first) in non-speeding and IgnitionOff state and wait until report is saved in log;
  4. set LoggingPositionsInterval back to 0 not to get any more reports;
  5. send message to configure log filter and select entries created during the TC;

  6. collect log form terminal and analyse every single field in the saved LoggedPosition reports (values in log should be the same as the state of terminal when message saved);

    Expected results: LoggedPosition messages saved periodically in log according to LoggingPositionsInterval, fields of report have correct values