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 815ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
074ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
034ms
And
Check is transport "CONTAINER" created in transport table and set transport id
52s 026ms
When
Click button advice in transport table "CONTAINER"
227ms
And
Set advice window in schedule
3s 594ms
And
Fill advice form
18s 261ms
And
Click advice save button and wait for advice form to disappear
33s 825ms
And
Go to "TRANSPORT_TABLE"
454ms
And
Go to transport details "CONTAINER"
4s 898ms
Then
Check are advice values equals
3s 060ms
After
Hooks.deleteTransportAfterTest()
1s 058ms
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 693ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
034ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
52s 272ms
When
Click button advice in transport table "OWN_COLLECTION"
236ms
And
Set advice window in schedule
3s 552ms
And
Fill advice form
18s 274ms
And
Click advice save button and wait for advice form to disappear
33s 835ms
And
Go to "TRANSPORT_TABLE"
450ms
And
Go to transport details "OWN_COLLECTION"
4s 887ms
Then
Check are advice values equals
2s 872ms
After
Hooks.deleteTransportAfterTest()
1s 071ms
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 765ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
024ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
034ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
51s 697ms
When
Click button advice in transport table "TRANSPORT_ORDER"
248ms
And
Set advice window in schedule
3s 512ms
And
Fill advice form
18s 049ms
And
Click advice save button and wait for advice form to disappear
33s 838ms
And
Go to "TRANSPORT_TABLE"
472ms
And
Go to transport details "TRANSPORT_ORDER"
4s 900ms
Then
Check are advice values equals
2s 881ms
After
Hooks.deleteTransportAfterTest()
1s 067ms
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 790ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
034ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
52s 251ms
When
Click button advice in transport table "OWN_COLLECTION"
228ms
And
Set advice window in schedule
3s 452ms
And
Fill advice form
18s 077ms
And
Click advice save button and wait for advice form to disappear
33s 836ms
And
Go to "TRANSPORT_TABLE"
462ms
Then
Check advice data in SK API database "OWN_COLLECTION"
434ms
After
Hooks.deleteTransportAfterTest()
1s 044ms
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 670ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
023ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
034ms
And
Check is transport "CONTAINER" created in transport table and set transport id
58s 057ms
When
Click button advice in transport table "CONTAINER"
241ms
And
Set advice window in schedule
3s 732ms
And
Fill advice form
18s 042ms
And
Click advice save button and wait for advice form to disappear
33s 855ms
And
Go to "TRANSPORT_TABLE"
443ms
Then
Check advice data in SK API database "CONTAINER"
235ms
After
Hooks.deleteTransportAfterTest()
1s 113ms
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 653ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
034ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
1m 698ms
When
Click button advice in transport table "TRANSPORT_ORDER"
238ms
And
Set advice window in schedule
3s 498ms
And
Fill advice form
18s 232ms
And
Click advice save button and wait for advice form to disappear
33s 788ms
And
Go to "TRANSPORT_TABLE"
470ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
097ms
After
Hooks.deleteTransportAfterTest()
1s 125ms
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 662ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
034ms
And
Check is transport "CONTAINER" created in transport table and set transport id
1m 1s 044ms
When
Click button advice in transport table "CONTAINER"
232ms
And
Set advice window in schedule in the past
3s 504ms
And
Fill advice form
18s 103ms
And
Click advice save button to check error message
205ms
Then
Check if possible advice alert is displayed
073ms
After
Hooks.deleteTransportAfterTest()
767ms
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 794ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
024ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
034ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
34s 234ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
55s 581ms
And
Go to "TRANSPORT_TABLE"
457ms
When
Go to transport details "OWN_COLLECTION"
4s 901ms
And
Expand advice panel
254ms
And
Edit advice in transport details
16s 623ms
And
Fill arrival date field
2s 640ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 516ms
Then
Check advice data in database after edition "OWN_COLLECTION"
101ms
After
Hooks.deleteTransportAfterTest()
1s 120ms
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 686ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
035ms
And
Check is transport "CONTAINER" created in transport table and set transport id
15s 971ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
55s 688ms
And
Go to "TRANSPORT_TABLE"
458ms
When
Go to transport details "CONTAINER"
4s 907ms
And
Expand advice panel
270ms
And
Edit advice in transport details
16s 596ms
And
Fill arrival date field
2s 610ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 499ms
Then
Check advice data in database after edition "CONTAINER"
105ms
After
Hooks.deleteTransportAfterTest()
1s 027ms
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 710ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
034ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
18s 658ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
55s 833ms
And
Go to "TRANSPORT_TABLE"
485ms
When
Go to transport details "TRANSPORT_ORDER"
4s 892ms
And
Expand advice panel
259ms
And
Edit advice in transport details
16s 592ms
And
Fill arrival date field
2s 617ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 440ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
083ms
After
Hooks.deleteTransportAfterTest()
1s 165ms