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 552ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
020ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
015ms
And
Check is transport "CONTAINER" created in transport table and set transport id
3s 891ms
When
Click button advice in transport table "CONTAINER"
217ms
And
Set advice window in schedule
3s 311ms
And
Fill advice form
17s 955ms
And
Click advice save button and wait for advice form to disappear
33s 312ms
And
Go to "TRANSPORT_TABLE"
399ms
And
Go to transport details "CONTAINER"
2s 881ms
Then
Check are advice values equals
2s 906ms
After
Hooks.deleteTransportAfterTest()
986ms
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 684ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
023ms
And
Add transport by SKApi in "MGW"
024ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
016ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
7s 081ms
When
Click button advice in transport table "OWN_COLLECTION"
238ms
And
Set advice window in schedule
3s 329ms
And
Fill advice form
18s 095ms
And
Click advice save button and wait for advice form to disappear
33s 337ms
And
Go to "TRANSPORT_TABLE"
435ms
And
Go to transport details "OWN_COLLECTION"
2s 900ms
Then
Check are advice values equals
2s 977ms
After
Hooks.deleteTransportAfterTest()
865ms
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 605ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
019ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
016ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 626ms
When
Click button advice in transport table "TRANSPORT_ORDER"
224ms
And
Set advice window in schedule
3s 369ms
And
Fill advice form
17s 947ms
And
Click advice save button and wait for advice form to disappear
18s 375ms
And
Go to "TRANSPORT_TABLE"
438ms
And
Go to transport details "TRANSPORT_ORDER"
2s 893ms
Then
Check are advice values equals
2s 896ms
After
Hooks.deleteTransportAfterTest()
973ms
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 699ms
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"
015ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
7s 115ms
When
Click button advice in transport table "OWN_COLLECTION"
243ms
And
Set advice window in schedule
3s 330ms
And
Fill advice form
17s 912ms
And
Click advice save button and wait for advice form to disappear
33s 878ms
And
Go to "TRANSPORT_TABLE"
439ms
Then
Check advice data in SK API database "OWN_COLLECTION"
402ms
After
Hooks.deleteTransportAfterTest()
892ms
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 688ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
018ms
And
Check is transport "CONTAINER" created in transport table and set transport id
3s 914ms
When
Click button advice in transport table "CONTAINER"
216ms
And
Set advice window in schedule
3s 330ms
And
Fill advice form
18s 022ms
And
Click advice save button and wait for advice form to disappear
33s 993ms
And
Go to "TRANSPORT_TABLE"
440ms
Then
Check advice data in SK API database "CONTAINER"
239ms
After
Hooks.deleteTransportAfterTest()
939ms
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 762ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "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 "TRANSPORT_ORDER" created in transport table and set transport id
3s 579ms
When
Click button advice in transport table "TRANSPORT_ORDER"
218ms
And
Set advice window in schedule
3s 389ms
And
Fill advice form
17s 721ms
And
Click advice save button and wait for advice form to disappear
33s 854ms
And
Go to "TRANSPORT_TABLE"
437ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
088ms
After
Hooks.deleteTransportAfterTest()
966ms
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 617ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
025ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
016ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 904ms
When
Click button advice in transport table "CONTAINER"
229ms
And
Set advice window in schedule in the past
3s 307ms
And
Fill advice form
17s 895ms
And
Click advice save button to check error message
182ms
Then
Check if possible advice alert is displayed
067ms
After
Hooks.deleteTransportAfterTest()
642ms
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 640ms
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 "EDIT_ADVICE" "super-admin-skz"
016ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
4s 165ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
54s 875ms
And
Go to "TRANSPORT_TABLE"
409ms
When
Go to transport details "OWN_COLLECTION"
2s 849ms
And
Expand advice panel
302ms
And
Edit advice in transport details
16s 601ms
And
Fill arrival date field
2s 629ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 218ms
Then
Check advice data in database after edition "OWN_COLLECTION"
105ms
After
Hooks.deleteTransportAfterTest()
904ms
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 657ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
019ms
And
Add transport by SKApi in "MGW"
019ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
016ms
And
Check is transport "CONTAINER" created in transport table and set transport id
3s 954ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
40s 085ms
And
Go to "TRANSPORT_TABLE"
403ms
When
Go to transport details "CONTAINER"
2s 906ms
And
Expand advice panel
305ms
And
Edit advice in transport details
16s 556ms
And
Fill arrival date field
2s 643ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 295ms
Then
Check advice data in database after edition "CONTAINER"
106ms
After
Hooks.deleteTransportAfterTest()
925ms
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 712ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
019ms
And
Add transport by SKApi in "MGW"
020ms
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
3s 602ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
55s 070ms
And
Go to "TRANSPORT_TABLE"
458ms
When
Go to transport details "TRANSPORT_ORDER"
2s 855ms
And
Expand advice panel
276ms
And
Edit advice in transport details
16s 572ms
And
Fill arrival date field
2s 658ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 251ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
096ms
After
Hooks.deleteTransportAfterTest()
853ms