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 424ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
021ms
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
3s 878ms
When
Click button advice in transport table "CONTAINER"
239ms
And
Set advice window in schedule
3s 329ms
And
Fill advice form
17s 921ms
And
Click advice save button and wait for advice form to disappear
33s 203ms
And
Go to "TRANSPORT_TABLE"
445ms
And
Go to transport details "CONTAINER"
2s 917ms
Then
Check are advice values equals
2s 890ms
After
Hooks.deleteTransportAfterTest()
1s 010ms
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 666ms
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 "CREATE_ADVICE" "super-admin-skz"
015ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
7s 178ms
When
Click button advice in transport table "OWN_COLLECTION"
222ms
And
Set advice window in schedule
3s 313ms
And
Fill advice form
17s 586ms
And
Click advice save button and wait for advice form to disappear
33s 306ms
And
Go to "TRANSPORT_TABLE"
430ms
And
Go to transport details "OWN_COLLECTION"
2s 878ms
Then
Check are advice values equals
2s 900ms
After
Hooks.deleteTransportAfterTest()
825ms
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 734ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
025ms
And
Add transport by SKApi in "MGW"
026ms
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
3s 708ms
When
Click button advice in transport table "TRANSPORT_ORDER"
259ms
And
Set advice window in schedule
3s 401ms
And
Fill advice form
17s 948ms
And
Click advice save button and wait for advice form to disappear
33s 338ms
And
Go to "TRANSPORT_TABLE"
442ms
And
Go to transport details "TRANSPORT_ORDER"
2s 846ms
Then
Check are advice values equals
2s 890ms
After
Hooks.deleteTransportAfterTest()
862ms
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"
8s 031ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "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 "TRANSPORT_ORDER" created in transport table and set transport id
5s 128ms
When
Click button advice in transport table "TRANSPORT_ORDER"
222ms
And
Set advice window in schedule
3s 271ms
And
Fill advice form
17s 918ms
And
Click advice save button and wait for advice form to disappear
33s 325ms
And
Go to "TRANSPORT_TABLE"
449ms
And
Go to transport details "TRANSPORT_ORDER"
2s 843ms
Then
Check are advice values equals
2s 941ms
After
Hooks.deleteTransportAfterTest()
1s 038ms
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 828ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id
7s 130ms
When
Click button advice in transport table "OWN_COLLECTION"
240ms
And
Set advice window in schedule
3s 288ms
And
Fill advice form
18s 027ms
And
Click advice save button and wait for advice form to disappear
33s 298ms
And
Go to "TRANSPORT_TABLE"
439ms
Then
Check advice data in SK API database "OWN_COLLECTION"
446ms
After
Hooks.deleteTransportAfterTest()
985ms
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 731ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
024ms
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
3s 920ms
When
Click button advice in transport table "CONTAINER"
262ms
And
Set advice window in schedule
3s 347ms
And
Fill advice form
17s 911ms
And
Click advice save button and wait for advice form to disappear
33s 234ms
And
Go to "TRANSPORT_TABLE"
416ms
Then
Check advice data in SK API database "CONTAINER"
237ms
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 634ms
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
6s 632ms
When
Click button advice in transport table "TRANSPORT_ORDER"
234ms
And
Set advice window in schedule
3s 321ms
And
Fill advice form
17s 964ms
And
Click advice save button and wait for advice form to disappear
18s 338ms
And
Go to "TRANSPORT_TABLE"
429ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
090ms
After
Hooks.deleteTransportAfterTest()
895ms
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 684ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
021ms
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
4s 065ms
When
Click button advice in transport table "CONTAINER"
243ms
And
Set advice window in schedule in the past
3s 288ms
And
Fill advice form
18s 104ms
And
Click advice save button to check error message
176ms
Then
Check if possible advice alert is displayed
067ms
After
Hooks.deleteTransportAfterTest()
617ms
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 765ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
023ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
016ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
7s 216ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
54s 738ms
And
Go to "TRANSPORT_TABLE"
408ms
When
Go to transport details "OWN_COLLECTION"
2s 856ms
And
Expand advice panel
291ms
And
Edit advice in transport details
16s 587ms
And
Fill arrival date field
2s 665ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 211ms
Then
Check advice data in database after edition "OWN_COLLECTION"
092ms
After
Hooks.deleteTransportAfterTest()
880ms
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 767ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
018ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
017ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 938ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
54s 825ms
And
Go to "TRANSPORT_TABLE"
416ms
When
Go to transport details "CONTAINER"
2s 892ms
And
Expand advice panel
300ms
And
Edit advice in transport details
16s 489ms
And
Fill arrival date field
2s 553ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 193ms
Then
Check advice data in database after edition "CONTAINER"
108ms
After
Hooks.deleteTransportAfterTest()
936ms
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 584ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
019ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
019ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 668ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
54s 902ms
And
Go to "TRANSPORT_TABLE"
467ms
When
Go to transport details "TRANSPORT_ORDER"
2s 863ms
And
Expand advice panel
306ms
And
Edit advice in transport details
16s 392ms
And
Fill arrival date field
2s 602ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 297ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
108ms
After
Hooks.deleteTransportAfterTest()
932ms