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 674ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
022ms
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 034ms
When
Click button advice in transport table "CONTAINER"
235ms
And
Set advice window in schedule
3s 398ms
And
Fill advice form
18s 153ms
And
Click advice save button and wait for advice form to disappear
33s 889ms
And
Go to "TRANSPORT_TABLE"
404ms
And
Go to transport details "CONTAINER"
2s 882ms
Then
Check are advice values equals
2s 858ms
After
Hooks.deleteTransportAfterTest()
978ms
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 659ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
021ms
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"
220ms
And
Set advice window in schedule
3s 435ms
And
Fill advice form
18s 185ms
And
Click advice save button and wait for advice form to disappear
33s 811ms
And
Go to "TRANSPORT_TABLE"
401ms
And
Go to transport details "OWN_COLLECTION"
2s 830ms
Then
Check are advice values equals
2s 858ms
After
Hooks.deleteTransportAfterTest()
1s 095ms
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 731ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "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 "TRANSPORT_ORDER" created in transport table and set transport id
54s 739ms
When
Click button advice in transport table "TRANSPORT_ORDER"
247ms
And
Set advice window in schedule
3s 353ms
And
Fill advice form
18s 027ms
And
Click advice save button and wait for advice form to disappear
33s 867ms
And
Go to "TRANSPORT_TABLE"
492ms
And
Go to transport details "TRANSPORT_ORDER"
2s 881ms
Then
Check are advice values equals
2s 915ms
After
Hooks.deleteTransportAfterTest()
1s 072ms
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 668ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
021ms
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
55s 256ms
When
Click button advice in transport table "OWN_COLLECTION"
225ms
And
Set advice window in schedule
3s 373ms
And
Fill advice form
18s 213ms
And
Click advice save button and wait for advice form to disappear
33s 801ms
And
Go to "TRANSPORT_TABLE"
455ms
Then
Check advice data in SK API database "OWN_COLLECTION"
408ms
After
Hooks.deleteTransportAfterTest()
1s 090ms
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 661ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
018ms
And
Check is transport "CONTAINER" created in transport table and set transport id
58s 023ms
When
Click button advice in transport table "CONTAINER"
236ms
And
Set advice window in schedule
3s 383ms
And
Fill advice form
18s 279ms
And
Click advice save button and wait for advice form to disappear
33s 871ms
And
Go to "TRANSPORT_TABLE"
439ms
Then
Check advice data in SK API database "CONTAINER"
205ms
After
Hooks.deleteTransportAfterTest()
1s 069ms
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 700ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
020ms
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
1m 709ms
When
Click button advice in transport table "TRANSPORT_ORDER"
248ms
And
Set advice window in schedule
3s 334ms
And
Fill advice form
18s 006ms
And
Click advice save button and wait for advice form to disappear
33s 813ms
And
Go to "TRANSPORT_TABLE"
477ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
090ms
After
Hooks.deleteTransportAfterTest()
1s 222ms
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 716ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
024ms
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 1s 028ms
When
Click button advice in transport table "CONTAINER"
238ms
And
Set advice window in schedule in the past
3s 384ms
And
Fill advice form
18s 065ms
And
Click advice save button to check error message
200ms
Then
Check if possible advice alert is displayed
070ms
After
Hooks.deleteTransportAfterTest()
739ms
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 686ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
024ms
And
Add transport by SKApi in "MGW"
022ms
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
34s 224ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
55s 592ms
And
Go to "TRANSPORT_TABLE"
441ms
When
Go to transport details "OWN_COLLECTION"
2s 898ms
And
Expand advice panel
292ms
And
Edit advice in transport details
16s 634ms
And
Fill arrival date field
2s 686ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 497ms
Then
Check advice data in database after edition "OWN_COLLECTION"
105ms
After
Hooks.deleteTransportAfterTest()
1s 085ms
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 688ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
020ms
And
Add transport by SKApi in "MGW"
022ms
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 974ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
55s 586ms
And
Go to "TRANSPORT_TABLE"
474ms
When
Go to transport details "CONTAINER"
2s 898ms
And
Expand advice panel
292ms
And
Edit advice in transport details
16s 657ms
And
Fill arrival date field
2s 636ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 495ms
Then
Check advice data in database after edition "CONTAINER"
094ms
After
Hooks.deleteTransportAfterTest()
979ms
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 659ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
020ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
017ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
18s 683ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
55s 766ms
And
Go to "TRANSPORT_TABLE"
411ms
When
Go to transport details "TRANSPORT_ORDER"
2s 821ms
And
Expand advice panel
229ms
And
Edit advice in transport details
16s 306ms
And
Fill arrival date field
2s 607ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 503ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
096ms
After
Hooks.deleteTransportAfterTest()
1s 249ms