-
Notifications
You must be signed in to change notification settings - Fork 160
/
Datastore.feature
1327 lines (1213 loc) · 67.9 KB
/
Datastore.feature
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
###############################################################################
# Copyright (c) 2017, 2022 Eurotech and/or its affiliates and others
#
# This program and the accompanying materials are made
# available under the terms of the Eclipse Public License 2.0
# which is available at https://www.eclipse.org/legal/epl-2.0/
#
# SPDX-License-Identifier: EPL-2.0
#
# Contributors:
# Eurotech - initial API and implementation
#
###############################################################################
@datastore
@integration
Feature: Datastore tests
Scenario: Start datastore for all scenarios
Given Start Datastore
Scenario: Start event broker for all scenarios
Given Start Event Broker
Scenario: Start broker for all scenarios
Given Start Broker
Scenario: Delete items by date ranges
Delete previously stored messages based on a time interval. The number of deleted items should
depend on the index window. Only the items in whole hours/days/weeks of th einterval should be deleted.
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-client-1"
And I set the database to device timestamp indexing
Given System property "datastore.index.prefix" with value ""
And I set the datastore indexing window to "week"
When I prepare a number of messages in the specified ranges and remember the list as "TestMessages"
| clientId | topic | count | startDate | endDate |
| test-client-1 | delete/by/date/test | 92 | 2018-10-01T12:00:00.000Z | 2018-12-31T12:00:00.000Z |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I create message query for current account from "2018-10-01T00:00:00.000Z" to "2018-12-31T23:59:59.999Z" with limit 1000
And I count for data message
Then I get message count 92
When I delete the indexes from "2018-10-10T00:00:00.000Z" to "2018-10-31T23:59:59.999Z"
And I refresh all indices
And I count for data message
Then I get message count 78
When I delete the indexes from "2018-12-11T00:00:00.000Z" to "2018-12-22T23:59:59.999Z"
And I refresh all indices
And I count for data message
Then I get message count 78
When I delete the indexes from "2018-11-16T00:00:00.000Z" to "2018-12-17T23:59:59.999Z"
And I refresh all indices
And I count for data message
Then I get message count 50
Then I delete all indices
When I set the datastore indexing window to "day"
When I prepare a number of messages in the specified ranges and remember the list as "TestMessages"
| clientId | topic | count | startDate | endDate |
| test-client-1 | delete/by/date/test | 744 | 2018-12-01T00:30:00.000Z | 2018-12-31T23:30:00.000Z |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I create message query for current account from "2018-12-01T00:00:00.000Z" to "2018-12-31T23:59:59.999Z" with limit 1000
And I count for data message
Then I get message count 744
When I delete the indexes from "2018-12-03T12:00:00.000Z" to "2018-12-08T12:00:00.000Z"
And I refresh all indices
And I count for data message
Then I get message count 648
When I delete the indexes from "2018-12-20T12:00:00.000Z" to "2018-12-21T12:00:00.000Z"
And I refresh all indices
And I count for data message
Then I get message count 648
When I delete the indexes from "2018-12-20T12:00:00.000Z" to "2018-12-24T12:00:00.000Z"
And I refresh all indices
And I count for data message
Then I get message count 576
Then I delete all indices
When I set the datastore indexing window to "hour"
When I prepare a number of messages in the specified ranges and remember the list as "TestMessages"
| clientId | topic | count | startDate | endDate |
| test-client-1 | delete/by/date/test | 1440 | 2018-12-01T00:00:30.000Z | 2018-12-01T23:59:30.000Z |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I create message query for current account from "2018-12-01T00:00:00.000Z" to "2018-12-01T23:59:59.999Z" with limit 1000
And I count for data message
Then I get message count 1440
When I delete the indexes from "2018-12-01T05:00:00.000Z" to "2018-12-01T08:30:00.000Z"
And I refresh all indices
And I count for data message
Then I get message count 1260
When I delete the indexes from "2018-12-01T12:01:00.000Z" to "2018-12-01T13:59:00.000Z"
And I refresh all indices
And I count for data message
Then I get message count 1260
When I delete the indexes from "2018-12-01T15:10:00.000Z" to "2018-12-01T18:50:00.000Z"
And I refresh all indices
And I count for data message
Then I get message count 1140
Then I logout
Scenario: Delete items by the datastore ID
Delete a previously stored message and verify that it is not in the store any more. Also delete and check the
message related channel, metric and client info entries.
Given I delete all indices
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
And I prepare a random message and save it as "RandomDataMessage"
And I store the message "RandomDataMessage" and remember its ID as "RandomDataMessageId"
And I refresh all indices
When I search for a data message with ID "RandomDataMessageId" and remember it as "DataStoreMessage"
Then The datastore message "DataStoreMessage" matches the prepared message "RandomDataMessage"
When I delete the datastore message with ID "RandomDataMessageId"
And I refresh all indices
When I search for a data message with ID "RandomDataMessageId" and remember it as "ShouldBeNull"
Then Message "ShouldBeNull" is null
When I query for the current account channels and store them as "AccountChannelList"
Then There is exactly 1 channel in the list "AccountChannelList"
When I delete all channels from the list "AccountChannelList"
And I refresh all indices
When I count the current account channels and store the count as "AccountChannelCount"
Then The value of "AccountChannelCount" is exactly 0
When I query for the current account metrics and store them as "AccountMetriclList"
Then There is exactly 12 metrics in the list "AccountMetriclList"
When I delete all metrics from the list "AccountMetriclList"
And I refresh all indices
When I count the current account metrics and store the count as "AccountMetricCount"
Then The value of "AccountMetricCount" is exactly 0
When I query for the current account clients and store them as "AccountClientlList"
Then There is exactly 1 client in the list "AccountClientlList"
When I delete all clients from the list "AccountClientlList"
And I refresh all indices
When I count the current account clients and store the count as "AccountClientCount"
Then The value of "AccountClientCount" is exactly 0
And I delete all indices
Scenario: Delete items based on query results
Given I delete all indices
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
Given I prepare a number of messages with the following details and remember the list as "TestMessages1"
| topic |
| delete/by/query/test/1 |
And The device "test-device-2"
Given I prepare a number of messages with the following details and remember the list as "TestMessages2"
| topic |
| delete/by/query/tests/2 |
And The device "test-device-3"
Given I prepare a number of messages with the following details and remember the list as "TestMessages3"
| topic |
| delete/by/query/test/3 |
Then I store the messages from list "TestMessages1" and remember the IDs as "StoredMessageIDs1"
Then I store the messages from list "TestMessages2" and remember the IDs as "StoredMessageIDs2"
Then I store the messages from list "TestMessages3" and remember the IDs as "StoredMessageIDs3"
And I refresh all indices
When I search for messages with IDs from the list "StoredMessageIDs1" and store them in the list "StoredMessagesList"
Then The datastore messages in list "StoredMessagesList" matches the prepared messages in list "TestMessages1"
When I pick the ID number 0 from the list "StoredMessageIDs1" and remember it as "SelectedMessageId"
When I delete the datastore message with ID "SelectedMessageId"
And I refresh all indices
When I search for a data message with ID "SelectedMessageId" and remember it as "ShouldBeNull"
Then Message "ShouldBeNull" is null
When I query for the current account channels and store them as "AccountChannelList"
Then There are exactly 3 channels in the list "AccountChannelList"
When I pick the ID of the channel number 0 in the list "AccountChannelList" and remember it as "FirstAccountId"
And I delete the channel with the ID "FirstAccountId"
And I refresh all indices
When I query for the current account channels and store them as "AccountChannelList"
Then There are exactly 2 channels in the list "AccountChannelList"
When I query for the current account metrics and store them as "AccountMetriclList"
Then There are exactly 36 metrics in the list "AccountMetriclList"
When I query for the metrics in topic "delete/by/query/test/1" and store them as "TopicMetricList"
Then There are exactly 12 metrics in the list "TopicMetricList"
When I delete the metric info data based on the last query
And I refresh all indices
When I query for the metrics in topic "delete/by/query/test/1" and store them as "TopicMetricList2x"
# Then There are exactly 0 metrics in the list "TopicMetricList2x"
When I query for the current account clients and store them as "AccountClientlList"
Then There are exactly 3 clients in the list "AccountClientlList"
And I delete client number 1 from the list "AccountClientlList"
And I refresh all indices
When I query for the current account clients and store them as "AccountClientlList2"
Then There are exactly 2 clients in the list "AccountClientlList2"
And I delete all indices
Scenario: Check the mapping for message semantic topics
Given I delete all indices
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
Given I prepare a number of messages with the following details and remember the list as "TestMessages"
| topic |
| same/metric/name/different/type/1 |
| same/metric/name/different/type/2 |
| same/metric/name/different/type/3 |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I count the current account messages and store the count as "AccountMessageCount"
Then The value of "AccountMessageCount" is exactly 3
When I count the current account metrics and store the count as "AccountMetricCount"
Then The value of "AccountMetricCount" is exactly 36
When I search for messages with IDs from the list "StoredMessageIDs" and store them in the list "StoredMessagesList"
Then The datastore messages in list "StoredMessagesList" matches the prepared messages in list "TestMessages"
And I delete all indices
Scenario: Query before schema search
Before schema is created methods that search with find for messages, channel info,
metric info and client info, should return null values.
Query methods on messages, channel info, metric info and client info should return empty
results and count on the same services should return 0.
Delete based on query or parametrized delete on non existent data should not fail. If data
doesn't exist it is not deleted.
Given I login as user with name "kapua-sys" and password "kapua-password"
Given I select account "kapua-sys"
When I search for data message with id "fake-id"
Then I don't find message
When I search for channel info with id "fake-id"
Then I don't find channel info
When I search for metric info with id "fake-id"
Then I don't find metric info
When I search for client info with id "fake-id"
Then I don't find client info
Given I create message query for current account with limit 100
When I query for data message
Then I get empty message list result
When I count for data message
Then I get message count 0
Then I delete the messages based on the last query
And I delete the the message with the ID "fake-id" from the current account
Given I create channel info query for current account with limit 10
When I query for channel info
Then I get empty channel info list result
When I count for channel info
Then I get channel info count 0
Then I delete the channel info data based on the last query
Then I delete the the channel info data with the ID "fake-id" from the current account
Given I create metric info query for current account with limit 10
When I query for metric info
Then I get empty metric info list result
When I count for metric info
Then I get metric info count 0
Then I delete the metric info data based on the last query
Then I delete the the metric info data with the ID "fake-id" from the current account
Given I create client info query for current account with limit 10
When I query for client info
Then I get empty client info list result
When I count for client info
Then I get client info count 0
Then I delete the client info data based on the last query
Then I delete the the client info data with the ID "fake-id" from the current account
Then I delete all indices
And I logout
Scenario: Check the database cache coherency
This test checks the coherence of the registry cache for the metrics info (so if, once the
cache is erased, after a new metric insert the firstMessageId and firstMessageOn contain
the previous value)
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
And I prepare a random message and save it as "RandomDataMessage1"
Then I store the message "RandomDataMessage1" and remember its ID as "RandomDataMessage1Id"
And I refresh all indices
When I search for a data message with ID "RandomDataMessage1Id" and remember it as "DataStoreMessage"
Then The datastore message "DataStoreMessage" matches the prepared message "RandomDataMessage1"
Then I clear all the database caches
And I store the message "RandomDataMessage1" and remember its ID as "RandomDataMessage2Id"
When I refresh all indices
And I search for a data message with ID "RandomDataMessage1Id" and remember it as "DataStoreMessageNew"
Then The datastore messages "DataStoreMessage" and "DataStoreMessageNew" match
And I delete all indices
Scenario: Check the message store
Store few messages with few metrics, position and body (partially randomly generated) and check
if the stored message (retrieved by id) has all the fields correctly set.
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
When I prepare 15 random messages and remember the list as "RandomMessagesList"
And I store the messages from list "RandomMessagesList" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I search for messages with IDs from the list "StoredMessageIDs" and store them in the list "StoredMessagesList"
Then The datastore messages in list "StoredMessagesList" matches the prepared messages in list "RandomMessagesList"
And I delete all indices
Scenario: Query based on message ordering
Test the correctness of the query filtering order (3 fields: date descending, date ascending,
string descending) for messages
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And I set the database to device timestamp indexing
Given I prepare 100 randomly ordered messages and remember the list as "TestMessageList"
| topic |
| bus/route/one |
| bus/route/one |
| bus/route/two/a |
| bus/route/two/b |
| tram/route/one |
| car/one |
And I store the messages from list "TestMessageList" and remember the IDs as "StoredMessageIDs"
Then I refresh all indices
When I perform an ordered query for messages and store the results as "QueriedMessageList"
Then The messages in the list "QueriedMessageList" are stored in the default order
And I delete all indices
Scenario: Test the message store with timestamp indexing
Test the correctness of the storage process with a basic message (no metrics, payload and position)
indexing message date by device timestamp (as default).
And I delete all indices
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
When I prepare a random message with null payload and save it as "TestMessageWithNullPayload"
And I set the database to device timestamp indexing
And I store the message "TestMessageWithNullPayload" and remember its ID as "TestMessageId"
Then I refresh all indices
When I perform a default query for the account messages and store the results as "AccountMessages"
And I pick message number 0 from the list "AccountMessages" and remember it as "QueriedMessage"
Then The datastore message "QueriedMessage" matches the prepared message "TestMessageWithNullPayload"
And I delete all indices
Scenario: Test the message store with server timestamp indexing
Test the correctness of the storage process with a basic message (no metrics, payload and position)
indexing message date by server timestamp (as default).
Given I delete all indices
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
When I prepare a random message with null payload and save it as "TestMessageWithNullPayload"
And I set the database to server timestamp indexing
And I store the message "TestMessageWithNullPayload" with the server time and remember its ID as "TestMessageId"
Then I refresh all indices
When I perform a default query for the account messages and store the results as "AccountMessages"
And I pick message number 0 from the list "AccountMessages" and remember it as "QueriedMessage"
Then The datastore message "QueriedMessage" matches the prepared message "TestMessageWithNullPayload"
And I delete all indices
Scenario: ChannelInfo client ID based on the account id
Check the correctness of the client ids info stored in the channel info data by retrieving the
channel info by account.
Given I delete all indices
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
And I set the database to device timestamp indexing
When I prepare a number of messages with the following details and remember the list as "TestMessages"
| clientId | topic |
| test-client-1 | ci_client_by_account/1/2/3 |
| test-client-2 | ci_client_by_account/1/2/3 |
| test-client-3 | ci_client_by_account/1/2/3 |
| test-client-4 | ci_client_by_account/1/2/3 |
| test-client-4 | ci_client_by_account/1/2/3 |
| test-client-4 | ci_client_by_account/1/2/3 |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I query for the current account channels and store them as "AccountChannelList"
Then There are exactly 4 channels in the list "AccountChannelList"
And The channel info items "AccountChannelList" match the prepared messages in "TestMessages"
And I delete all indices
Scenario: ChannelInfo last published date
Check the correctness of the channel info last publish date stored by retrieving the
channel info by account and time window.
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
And I set the database to device timestamp indexing
When I prepare a number of messages with the following details and remember the list as "TestMessages"
| clientId | topic | captured |
| test-client-1 | ci_client_by_pd_by_account/1/2/3 | 2017-07-03T09:00:00.000Z |
| test-client-2 | ci_client_by_pd_by_account/1/2/3 | 2017-07-03T09:00:00.000Z |
| test-client-2 | ci_client_by_pd_by_account/1/2/3 | 2017-07-03T09:00:10.000Z |
| test-client-2 | ci_client_by_pd_by_account/1/2/3 | 2017-07-03T09:00:20.000Z |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I query for the current account channels in the date range "2017-07-03T09:00:00.000Z" to "2017-07-03T09:00:20.000Z" and store them as "ChannelList"
Then There are exactly 2 channels in the list "ChannelList"
And Client "test-client-1" first published on a channel in the list "ChannelList" on "2017-07-03T09:00:00.000Z"
And Client "test-client-1" last published on a channel in the list "ChannelList" on "2017-07-03T09:00:00.000Z"
And Client "test-client-2" first published on a channel in the list "ChannelList" on "2017-07-03T09:00:00.000Z"
And Client "test-client-2" last published on a channel in the list "ChannelList" on "2017-07-03T09:00:20.000Z"
And I delete all indices
Scenario: ChannelInfo topic data based on the account id
Check the correctness of the topic info stored in the channel info data by retrieving the channel
info by account.
Given I delete all indices
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
And I set the database to device timestamp indexing
When I prepare a number of messages with the following details and remember the list as "TestMessages"
| clientId | topic |
| test-client-1 | ci_topic_by_account/1/2/3 |
| test-client-1 | ci_topic_by_account/1/2/4 |
| test-client-1 | ci_topic_by_account/1/2/5 |
| test-client-1 | ci_topic_by_account/1/2/6 |
| test-client-2 | ci_topic_by_account/1/2/3 |
| test-client-2 | ci_topic_by_account/1/2/4 |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I query for the current account channels and store them as "AccountChannelList"
Then There are exactly 6 channels in the list "AccountChannelList"
And The channel info items "AccountChannelList" match the prepared messages in "TestMessages"
And I delete all indices
Scenario: ChannelInfo client ID and topic data based on the client id
Check the correctness of the client ids and topics stored in the channel info data by retrieving the
channel info by client id
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And I set the database to device timestamp indexing
And The device "test-device-1"
When I prepare a number of messages with the following details and remember the list as "TestMessages1"
| clientId | topic |
| test-client-1 | bus/route/one |
| test-client-1 | bus/route/one/a |
| test-client-1 | bus/route/two/a |
| test-client-1 | bus/route/two/b |
Then I store the messages from list "TestMessages1" and remember the IDs as "StoredMessageIDs1"
When I prepare a number of messages with the following details and remember the list as "TestMessages2"
| clientId | topic |
| test-client-2 | bus/route/three |
| test-client-2 | bus/route/four |
| test-client-2 | bus/route/four/a |
Then I store the messages from list "TestMessages2" and remember the IDs as "StoredMessageIDs2"
And I refresh all indices
When I query for the channel info of the client "test-client-1" and store the result as "ClientInfoList"
Then There are exactly 4 channels in the list "ClientInfoList"
And The channel info items "ClientInfoList" match the prepared messages in "TestMessages1"
And I delete all indices
Scenario: Account wide metrics check
Check the correctness of the metric info data stored by retrieving the metrics information by account.
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
And I set the database to device timestamp indexing
Then I prepare a number of messages with the following details and remember the list as "TestMessages"
| clientId | topic |
| test-client-1 | test_topic/1/2/3 |
| test-client-2 | test_topic/1/2/3 |
And I set the following metrics to the message 0 from the list "TestMessages"
| metric | type | value |
| tst-metric-1 | double | 123 |
| tst-metric-2 | int | 123 |
And I set the following metrics to the message 1 from the list "TestMessages"
| metric | type | value |
| tst-metric-3 | string | 123 |
| tst-metric-4 | bool | true |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I query for the current account metrics and store them as "AccountMetrics"
Then There are exactly 4 metrics in the list "AccountMetrics"
And The metric info items "AccountMetrics" match the prepared messages in "TestMessages"
And I delete all indices
Scenario: MetricsInfo last published date
Check the correctness of the metrics info last publish date stored by retrieving the
metrics info published in a defined time window.
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
And I set the database to device timestamp indexing
When I prepare a number of messages with the following details and remember the list as "TestMessages"
| clientId | topic | captured |
| test-client-1 | test_topic/1/2/3 | 2017-07-03T09:00:00.000Z |
| test-client-2 | test_topic/1/2/3 | 2017-07-03T09:00:00.000Z |
| test-client-2 | test_topic/1/2/3 | 2017-07-03T09:00:10.000Z |
| test-client-2 | test_topic/1/2/3 | 2017-07-03T09:00:20.000Z |
And I set the following metrics to the message 0 from the list "TestMessages"
| metric | type | value |
| tst-metric-1 | double | 123 |
| tst-metric-2 | int | 123 |
And I set the following metrics to the message 1 from the list "TestMessages"
| metric | type | value |
| tst-metric-3 | string | 123 |
| tst-metric-4 | bool | true |
And I set the following metrics to the message 2 from the list "TestMessages"
| metric | type | value |
| tst-metric-3 | string | 123 |
| tst-metric-4 | bool | true |
And I set the following metrics to the message 3 from the list "TestMessages"
| metric | type | value |
| tst-metric-3 | string | 123 |
| tst-metric-4 | bool | true |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I query for the current account metrics in the date range "2017-07-03T09:00:00.000Z" to "2017-07-03T09:00:20.000Z" and store them as "AccountMetrics"
Then There are exactly 4 metrics in the list "AccountMetrics"
And The metric info items "AccountMetrics" match the prepared messages in "TestMessages"
And Client "test-client-1" first published a metric in the list "AccountMetrics" on "2017-07-03T09:00:00.000Z"
And Client "test-client-1" last published a metric in the list "AccountMetrics" on "2017-07-03T09:00:00.000Z"
And Client "test-client-2" first published a metric in the list "AccountMetrics" on "2017-07-03T09:00:00.000Z"
And Client "test-client-2" last published a metric in the list "AccountMetrics" on "2017-07-03T09:00:20.000Z"
And The metric "tst-metric-1" was last published in the list "AccountMetrics" on "2017-07-03T09:00:00.000Z"
And The metric "tst-metric-2" was last published in the list "AccountMetrics" on "2017-07-03T09:00:00.000Z"
And The metric "tst-metric-3" was last published in the list "AccountMetrics" on "2017-07-03T09:00:20.000Z"
And The metric "tst-metric-4" was last published in the list "AccountMetrics" on "2017-07-03T09:00:20.000Z"
And I delete all indices
Scenario: MetricsInfo client ID and topic data based on the client id
Check the correctness of the client ids and metrics stored in the metrics info data by retrieving the
metric info by client id.
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
And I set the database to device timestamp indexing
Then I prepare a number of messages with the following details and remember the list as "TestMessages"
| clientId | topic |
| test-client-1 | test_topic/1/2/3 |
| test-client-1 | test_topic/1/2/3 |
And I set the following metrics to the message 0 from the list "TestMessages"
| metric | type | value |
| tst-metric-1 | double | 123 |
| tst-metric-2 | int | 123 |
And I set the following metrics to the message 1 from the list "TestMessages"
| metric | type | value |
| tst-metric-3 | string | 123 |
| tst-metric-4 | bool | true |
Then I prepare a number of messages with the following details and remember the list as "TestMessages2"
| clientId | topic |
| test-client-2 | test_topic/1/2/3 |
And I set the following metrics to the message 0 from the list "TestMessages2"
| metric | type | value |
| tst-metric-3 | double | 123 |
| tst-metric-4 | int | 123 |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
Then I store the messages from list "TestMessages2" and remember the IDs as "StoredMessageIDs2"
And I refresh all indices
When I query for the metrics from client "test-client-1" and store them as "Client1Metrics"
Then There are exactly 4 metrics in the list "Client1Metrics"
And The metric info items "Client1Metrics" match the prepared messages in "TestMessages"
And I delete all indices
Scenario: Query based on metrics ordering
Test the correctness of the query filtering order (3 fields: date descending, date ascending,
string descending) for the metrics
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And I set the database to device timestamp indexing
Given I prepare 100 randomly ordered messages and remember the list as "TestMessageList"
| topic |
| bus/route/one |
| bus/route/one |
| bus/route/two/a |
| bus/route/two/b |
| tram/route/one |
| car/one |
And I store the messages from list "TestMessageList" and remember the IDs as "StoredMessageIDs"
Then I refresh all indices
When I perform an ordered query for metrics and store the results as "QueriedMetricList"
Then The metrics in the list "QueriedMetricList" are ordered by name
And I delete all indices
Scenario: Account based ClientInfo data check
Check the correctness of the client info data stored by retrieving the client information by account.
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
And I set the database to device timestamp indexing
When I prepare a number of messages with the following details and remember the list as "TestMessages"
| clientId | topic |
| test-client-1 | test_topic/1/2/3 |
| test-client-2 | test_topic/1/2/3 |
| test-client-2 | test_topic/1/2/3 |
| test-client-2 | test_topic/1/2/3 |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I query for the current account clients and store them as "AccountClients"
Then There are exactly 2 clients in the list "AccountClients"
And The client info items "AccountClients" match the prepared messages in "TestMessages"
And I delete all indices
Scenario: Captured date based ClientInfo data check
Check the correctness of the client info data stored by retrieving the client info with a query based
on the Captured date.
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
And I set the database to device timestamp indexing
When I prepare a number of messages with the following details and remember the list as "TestMessages"
| clientId | topic | captured |
| test-client-1 | test_topic/1/2/3 | 2017-07-03T09:00:00.000Z |
| test-client-2 | test_topic/1/2/3 | 2017-07-03T09:00:00.000Z |
| test-client-2 | test_topic/1/2/3 | 2017-07-03T09:00:10.000Z |
| test-client-2 | test_topic/1/2/3 | 2017-07-03T09:00:20.000Z |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I query for current account clients in the date range "2017-07-03T09:00:00.000Z" to "2017-07-03T09:00:20.000Z" and store them as "ClientInfos"
Then There are exactly 2 clients in the list "ClientInfos"
And Client "test-client-1" first message in the list "ClientInfos" is on "2017-07-03T09:00:00.000Z"
And Client "test-client-1" last message in the list "ClientInfos" is on "2017-07-03T09:00:00.000Z"
And Client "test-client-2" first message in the list "ClientInfos" is on "2017-07-03T09:00:00.000Z"
And Client "test-client-2" last message in the list "ClientInfos" is on "2017-07-03T09:00:20.000Z"
And I delete all indices
Scenario: Client Id based ClientInfo data check
Check the correctness of the client info data stored by retrieving the client info with a query based
on the Client Id.
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
And I set the database to device timestamp indexing
When I prepare a number of messages with the following details and remember the list as "TestMessages1"
| clientId | topic |
| test-client-1 | test_topic/1/2/3 |
Then I store the messages from list "TestMessages1" and remember the IDs as "StoredMessageIDs1"
When I prepare a number of messages with the following details and remember the list as "TestMessages2"
| clientId | topic |
| test-client-2 | test_topic/1/2/4 |
| test-client-3 | test_topic/1/2/3 |
| test-client-4 | test_topic/1/2/4 |
Then I store the messages from list "TestMessages2" and remember the IDs as "StoredMessageIDs2"
And I refresh all indices
When I query for the current account client with the Id "test-client-1" and store it as "ClientInfo"
Then There is exactly 1 client in the list "ClientInfo"
And The client info items "ClientInfo" match the prepared messages in "TestMessages1"
And I delete all indices
Scenario: Channel info queries based on datastore channel filters
Query for account channels and use specific topic filters to narrow the range of retrieved
channel info items.
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
And I set the database to device timestamp indexing
When I prepare a number of messages with the following details and remember the list as "TestMessages"
| clientId | topic |
| test-client-1 | tba_1/1/1/1 |
| test-client-1 | tba_1/1/1/2 |
| test-client-1 | tba_1/1/1/3 |
| test-client-1 | tba_1/1/2/1 |
| test-client-1 | tba_1/1/2/2 |
| test-client-1 | tba_1/1/2/3 |
| test-client-1 | tba_1/2/1/1 |
| test-client-1 | tba_1/2/1/2 |
| test-client-1 | tba_1/2/1/3 |
| test-client-1 | tba_1/2/2/1 |
| test-client-1 | tba_1/2/2/2 |
| test-client-1 | tba_1/2/2/3 |
| test-client-1 | tba_2/1/1/1 |
| test-client-1 | tba_2/1/1/2 |
| test-client-1 | tba_2/1/1/3 |
| test-client-1 | tba_2/1/2/1 |
| test-client-1 | tba_2/1/2/2 |
| test-client-1 | tba_2/1/2/3 |
| test-client-1 | tba_2/2/1/1 |
| test-client-1 | tba_2/2/1/2 |
| test-client-1 | tba_2/2/1/3 |
| test-client-1 | tba_2/2/2/1 |
| test-client-1 | tba_2/2/2/2 |
| test-client-1 | tba_2/2/2/3 |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I query for the current account channels and store them as "AccountChannelList"
Then There are exactly 24 channels in the list "AccountChannelList"
When I query for the current account channels with the filter "1/#" and store them as "QueryResult1"
Then There are exactly 0 channels in the list "QueryResult1"
When I query for the current account channels with the filter "tba_1/#" and store them as "QueryResult2"
Then There are exactly 12 channels in the list "QueryResult2"
And The channel list "QueryResult2" contains the following topics
| topic |
| tba_1/1/1/1 |
| tba_1/1/1/2 |
| tba_1/1/1/3 |
| tba_1/1/2/1 |
| tba_1/1/2/2 |
| tba_1/1/2/3 |
| tba_1/2/1/1 |
| tba_1/2/1/2 |
| tba_1/2/1/3 |
| tba_1/2/2/1 |
| tba_1/2/2/2 |
| tba_1/2/2/3 |
When I query for the current account channels with the filter "tba_2/#" and store them as "QueryResult3"
Then There are exactly 12 channels in the list "QueryResult3"
And The channel list "QueryResult3" contains the following topics
| topic |
| tba_2/1/1/1 |
| tba_2/1/1/2 |
| tba_2/1/1/3 |
| tba_2/1/2/1 |
| tba_2/1/2/2 |
| tba_2/1/2/3 |
| tba_2/2/1/1 |
| tba_2/2/1/2 |
| tba_2/2/1/3 |
| tba_2/2/2/1 |
| tba_2/2/2/2 |
| tba_2/2/2/3 |
When I query for the current account channels with the filter "tba_1/1/#" and store them as "QueryResult4"
Then There are exactly 6 channels in the list "QueryResult4"
And The channel list "QueryResult4" contains the following topics
| topic |
| tba_1/1/1/1 |
| tba_1/1/1/2 |
| tba_1/1/1/3 |
| tba_1/1/2/1 |
| tba_1/1/2/2 |
| tba_1/1/2/3 |
When I query for the current account channels with the filter "tba_2/1/1/#" and store them as "QueryResult5"
Then There are exactly 3 channels in the list "QueryResult5"
And The channel list "QueryResult5" contains the following topics
| topic |
| tba_2/1/1/1 |
| tba_2/1/1/2 |
| tba_2/1/1/3 |
And I delete all indices
Scenario: Find correct number of messages by corresponding metric
Checking of the number of messages that are associated with the correct metrics.
Searching for messages is done by one metric.
Given I start the Kura Mock
When Device is connected
And I wait for 1 seconds
Then Device status is "CONNECTED"
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And I get the KuraMock device
And I set the database to device timestamp indexing
Then I prepare a number of messages with the following details and remember the list as "TestMessages"
| clientId | topic |
| test-client-1 | test_topic/1/2/3 |
| test-client-1 | test_topic/1/2/3 |
| test-client-1 | test_topic/1/2/3 |
| test-client-2 | test_topic/1/2/3 |
| test-client-2 | test_topic/1/2/3 |
| test-client-2 | test_topic/1/2/3 |
| test-client-3 | test_topic/1/2/3 |
| test-client-3 | test_topic/1/2/3 |
| test-client-4 | test_topic/1/2/3 |
| test-client-4 | test_topic/1/2/3 |
And I set the following metrics with messages from the list "TestMessages"
| message | metric | type | value |
| 0 | tst-metric-1 | double | 123 |
| 1 | tst-metric-1 | double | 123 |
| 2 | tst-metric-1 | double | 123 |
| 3 | tst-metric-2 | int | 123 |
| 4 | tst-metric-2 | int | 123 |
| 5 | tst-metric-2 | int | 123 |
| 6 | tst-metric-3 | bool | 123 |
| 7 | tst-metric-3 | bool | 123 |
| 8 | tst-metric-4 | string | 123 |
| 9 | tst-metric-4 | string | 123 |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I query for the current account metrics and store them as "AccountMetrics"
Then There are exactly 4 metrics in the list "AccountMetrics"
When I create message query for metric "tst-metric-1"
And I count for data message
Then I get message count 3
When I create message query for metric "tst-metric-2"
And I count for data message
Then I get message count 3
When I create message query for metric "tst-metric-3"
And I count for data message
Then I get message count 2
When I create message query for metric "tst-metric-4"
And I count for data message
Then I get message count 2
And No assertion error was thrown
Then I logout
Scenario: Finding correct number of messages by corresponding two metrics
Checking of the number of messages that are associated with the correct metrics.
Searching for messages is done by two metrics.
Given I start the Kura Mock
When Device is connected
And I wait for 1 seconds
Then Device status is "CONNECTED"
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And I get the KuraMock device
And I set the database to device timestamp indexing
Then I prepare a number of messages with the following details and remember the list as "TestMessages"
| clientId | topic |
| test-client-1 | test_topic/1/2/3 |
| test-client-1 | test_topic/1/2/3 |
| test-client-1 | test_topic/1/2/3 |
| test-client-2 | test_topic/1/2/3 |
| test-client-2 | test_topic/1/2/3 |
| test-client-2 | test_topic/1/2/3 |
| test-client-3 | test_topic/1/2/3 |
| test-client-3 | test_topic/1/2/3 |
| test-client-4 | test_topic/1/2/3 |
| test-client-4 | test_topic/1/2/3 |
And I set the following metrics with messages from the list "TestMessages"
| message | metric | type | value |
| 0 | tst-metric-1 | double | 123 |
| 1 | tst-metric-1 | double | 123 |
| 2 | tst-metric-1 | double | 123 |
| 3 | tst-metric-2 | int | 123 |
| 4 | tst-metric-2 | int | 123 |
| 5 | tst-metric-2 | int | 123 |
| 6 | tst-metric-3 | bool | 123 |
| 7 | tst-metric-3 | bool | 123 |
| 8 | tst-metric-4 | string | 123 |
| 9 | tst-metric-4 | string | 123 |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I query for the current account metrics and store them as "AccountMetrics"
Then There are exactly 4 metrics in the list "AccountMetrics"
When I create message query for following metrics
| tst-metric-1 |
| tst-metric-2 |
And I count data messages for more metrics
Then I count 6 data messages
When I create message query for following metrics
| tst-metric-3 |
| tst-metric-4 |
And I count data messages for more metrics
Then I count 4 data messages
When I create message query for following metrics
| tst-metric-1 |
| tst-metric-3 |
And I count data messages for more metrics
Then I count 5 data messages
And No assertion error was thrown
And I logout
Scenario: Finding all messages by selecting all metrics
Checking of the number of messages that are associated with the correct metrics.
Searching for messages is done by all metrics.
Given I start the Kura Mock
When Device is connected
And I wait for 1 seconds
Then Device status is "CONNECTED"
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And I get the KuraMock device
And I set the database to device timestamp indexing
Then I prepare a number of messages with the following details and remember the list as "TestMessages"
| clientId | topic |
| test-client-1 | test_topic/1/2/3 |
| test-client-1 | test_topic/1/2/3 |
| test-client-1 | test_topic/1/2/3 |
| test-client-2 | test_topic/1/2/3 |
| test-client-2 | test_topic/1/2/3 |
| test-client-2 | test_topic/1/2/3 |
| test-client-3 | test_topic/1/2/3 |
| test-client-3 | test_topic/1/2/3 |
| test-client-4 | test_topic/1/2/3 |
| test-client-4 | test_topic/1/2/3 |
And I set the following metrics with messages from the list "TestMessages"
| message | metric | type | value |
| 0 | tst-metric-1 | double | 123 |
| 1 | tst-metric-1 | double | 123 |
| 2 | tst-metric-1 | double | 123 |
| 3 | tst-metric-2 | int | 123 |
| 4 | tst-metric-2 | int | 123 |
| 5 | tst-metric-2 | int | 123 |
| 6 | tst-metric-3 | bool | 123 |
| 7 | tst-metric-3 | bool | 123 |
| 8 | tst-metric-4 | string | 123 |
| 9 | tst-metric-4 | string | 123 |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I query for the current account metrics and store them as "AccountMetrics"
Then There are exactly 4 metrics in the list "AccountMetrics"
When I create message query for following metrics
| tst-metric-1 |
| tst-metric-2 |
| tst-metric-3 |
| tst-metric-4 |
And I count data messages for more metrics
Then I count 10 data messages
And No assertion error was thrown
And I logout
Scenario: Finding messages with incorrect metric parameters
Checking of the number of messages that are associated with the incorrect metrics.
Searching for messages is done by one metric.
Given I start the Kura Mock
When Device is connected
And I wait for 1 seconds
Then Device status is "CONNECTED"
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And I get the KuraMock device
And I set the database to device timestamp indexing
Then I prepare a number of messages with the following details and remember the list as "TestMessages"
| clientId | topic |
| test-client-1 | test_topic/1/2/3 |
| test-client-1 | test_topic/1/2/3 |
| test-client-1 | test_topic/1/2/3 |
| test-client-2 | test_topic/1/2/3 |
| test-client-2 | test_topic/1/2/3 |
| test-client-2 | test_topic/1/2/3 |
| test-client-3 | test_topic/1/2/3 |
| test-client-3 | test_topic/1/2/3 |
| test-client-4 | test_topic/1/2/3 |
| test-client-4 | test_topic/1/2/3 |
And I set the following metrics with messages from the list "TestMessages"
| message | metric | type | value |
| 0 | tst-metric-1 | double | 123 |
| 1 | tst-metric-1 | double | 123 |
| 2 | tst-metric-1 | double | 123 |
| 3 | tst-metric-2 | int | 123 |
| 4 | tst-metric-2 | int | 123 |
| 5 | tst-metric-2 | int | 123 |
| 6 | tst-metric-3 | bool | 123 |
| 7 | tst-metric-3 | bool | 123 |
| 8 | tst-metric-4 | string | 123 |
| 9 | tst-metric-4 | string | 123 |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I query for the current account metrics and store them as "AccountMetrics"
Then There are exactly 4 metrics in the list "AccountMetrics"
When I create message query for metric "tst-metric-1"
And I count for data message
And I expect the assertion error "AssertionError" with the text "This two values are not equal"
And I get message count 2
Then An assertion error was thrown
When I create message query for metric "tst-metric-2"
And I count for data message
And I expect the assertion error "AssertionError" with the text "This two values are not equal"
And I get message count 2
Then An assertion error was thrown
When I create message query for metric "tst-metric-3"
And I count for data message
And I expect the assertion error "AssertionError" with the text "This two values are not equal"
And I get message count 1
Then An assertion error was thrown
When I create message query for metric "tst-metric-4"
And I count for data message
And I expect the assertion error "AssertionError" with the text "This two values are not equal"
And I get message count 1
Then An assertion error was thrown
And I logout
Scenario: Create 4 clients, query all clients with offset 0 and limit 1
Check if value of limitExceed is true.
Given I delete all indices
Given I login as user with name "kapua-sys" and password "kapua-password"
And I select account "kapua-sys"
And The device "test-device-1"
And I set the database to device timestamp indexing
When I prepare a number of messages with the following details and remember the list as "TestMessages"
| clientId | topic |
| test-client-1 | ci_topic_by_account/1/2/3 |
| test-client-1 | ci_topic_by_account/1/2/4 |
| test-client-1 | ci_topic_by_account/1/2/5 |
| test-client-1 | ci_topic_by_account/1/2/6 |
Then I store the messages from list "TestMessages" and remember the IDs as "StoredMessageIDs"
And I refresh all indices
When I query for the current account channels with limit 1 and offset 0 and store them as "AccountChannelList"
Then The channel list "AccountChannelList" have limitExceed value true
And I delete all indices
And I logout
Scenario: Create 4 clients, query all clients with offset 0 and limit 4