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.
Before
Hooks.showScenarioName(Scenario)
000ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 669ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
020ms
And
Add transport by SKApi in "MGW"
025ms
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 906ms
When
Click button advice in transport table "CONTAINER"
223ms
And
Set advice window in schedule
3s 370ms
And
Fill advice form
17s 782ms
And
Click advice save button and wait for advice form to disappear
33s 295ms
And
Go to "TRANSPORT_TABLE"
412ms
And
Go to transport details "CONTAINER"
2s 900ms
Then
Check are advice values equals
2s 855ms
After
Hooks.deleteTransportAfterTest()
912ms
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.
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 721ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
024ms
And
Add transport by SKApi in "MGW"
027ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
015ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
7s 097ms
When
Click button advice in transport table "OWN_COLLECTION"
242ms
And
Set advice window in schedule
3s 280ms
And
Fill advice form
17s 792ms
And
Click advice save button and wait for advice form to disappear
33s 226ms
And
Go to "TRANSPORT_TABLE"
395ms
And
Go to transport details "OWN_COLLECTION"
2s 841ms
Then
Check are advice values equals
2s 897ms
After
Hooks.deleteTransportAfterTest()
844ms
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.
Before
Hooks.showScenarioName(Scenario)
000ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 763ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "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 "TRANSPORT_ORDER" created in transport table and set transport id
3s 608ms
When
Click button advice in transport table "TRANSPORT_ORDER"
228ms
And
Set advice window in schedule
3s 340ms
And
Fill advice form
17s 687ms
And
Click advice save button and wait for advice form to disappear
33s 290ms
And
Go to "TRANSPORT_TABLE"
441ms
And
Go to transport details "TRANSPORT_ORDER"
2s 852ms
Then
Check are advice values equals
2s 856ms
After
Hooks.deleteTransportAfterTest()
820ms
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.
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 709ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
019ms
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
10s 112ms
When
Click button advice in transport table "OWN_COLLECTION"
208ms
And
Set advice window in schedule
3s 311ms
And
Fill advice form
17s 766ms
And
Click advice save button and wait for advice form to disappear
33s 275ms
And
Go to "TRANSPORT_TABLE"
467ms
Then
Check advice data in SK API database "OWN_COLLECTION"
438ms
After
Hooks.deleteTransportAfterTest()
835ms
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.
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 744ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
016ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 914ms
When
Click button advice in transport table "CONTAINER"
231ms
And
Set advice window in schedule
3s 325ms
And
Fill advice form
17s 809ms
And
Click advice save button and wait for advice form to disappear
33s 279ms
And
Go to "TRANSPORT_TABLE"
416ms
Then
Check advice data in SK API database "CONTAINER"
231ms
After
Hooks.deleteTransportAfterTest()
905ms
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.
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 712ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
018ms
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
15s 674ms
When
Click button advice in transport table "TRANSPORT_ORDER"
236ms
And
Set advice window in schedule
3s 359ms
And
Fill advice form
17s 748ms
And
Click advice save button and wait for advice form to disappear
33s 210ms
And
Go to "TRANSPORT_TABLE"
495ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
094ms
After
Hooks.deleteTransportAfterTest()
919ms
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
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 687ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
023ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
016ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 908ms
When
Click button advice in transport table "CONTAINER"
218ms
And
Set advice window in schedule in the past
3s 323ms
And
Fill advice form
17s 711ms
And
Click advice save button to check error message
195ms
Then
Check if possible advice alert is displayed
070ms
After
Hooks.deleteTransportAfterTest()
677ms
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.
Before
Hooks.showScenarioName(Scenario)
000ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 593ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
023ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
019ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
4s 121ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
54s 550ms
And
Go to "TRANSPORT_TABLE"
411ms
When
Go to transport details "OWN_COLLECTION"
2s 799ms
And
Expand advice panel
297ms
And
Edit advice in transport details
16s 344ms
And
Fill arrival date field
2s 571ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 249ms
Then
Check advice data in database after edition "OWN_COLLECTION"
105ms
After
Hooks.deleteTransportAfterTest()
938ms
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.
Before
Hooks.showScenarioName(Scenario)
000ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 762ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
017ms
And
Add transport by SKApi in "MGW"
019ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
014ms
And
Check is transport "CONTAINER" created in transport table and set transport id
3s 907ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
54s 587ms
And
Go to "TRANSPORT_TABLE"
417ms
When
Go to transport details "CONTAINER"
2s 923ms
And
Expand advice panel
305ms
And
Edit advice in transport details
16s 316ms
And
Fill arrival date field
2s 563ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 207ms
Then
Check advice data in database after edition "CONTAINER"
106ms
After
Hooks.deleteTransportAfterTest()
904ms
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.
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 720ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
018ms
And
Add transport by SKApi in "MGW"
021ms
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
3s 628ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
54s 671ms
And
Go to "TRANSPORT_TABLE"
454ms
When
Go to transport details "TRANSPORT_ORDER"
2s 849ms
And
Expand advice panel
284ms
And
Edit advice in transport details
16s 304ms
And
Fill arrival date field
2s 592ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 272ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
099ms
After
Hooks.deleteTransportAfterTest()
841ms