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 598ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
023ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
017ms
And
Check is transport "CONTAINER" created in transport table and set transport id
52s 017ms
When
Click button advice in transport table "CONTAINER"
229ms
And
Set advice window in schedule
3s 395ms
And
Fill advice form
18s 018ms
And
Click advice save button and wait for advice form to disappear
33s 169ms
And
Go to "TRANSPORT_TABLE"
449ms
And
Go to transport details "CONTAINER"
2s 909ms
Then
Check are advice values equals
2s 924ms
After
Hooks.deleteTransportAfterTest()
1s 031ms
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 632ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
023ms
And
Add transport by SKApi in "MGW"
023ms
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
55s 219ms
When
Click button advice in transport table "OWN_COLLECTION"
246ms
And
Set advice window in schedule
3s 366ms
And
Fill advice form
18s 040ms
And
Click advice save button and wait for advice form to disappear
33s 849ms
And
Go to "TRANSPORT_TABLE"
449ms
And
Go to transport details "OWN_COLLECTION"
2s 898ms
Then
Check are advice values equals
2s 910ms
After
Hooks.deleteTransportAfterTest()
975ms
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 757ms
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"
020ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
54s 744ms
When
Click button advice in transport table "TRANSPORT_ORDER"
230ms
And
Set advice window in schedule
3s 385ms
And
Fill advice form
17s 965ms
And
Click advice save button and wait for advice form to disappear
33s 794ms
And
Go to "TRANSPORT_TABLE"
468ms
And
Go to transport details "TRANSPORT_ORDER"
2s 896ms
Then
Check are advice values equals
2s 936ms
After
Hooks.deleteTransportAfterTest()
1s 041ms
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 600ms
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"
017ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
55s 207ms
When
Click button advice in transport table "OWN_COLLECTION"
223ms
And
Set advice window in schedule
3s 358ms
And
Fill advice form
17s 991ms
And
Click advice save button and wait for advice form to disappear
33s 814ms
And
Go to "TRANSPORT_TABLE"
448ms
Then
Check advice data in SK API database "OWN_COLLECTION"
410ms
After
Hooks.deleteTransportAfterTest()
1s 057ms
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 679ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
019ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
019ms
And
Check is transport "CONTAINER" created in transport table and set transport id
1m 1s 017ms
When
Click button advice in transport table "CONTAINER"
230ms
And
Set advice window in schedule
3s 395ms
And
Fill advice form
17s 922ms
And
Click advice save button and wait for advice form to disappear
33s 841ms
And
Go to "TRANSPORT_TABLE"
455ms
Then
Check advice data in SK API database "CONTAINER"
236ms
After
Hooks.deleteTransportAfterTest()
1s 089ms
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 732ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
024ms
And
Add transport by SKApi in "MGW"
019ms
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
58s 517ms
When
Click button advice in transport table "TRANSPORT_ORDER"
245ms
And
Set advice window in schedule
3s 356ms
And
Fill advice form
18s 022ms
And
Click advice save button and wait for advice form to disappear
33s 751ms
And
Go to "TRANSPORT_TABLE"
467ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
090ms
After
Hooks.deleteTransportAfterTest()
1s 123ms
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 752ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
020ms
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 1s 008ms
When
Click button advice in transport table "CONTAINER"
233ms
And
Set advice window in schedule in the past
3s 360ms
And
Fill advice form
18s 084ms
And
Click advice save button to check error message
201ms
Then
Check if possible advice alert is displayed
070ms
After
Hooks.deleteTransportAfterTest()
856ms
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 818ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
023ms
And
Add transport by SKApi in "MGW"
026ms
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 239ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
55s 487ms
And
Go to "TRANSPORT_TABLE"
479ms
When
Go to transport details "OWN_COLLECTION"
2s 908ms
And
Expand advice panel
302ms
And
Edit advice in transport details
16s 735ms
And
Fill arrival date field
2s 565ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 439ms
Then
Check advice data in database after edition "OWN_COLLECTION"
091ms
After
Hooks.deleteTransportAfterTest()
1s 008ms
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 736ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
020ms
And
Add transport by SKApi in "MGW"
024ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
015ms
And
Check is transport "CONTAINER" created in transport table and set transport id
18s 958ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
55s 420ms
And
Go to "TRANSPORT_TABLE"
462ms
When
Go to transport details "CONTAINER"
2s 930ms
And
Expand advice panel
292ms
And
Edit advice in transport details
16s 647ms
And
Fill arrival date field
2s 565ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 437ms
Then
Check advice data in database after edition "CONTAINER"
099ms
After
Hooks.deleteTransportAfterTest()
984ms
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 733ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
016ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
21s 661ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
55s 498ms
And
Go to "TRANSPORT_TABLE"
480ms
When
Go to transport details "TRANSPORT_ORDER"
2s 904ms
And
Expand advice panel
293ms
And
Edit advice in transport details
16s 681ms
And
Fill arrival date field
2s 521ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 383ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
102ms
After
Hooks.deleteTransportAfterTest()
958ms