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 728ms
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"
016ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 925ms
When
Click button advice in transport table "CONTAINER"
219ms
And
Set advice window in schedule
3s 354ms
And
Fill advice form
17s 705ms
And
Click advice save button and wait for advice form to disappear
33s 227ms
And
Go to "TRANSPORT_TABLE"
432ms
And
Go to transport details "CONTAINER"
2s 905ms
Then
Check are advice values equals
2s 893ms
After
Hooks.deleteTransportAfterTest()
890ms
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 819ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
022ms
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 100ms
When
Click button advice in transport table "OWN_COLLECTION"
227ms
And
Set advice window in schedule
3s 305ms
And
Fill advice form
17s 702ms
And
Click advice save button and wait for advice form to disappear
33s 202ms
And
Go to "TRANSPORT_TABLE"
408ms
And
Go to transport details "OWN_COLLECTION"
2s 923ms
Then
Check are advice values equals
2s 851ms
After
Hooks.deleteTransportAfterTest()
892ms
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 959ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
023ms
And
Add transport by SKApi in "MGW"
027ms
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
3s 633ms
When
Click button advice in transport table "TRANSPORT_ORDER"
247ms
And
Set advice window in schedule
3s 353ms
And
Fill advice form
17s 739ms
And
Click advice save button and wait for advice form to disappear
33s 349ms
And
Go to "TRANSPORT_TABLE"
463ms
And
Go to transport details "TRANSPORT_ORDER"
2s 856ms
Then
Check are advice values equals
2s 870ms
After
Hooks.deleteTransportAfterTest()
885ms
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 "pskza1-carrier-2@qa.qa-test" and set token of apiUsername "super-admin-skz"
7s 813ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
019ms
And
Add transport by SKApi in "MGW"
017ms
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
11s 116ms
When
Click button advice in transport table "TRANSPORT_ORDER"
208ms
And
Set advice window in schedule
3s 331ms
And
Fill advice form
17s 699ms
And
Click advice save button and wait for advice form to disappear
33s 297ms
And
Go to "TRANSPORT_TABLE"
462ms
And
Go to transport details "TRANSPORT_ORDER"
2s 916ms
Then
Check are advice values equals
2s 837ms
After
Hooks.deleteTransportAfterTest()
848ms
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 853ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
019ms
And
Add transport by SKApi in "MGW"
022ms
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 144ms
When
Click button advice in transport table "OWN_COLLECTION"
216ms
And
Set advice window in schedule
3s 383ms
And
Fill advice form
17s 670ms
And
Click advice save button and wait for advice form to disappear
33s 397ms
And
Go to "TRANSPORT_TABLE"
470ms
Then
Check advice data in SK API database "OWN_COLLECTION"
379ms
After
Hooks.deleteTransportAfterTest()
918ms
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 733ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
023ms
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
9s 971ms
When
Click button advice in transport table "CONTAINER"
203ms
And
Set advice window in schedule
3s 366ms
And
Fill advice form
17s 780ms
And
Click advice save button and wait for advice form to disappear
33s 828ms
And
Go to "TRANSPORT_TABLE"
404ms
Then
Check advice data in SK API database "CONTAINER"
234ms
After
Hooks.deleteTransportAfterTest()
904ms
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)
000ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 759ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
024ms
And
Add transport by SKApi in "MGW"
026ms
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
3s 615ms
When
Click button advice in transport table "TRANSPORT_ORDER"
240ms
And
Set advice window in schedule
3s 407ms
And
Fill advice form
17s 729ms
And
Click advice save button and wait for advice form to disappear
33s 269ms
And
Go to "TRANSPORT_TABLE"
435ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
095ms
After
Hooks.deleteTransportAfterTest()
871ms
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 611ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
022ms
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
6s 988ms
When
Click button advice in transport table "CONTAINER"
235ms
And
Set advice window in schedule in the past
3s 345ms
And
Fill advice form
17s 693ms
And
Click advice save button to check error message
179ms
Then
Check if possible advice alert is displayed
068ms
After
Hooks.deleteTransportAfterTest()
589ms
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 721ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
018ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
014ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
7s 224ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
54s 518ms
And
Go to "TRANSPORT_TABLE"
409ms
When
Go to transport details "OWN_COLLECTION"
3s 006ms
And
Expand advice panel
307ms
And
Edit advice in transport details
16s 349ms
And
Fill arrival date field
2s 617ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 253ms
Then
Check advice data in database after edition "OWN_COLLECTION"
088ms
After
Hooks.deleteTransportAfterTest()
896ms
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 808ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
020ms
And
Add transport by SKApi in "MGW"
019ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
016ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 934ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
54s 770ms
And
Go to "TRANSPORT_TABLE"
437ms
When
Go to transport details "CONTAINER"
2s 921ms
And
Expand advice panel
321ms
And
Edit advice in transport details
16s 316ms
And
Fill arrival date field
2s 588ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 195ms
Then
Check advice data in database after edition "CONTAINER"
092ms
After
Hooks.deleteTransportAfterTest()
788ms
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 873ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
019ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
015ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
7s 587ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
54s 617ms
And
Go to "TRANSPORT_TABLE"
499ms
When
Go to transport details "TRANSPORT_ORDER"
2s 868ms
And
Expand advice panel
305ms
And
Edit advice in transport details
16s 403ms
And
Fill arrival date field
2s 589ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 181ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
092ms
After
Hooks.deleteTransportAfterTest()
842ms