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 273ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
001ms
And
Add transport by SKApi in "MGW"
001ms
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 380ms
When
Click button advice in transport table "CONTAINER"
083ms
And
Set advice window in schedule
2s 858ms
And
Fill advice form
14s 557ms
And
Click advice save button and wait for advice form to disappear
30s 731ms
And
Go to "TRANSPORT_TABLE"
302ms
And
Go to transport details "CONTAINER"
4s 548ms
Then
Check are advice values equals
2s 283ms
After
Hooks.deleteTransportAfterTest()
147ms
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 305ms
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 362ms
When
Click button advice in transport table "OWN_COLLECTION"
089ms
And
Set advice window in schedule
2s 607ms
And
Fill advice form
14s 575ms
And
Click advice save button and wait for advice form to disappear
30s 744ms
And
Go to "TRANSPORT_TABLE"
164ms
And
Go to transport details "OWN_COLLECTION"
4s 405ms
Then
Check are advice values equals
2s 273ms
After
Hooks.deleteTransportAfterTest()
115ms
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 238ms
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
3s 191ms
When
Click button advice in transport table "TRANSPORT_ORDER"
086ms
And
Set advice window in schedule
2s 738ms
And
Fill advice form
14s 491ms
And
Click advice save button and wait for advice form to disappear
30s 699ms
And
Go to "TRANSPORT_TABLE"
246ms
And
Go to transport details "TRANSPORT_ORDER"
4s 421ms
Then
Check are advice values equals
2s 278ms
After
Hooks.deleteTransportAfterTest()
111ms
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 244ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
004ms
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 380ms
When
Click button advice in transport table "OWN_COLLECTION"
088ms
And
Set advice window in schedule
2s 556ms
And
Fill advice form
14s 515ms
And
Click advice save button and wait for advice form to disappear
30s 664ms
And
Go to "TRANSPORT_TABLE"
149ms
Then
Check advice data in SK API database "OWN_COLLECTION"
3s 166ms
After
Hooks.deleteTransportAfterTest()
145ms
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 212ms
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 294ms
When
Click button advice in transport table "CONTAINER"
081ms
And
Set advice window in schedule
2s 623ms
And
Fill advice form
14s 495ms
And
Click advice save button and wait for advice form to disappear
30s 688ms
And
Go to "TRANSPORT_TABLE"
162ms
Then
Check advice data in SK API database "CONTAINER"
4s 134ms
After
Hooks.deleteTransportAfterTest()
124ms
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 231ms
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 "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
6s 820ms
When
Click button advice in transport table "TRANSPORT_ORDER"
078ms
And
Set advice window in schedule
2s 570ms
And
Fill advice form
14s 499ms
And
Click advice save button and wait for advice form to disappear
30s 666ms
And
Go to "TRANSPORT_TABLE"
184ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 038ms
After
Hooks.deleteTransportAfterTest()
112ms
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 194ms
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 322ms
When
Click button advice in transport table "CONTAINER"
080ms
And
Set advice window in schedule in the past
2s 602ms
And
Fill advice form
14s 619ms
And
Click advice save button to check error message
084ms
Then
Check if possible advice alert is displayed
015ms
After
Hooks.deleteTransportAfterTest()
128ms
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 236ms
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 "EDIT_ADVICE" "super-admin-skz"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
42s 428ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
47s 979ms
And
Go to "TRANSPORT_TABLE"
187ms
When
Go to transport details "OWN_COLLECTION"
4s 504ms
And
Expand advice panel
089ms
And
Edit advice in transport details
13s 847ms
And
Fill arrival date field
2s 257ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 634ms
Then
Check advice data in database after edition "OWN_COLLECTION"
029ms
After
Hooks.deleteTransportAfterTest()
125ms
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 267ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
001ms
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 425ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 002ms
And
Go to "TRANSPORT_TABLE"
182ms
When
Go to transport details "CONTAINER"
4s 477ms
And
Expand advice panel
099ms
And
Edit advice in transport details
13s 901ms
And
Fill arrival date field
2s 250ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 684ms
Then
Check advice data in database after edition "CONTAINER"
033ms
After
Hooks.deleteTransportAfterTest()
117ms
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 363ms
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 "EDIT_ADVICE" "super-admin-skz"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
33s 328ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 281ms
And
Go to "TRANSPORT_TABLE"
214ms
When
Go to transport details "TRANSPORT_ORDER"
4s 448ms
And
Expand advice panel
088ms
And
Edit advice in transport details
13s 895ms
And
Fill arrival date field
2s 228ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 115ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
033ms
After
Hooks.deleteTransportAfterTest()
115ms