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 855ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
020ms
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
51s 983ms
When
Click button advice in transport table "CONTAINER"
218ms
And
Set advice window in schedule
3s 636ms
And
Fill advice form
18s 049ms
And
Click advice save button and wait for advice form to disappear
33s 845ms
And
Go to "TRANSPORT_TABLE"
451ms
And
Go to transport details "CONTAINER"
4s 911ms
Then
Check are advice values equals
2s 912ms
After
Hooks.deleteTransportAfterTest()
968ms
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 687ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
020ms
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 225ms
When
Click button advice in transport table "OWN_COLLECTION"
227ms
And
Set advice window in schedule
3s 481ms
And
Fill advice form
18s 130ms
And
Click advice save button and wait for advice form to disappear
33s 823ms
And
Go to "TRANSPORT_TABLE"
491ms
And
Go to transport details "OWN_COLLECTION"
4s 926ms
Then
Check are advice values equals
2s 914ms
After
Hooks.deleteTransportAfterTest()
950ms
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 710ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
020ms
And
Add transport by SKApi in "MGW"
024ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
019ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
51s 727ms
When
Click button advice in transport table "TRANSPORT_ORDER"
195ms
And
Set advice window in schedule
3s 562ms
And
Fill advice form
18s 082ms
And
Click advice save button and wait for advice form to disappear
33s 913ms
And
Go to "TRANSPORT_TABLE"
503ms
And
Go to transport details "TRANSPORT_ORDER"
4s 843ms
Then
Check are advice values equals
2s 902ms
After
Hooks.deleteTransportAfterTest()
1s 139ms
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 753ms
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"
027ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
52s 184ms
When
Click button advice in transport table "OWN_COLLECTION"
200ms
And
Set advice window in schedule
3s 522ms
And
Fill advice form
18s 042ms
And
Click advice save button and wait for advice form to disappear
33s 881ms
And
Go to "TRANSPORT_TABLE"
461ms
Then
Check advice data in SK API database "OWN_COLLECTION"
446ms
After
Hooks.deleteTransportAfterTest()
1s 004ms
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 723ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
020ms
And
Add transport by SKApi in "MGW"
026ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
017ms
And
Check is transport "CONTAINER" created in transport table and set transport id
1m 994ms
When
Click button advice in transport table "CONTAINER"
225ms
And
Set advice window in schedule
3s 494ms
And
Click advice save button and wait for advice form to disappear
33s 818ms
And
Go to "TRANSPORT_TABLE"
455ms
Then
Check advice data in SK API database "CONTAINER"
203ms
After
Hooks.deleteTransportAfterTest()
1s 088ms
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 523ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
024ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
019ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
58s 619ms
When
Click button advice in transport table "TRANSPORT_ORDER"
195ms
And
Set advice window in schedule
3s 477ms
And
Fill advice form
18s 140ms
And
Click advice save button and wait for advice form to disappear
33s 857ms
And
Go to "TRANSPORT_TABLE"
485ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
094ms
After
Hooks.deleteTransportAfterTest()
1s 162ms
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 646ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
019ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
018ms
And
Check is transport "CONTAINER" created in transport table and set transport id
1m 996ms
When
Click button advice in transport table "CONTAINER"
230ms
And
Set advice window in schedule in the past
3s 638ms
And
Fill advice form
17s 958ms
And
Click advice save button to check error message
191ms
Then
Check if possible advice alert is displayed
065ms
After
Hooks.deleteTransportAfterTest()
793ms
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 955ms
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 "EDIT_ADVICE" "super-admin-skz"
018ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
34s 247ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
55s 494ms
And
Go to "TRANSPORT_TABLE"
468ms
When
Go to transport details "OWN_COLLECTION"
4s 885ms
And
Expand advice panel
265ms
And
Edit advice in transport details
16s 599ms
And
Fill arrival date field
2s 644ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 487ms
Then
Check advice data in database after edition "OWN_COLLECTION"
105ms
After
Hooks.deleteTransportAfterTest()
1s 030ms
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 769ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
020ms
And
Add transport by SKApi in "MGW"
023ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
020ms
And
Check is transport "CONTAINER" created in transport table and set transport id
18s 986ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
55s 612ms
And
Go to "TRANSPORT_TABLE"
460ms
When
Go to transport details "CONTAINER"
4s 914ms
And
Expand advice panel
256ms
And
Edit advice in transport details
16s 639ms
And
Fill arrival date field
2s 605ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 458ms
Then
Check advice data in database after edition "CONTAINER"
105ms
After
Hooks.deleteTransportAfterTest()
1s 138ms
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 666ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
019ms
And
Add transport by SKApi in "MGW"
027ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
020ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
15s 693ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
55s 648ms
And
Go to "TRANSPORT_TABLE"
511ms
When
Go to transport details "TRANSPORT_ORDER"
4s 933ms
And
Expand advice panel
258ms
And
Edit advice in transport details
16s 608ms
And
Fill arrival date field
2s 585ms
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"
100ms
After
Hooks.deleteTransportAfterTest()
1s 134ms