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 431ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
023ms
And
Add transport by SKApi in "MGW"
025ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
017ms
And
Check is transport "CONTAINER" created in transport table and set transport id
3s 907ms
When
Click button advice in transport table "CONTAINER"
235ms
And
Set advice window in schedule
3s 301ms
And
Fill advice form
17s 665ms
And
Click advice save button and wait for advice form to disappear
33s 275ms
And
Go to "TRANSPORT_TABLE"
397ms
And
Go to transport details "CONTAINER"
2s 853ms
Then
Check are advice values equals
2s 845ms
After
Hooks.deleteTransportAfterTest()
827ms
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 656ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
019ms
And
Add transport by SKApi in "MGW"
020ms
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 077ms
When
Click button advice in transport table "OWN_COLLECTION"
209ms
And
Set advice window in schedule
3s 245ms
And
Fill advice form
17s 568ms
And
Click advice save button and wait for advice form to disappear
33s 129ms
And
Go to "TRANSPORT_TABLE"
403ms
And
Go to transport details "OWN_COLLECTION"
2s 853ms
Then
Check are advice values equals
2s 817ms
After
Hooks.deleteTransportAfterTest()
828ms
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 525ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
021ms
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
4s 339ms
When
Click button advice in transport table "TRANSPORT_ORDER"
198ms
And
Set advice window in schedule
3s 267ms
And
Fill advice form
17s 659ms
And
Click advice save button and wait for advice form to disappear
33s 241ms
And
Go to "TRANSPORT_TABLE"
447ms
And
Go to transport details "TRANSPORT_ORDER"
2s 786ms
Then
Check are advice values equals
2s 815ms
After
Hooks.deleteTransportAfterTest()
945ms
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 545ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
023ms
And
Add transport by SKApi in "MGW"
021ms
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
7s 080ms
When
Click button advice in transport table "OWN_COLLECTION"
212ms
And
Set advice window in schedule
3s 300ms
And
Fill advice form
17s 557ms
And
Click advice save button and wait for advice form to disappear
33s 201ms
And
Go to "TRANSPORT_TABLE"
379ms
Then
Check advice data in SK API database "OWN_COLLECTION"
402ms
After
Hooks.deleteTransportAfterTest()
963ms
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 632ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
017ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
015ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 908ms
When
Click button advice in transport table "CONTAINER"
223ms
And
Set advice window in schedule
3s 314ms
And
Fill advice form
17s 541ms
And
Click advice save button and wait for advice form to disappear
33s 276ms
And
Go to "TRANSPORT_TABLE"
389ms
Then
Check advice data in SK API database "CONTAINER"
224ms
After
Hooks.deleteTransportAfterTest()
915ms
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 626ms
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"
016ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
6s 607ms
When
Click button advice in transport table "TRANSPORT_ORDER"
235ms
And
Set advice window in schedule
3s 274ms
And
Fill advice form
17s 558ms
And
Click advice save button and wait for advice form to disappear
33s 854ms
And
Go to "TRANSPORT_TABLE"
424ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
080ms
After
Hooks.deleteTransportAfterTest()
960ms
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 499ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
016ms
And
Check is transport "CONTAINER" created in transport table and set transport id
3s 928ms
When
Click button advice in transport table "CONTAINER"
205ms
And
Set advice window in schedule in the past
3s 238ms
And
Fill advice form
17s 543ms
And
Click advice save button to check error message
177ms
Then
Check if possible advice alert is displayed
066ms
After
Hooks.deleteTransportAfterTest()
586ms
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 529ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
024ms
And
Add transport by SKApi in "MGW"
023ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
017ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
7s 084ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
54s 391ms
And
Go to "TRANSPORT_TABLE"
374ms
When
Go to transport details "OWN_COLLECTION"
2s 819ms
And
Expand advice panel
261ms
And
Edit advice in transport details
16s 205ms
And
Fill arrival date field
2s 604ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 433ms
Then
Check advice data in database after edition "OWN_COLLECTION"
091ms
After
Hooks.deleteTransportAfterTest()
899ms
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 495ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
016ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
015ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 919ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
54s 419ms
And
Go to "TRANSPORT_TABLE"
400ms
When
Go to transport details "CONTAINER"
2s 941ms
And
Expand advice panel
259ms
And
Edit advice in transport details
16s 269ms
And
Fill arrival date field
2s 578ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 503ms
Then
Check advice data in database after edition "CONTAINER"
086ms
After
Hooks.deleteTransportAfterTest()
978ms
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 622ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
017ms
And
Add transport by SKApi in "MGW"
022ms
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
6s 628ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
54s 845ms
And
Go to "TRANSPORT_TABLE"
398ms
When
Go to transport details "TRANSPORT_ORDER"
2s 790ms
And
Expand advice panel
264ms
And
Edit advice in transport details
16s 191ms
And
Fill arrival date field
2s 558ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 423ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
083ms
After
Hooks.deleteTransportAfterTest()
1s 115ms