Scenario Outline
Check if it possible to advice transport when transport is created by sk API
The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 673ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
026ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "CONTAINER" created in transport table and set transport id
52s 028ms
When
Click button advice in transport table "CONTAINER"
234ms
And
Set advice window in schedule
3s 690ms
And
Fill advice form
18s 240ms
And
Click advice save button and wait for advice form to disappear
18s 398ms
And
Go to "TRANSPORT_TABLE"
437ms
And
Go to transport details "CONTAINER"
4s 998ms
Then
Check are advice values equals
2s 876ms
After
Hooks.deleteTransportAfterTest()
973ms
Scenario Outline
Check if it possible to advice transport when transport is created by sk API
The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 696ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
033ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
7s 138ms
When
Click button advice in transport table "OWN_COLLECTION"
234ms
And
Set advice window in schedule
3s 472ms
And
Fill advice form
18s 182ms
And
Click advice save button and wait for advice form to disappear
33s 824ms
And
Go to "TRANSPORT_TABLE"
472ms
And
Go to transport details "OWN_COLLECTION"
4s 891ms
Then
Check are advice values equals
2s 922ms
After
Hooks.deleteTransportAfterTest()
933ms
Scenario Outline
Check if it possible to advice transport when transport is created by sk API
The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
3s 024ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
043ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
032ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
51s 783ms
When
Click button advice in transport table "TRANSPORT_ORDER"
238ms
And
Set advice window in schedule
3s 498ms
And
Fill advice form
18s 120ms
And
Click advice save button and wait for advice form to disappear
33s 803ms
And
Go to "TRANSPORT_TABLE"
497ms
And
Go to transport details "TRANSPORT_ORDER"
4s 896ms
Then
Check are advice values equals
2s 925ms
After
Hooks.deleteTransportAfterTest()
853ms
Scenario Outline
Verify that advice data are saved properly
The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 749ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
047ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
096ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
52s 253ms
When
Click button advice in transport table "OWN_COLLECTION"
232ms
And
Set advice window in schedule
3s 491ms
And
Fill advice form
18s 296ms
And
Click advice save button and wait for advice form to disappear
33s 373ms
And
Go to "TRANSPORT_TABLE"
457ms
Then
Check advice data in SK API database "OWN_COLLECTION"
416ms
After
Hooks.deleteTransportAfterTest()
869ms
Scenario Outline
Verify that advice data are saved properly
The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 672ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "CONTAINER" created in transport table and set transport id
1m 1s 056ms
When
Click button advice in transport table "CONTAINER"
242ms
And
Set advice window in schedule
3s 554ms
And
Fill advice form
18s 241ms
And
Click advice save button and wait for advice form to disappear
33s 400ms
And
Go to "TRANSPORT_TABLE"
459ms
Then
Check advice data in SK API database "CONTAINER"
244ms
After
Hooks.deleteTransportAfterTest()
1s 021ms
Scenario Outline
Verify that advice data are saved properly
The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 756ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
037ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
58s 556ms
When
Click button advice in transport table "TRANSPORT_ORDER"
243ms
And
Set advice window in schedule
3s 513ms
And
Fill advice form
18s 003ms
And
Click advice save button and wait for advice form to disappear
33s 303ms
And
Go to "TRANSPORT_TABLE"
468ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
094ms
After
Hooks.deleteTransportAfterTest()
999ms
Scenario Outline
Check if not possible to advice transport in the past when advice is created from transports table and transport is created by sk API
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 721ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "CONTAINER" created in transport table and set transport id
1m 1s 035ms
When
Click button advice in transport table "CONTAINER"
228ms
And
Set advice window in schedule in the past
3s 633ms
And
Fill advice form
18s 245ms
And
Click advice save button to check error message
187ms
Then
Check if possible advice alert is displayed
069ms
After
Hooks.deleteTransportAfterTest()
722ms
Scenario Outline
Check if advice data saved in SK API database after edition
The scenario checks if you can correctly edit an advice. After that the correctness of the data that has been sent to the SK API microservice database is also verified.
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 814ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
033ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
033ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
34s 204ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
55s 273ms
And
Go to "TRANSPORT_TABLE"
491ms
When
Go to transport details "OWN_COLLECTION"
4s 991ms
And
Expand advice panel
236ms
And
Edit advice in transport details
17s 176ms
And
Fill arrival date field
2s 780ms
And
Click "save-transport-and-close" save button and wait for form to disappear
18s 246ms
Then
Check advice data in database after edition "OWN_COLLECTION"
092ms
After
Hooks.deleteTransportAfterTest()
1s 033ms
Scenario Outline
Check if advice data saved in SK API database after edition
The scenario checks if you can correctly edit an advice. After that the correctness of the data that has been sent to the SK API microservice database is also verified.
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 720ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
038ms
And
Check is transport "CONTAINER" created in transport table and set transport id
19s 152ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
57s 487ms
And
Go to "TRANSPORT_TABLE"
468ms
When
Go to transport details "CONTAINER"
5s 147ms
And
Expand advice panel
300ms
And
Edit advice in transport details
17s 088ms
And
Fill arrival date field
2s 713ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 698ms
Then
Check advice data in database after edition "CONTAINER"
098ms
After
Hooks.deleteTransportAfterTest()
1s 075ms
Scenario Outline
Check if advice data saved in SK API database after edition
The scenario checks if you can correctly edit an advice. After that the correctness of the data that has been sent to the SK API microservice database is also verified.
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
3s 139ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
038ms
And
Add transport by SKApi in "MGW"
038ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
036ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
12s 814ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
57s 064ms
And
Go to "TRANSPORT_TABLE"
463ms
When
Go to transport details "TRANSPORT_ORDER"
5s 270ms
And
Expand advice panel
462ms
And
Edit advice in transport details
17s 153ms
And
Fill arrival date field
2s 567ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 493ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
127ms
After
Hooks.deleteTransportAfterTest()
1s 527ms