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"
1s 231ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
002ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "CONTAINER" created in transport table and set transport id
54s 420ms
When
Click button advice in transport table "CONTAINER"
104ms
And
Set advice window in schedule
2s 669ms
And
Fill advice form
14s 828ms
And
Click advice save button and wait for advice form to disappear
30s 777ms
And
Go to "TRANSPORT_TABLE"
214ms
And
Go to transport details "CONTAINER"
4s 524ms
Then
Check are advice values equals
2s 327ms
After
Hooks.deleteTransportAfterTest()
137ms
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"
1s 246ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
002ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 395ms
When
Click button advice in transport table "OWN_COLLECTION"
100ms
And
Set advice window in schedule
2s 577ms
And
Fill advice form
14s 656ms
And
Click advice save button and wait for advice form to disappear
30s 696ms
And
Go to "TRANSPORT_TABLE"
209ms
And
Go to transport details "OWN_COLLECTION"
4s 473ms
Then
Check are advice values equals
2s 337ms
After
Hooks.deleteTransportAfterTest()
161ms
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"
1s 222ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
003ms
And
Add transport by SKApi in "MGW"
003ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 244ms
When
Click button advice in transport table "TRANSPORT_ORDER"
117ms
And
Set advice window in schedule
2s 578ms
And
Fill advice form
14s 739ms
And
Click advice save button and wait for advice form to disappear
30s 718ms
And
Go to "TRANSPORT_TABLE"
238ms
And
Go to transport details "TRANSPORT_ORDER"
4s 479ms
Then
Check are advice values equals
2s 329ms
After
Hooks.deleteTransportAfterTest()
116ms
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"
1s 262ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
002ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 378ms
When
Click button advice in transport table "OWN_COLLECTION"
123ms
And
Set advice window in schedule
2s 554ms
And
Fill advice form
14s 680ms
And
Click advice save button and wait for advice form to disappear
30s 714ms
And
Go to "TRANSPORT_TABLE"
195ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 171ms
After
Hooks.deleteTransportAfterTest()
128ms
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"
1s 250ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
002ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 332ms
When
Click button advice in transport table "CONTAINER"
115ms
And
Set advice window in schedule
2s 518ms
And
Fill advice form
14s 723ms
And
Click advice save button and wait for advice form to disappear
30s 771ms
And
Go to "TRANSPORT_TABLE"
193ms
Then
Check advice data in SK API database "CONTAINER"
4s 111ms
After
Hooks.deleteTransportAfterTest()
135ms
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"
1s 240ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
002ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
6s 225ms
When
Click button advice in transport table "TRANSPORT_ORDER"
102ms
And
Set advice window in schedule
2s 555ms
And
Fill advice form
14s 731ms
And
Click advice save button and wait for advice form to disappear
30s 766ms
And
Go to "TRANSPORT_TABLE"
257ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 041ms
After
Hooks.deleteTransportAfterTest()
108ms
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"
1s 213ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
003ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
002ms
And
Check is transport "CONTAINER" created in transport table and set transport id
9s 349ms
When
Click button advice in transport table "CONTAINER"
108ms
And
Set advice window in schedule in the past
2s 589ms
And
Fill advice form
14s 786ms
And
Click advice save button to check error message
084ms
Then
Check if possible advice alert is displayed
019ms
After
Hooks.deleteTransportAfterTest()
118ms
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"
1s 264ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
003ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
39s 482ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 329ms
And
Go to "TRANSPORT_TABLE"
218ms
When
Go to transport details "OWN_COLLECTION"
4s 501ms
And
Expand advice panel
104ms
And
Edit advice in transport details
14s 088ms
And
Fill arrival date field
2s 310ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 660ms
Then
Check advice data in database after edition "OWN_COLLECTION"
040ms
After
Hooks.deleteTransportAfterTest()
136ms
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"
1s 243ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
002ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
001ms
And
Check is transport "CONTAINER" created in transport table and set transport id
33s 421ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 171ms
And
Go to "TRANSPORT_TABLE"
217ms
When
Go to transport details "CONTAINER"
4s 509ms
And
Expand advice panel
087ms
And
Edit advice in transport details
14s 137ms
And
Fill arrival date field
2s 315ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 629ms
Then
Check advice data in database after edition "CONTAINER"
037ms
After
Hooks.deleteTransportAfterTest()
126ms
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"
1s 255ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
003ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
33s 314ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 243ms
And
Go to "TRANSPORT_TABLE"
248ms
When
Go to transport details "TRANSPORT_ORDER"
4s 489ms
And
Expand advice panel
098ms
And
Edit advice in transport details
14s 122ms
And
Fill arrival date field
2s 312ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 646ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
043ms
After
Hooks.deleteTransportAfterTest()
132ms