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 720ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
023ms
And
Add transport by SKApi in "MGW"
024ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
017ms
And
Check is transport "CONTAINER" created in transport table and set transport id
52s 002ms
When
Click button advice in transport table "CONTAINER"
241ms
And
Set advice window in schedule
3s 519ms
And
Fill advice form
18s 116ms
And
Click advice save button and wait for advice form to disappear
33s 931ms
And
Go to "TRANSPORT_TABLE"
467ms
And
Go to transport details "CONTAINER"
4s 961ms
Then
Check are advice values equals
2s 866ms
After
Hooks.deleteTransportAfterTest()
967ms
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 623ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
018ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
52s 265ms
When
Click button advice in transport table "OWN_COLLECTION"
234ms
And
Set advice window in schedule
3s 576ms
And
Fill advice form
18s 139ms
And
Click advice save button and wait for advice form to disappear
33s 874ms
And
Go to "TRANSPORT_TABLE"
454ms
And
Go to transport details "OWN_COLLECTION"
4s 830ms
Then
Check are advice values equals
2s 896ms
After
Hooks.deleteTransportAfterTest()
1s 040ms
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 732ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
023ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
017ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
51s 764ms
When
Click button advice in transport table "TRANSPORT_ORDER"
237ms
And
Set advice window in schedule
3s 473ms
And
Fill advice form
18s 008ms
And
Click advice save button and wait for advice form to disappear
33s 882ms
And
Go to "TRANSPORT_TABLE"
531ms
And
Go to transport details "TRANSPORT_ORDER"
4s 888ms
Then
Check are advice values equals
2s 898ms
After
Hooks.deleteTransportAfterTest()
952ms
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 660ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
019ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
017ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
52s 241ms
When
Click button advice in transport table "OWN_COLLECTION"
239ms
And
Set advice window in schedule
3s 456ms
And
Fill advice form
18s 179ms
And
Click advice save button and wait for advice form to disappear
33s 836ms
And
Go to "TRANSPORT_TABLE"
457ms
Then
Check advice data in SK API database "OWN_COLLECTION"
414ms
After
Hooks.deleteTransportAfterTest()
1s 079ms
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 624ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
023ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
020ms
And
Check is transport "CONTAINER" created in transport table and set transport id
58s 027ms
When
Click button advice in transport table "CONTAINER"
236ms
And
Set advice window in schedule
3s 760ms
And
Fill advice form
18s 130ms
And
Click advice save button and wait for advice form to disappear
33s 830ms
And
Go to "TRANSPORT_TABLE"
471ms
Then
Check advice data in SK API database "CONTAINER"
242ms
After
Hooks.deleteTransportAfterTest()
1s 059ms
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 644ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
019ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
015ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
1m 677ms
When
Click button advice in transport table "TRANSPORT_ORDER"
252ms
And
Set advice window in schedule
3s 550ms
And
Fill advice form
18s 181ms
And
Click advice save button and wait for advice form to disappear
33s 934ms
And
Go to "TRANSPORT_TABLE"
495ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
091ms
After
Hooks.deleteTransportAfterTest()
1s 039ms
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 659ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
018ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
019ms
And
Check is transport "CONTAINER" created in transport table and set transport id
1m 1s 034ms
When
Click button advice in transport table "CONTAINER"
230ms
And
Set advice window in schedule in the past
3s 451ms
And
Fill advice form
18s 034ms
And
Click advice save button to check error message
196ms
Then
Check if possible advice alert is displayed
072ms
After
Hooks.deleteTransportAfterTest()
801ms
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 698ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
025ms
And
Add transport by SKApi in "MGW"
024ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
018ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
34s 246ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
55s 649ms
And
Go to "TRANSPORT_TABLE"
469ms
When
Go to transport details "OWN_COLLECTION"
4s 882ms
And
Expand advice panel
266ms
And
Edit advice in transport details
16s 516ms
And
Fill arrival date field
2s 632ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 538ms
Then
Check advice data in database after edition "OWN_COLLECTION"
103ms
After
Hooks.deleteTransportAfterTest()
1s 054ms
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 732ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
019ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
016ms
And
Check is transport "CONTAINER" created in transport table and set transport id
15s 959ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
55s 680ms
And
Go to "TRANSPORT_TABLE"
431ms
When
Go to transport details "CONTAINER"
4s 929ms
And
Expand advice panel
262ms
And
Edit advice in transport details
16s 544ms
And
Fill arrival date field
2s 549ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 505ms
Then
Check advice data in database after edition "CONTAINER"
106ms
After
Hooks.deleteTransportAfterTest()
1s 103ms
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 758ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
023ms
And
Add transport by SKApi in "MGW"
026ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
018ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
18s 675ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
55s 628ms
And
Go to "TRANSPORT_TABLE"
478ms
When
Go to transport details "TRANSPORT_ORDER"
4s 887ms
And
Expand advice panel
279ms
And
Edit advice in transport details
16s 613ms
And
Fill arrival date field
2s 628ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 469ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
096ms
After
Hooks.deleteTransportAfterTest()
1s 120ms