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 530ms
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"
017ms
And
Check is transport "CONTAINER" created in transport table and set transport id
3s 872ms
When
Click button advice in transport table "CONTAINER"
206ms
And
Set advice window in schedule
3s 385ms
And
Fill advice form
17s 853ms
And
Click advice save button and wait for advice form to disappear
33s 220ms
And
Go to "TRANSPORT_TABLE"
429ms
And
Go to transport details "CONTAINER"
2s 877ms
Then
Check are advice values equals
2s 944ms
After
Hooks.deleteTransportAfterTest()
911ms
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 656ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
018ms
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 113ms
When
Click button advice in transport table "OWN_COLLECTION"
241ms
And
Set advice window in schedule
3s 348ms
And
Fill advice form
17s 992ms
And
Click advice save button and wait for advice form to disappear
33s 320ms
And
Go to "TRANSPORT_TABLE"
456ms
And
Go to transport details "OWN_COLLECTION"
2s 871ms
Then
Check are advice values equals
2s 845ms
After
Hooks.deleteTransportAfterTest()
830ms
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 674ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
021ms
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
3s 605ms
When
Click button advice in transport table "TRANSPORT_ORDER"
224ms
And
Set advice window in schedule
3s 358ms
And
Fill advice form
17s 973ms
And
Click advice save button and wait for advice form to disappear
33s 257ms
And
Go to "TRANSPORT_TABLE"
439ms
And
Go to transport details "TRANSPORT_ORDER"
2s 862ms
Then
Check are advice values equals
2s 902ms
After
Hooks.deleteTransportAfterTest()
937ms
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 860ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
020ms
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
4s 869ms
When
Click button advice in transport table "TRANSPORT_ORDER"
216ms
And
Set advice window in schedule
3s 286ms
And
Fill advice form
17s 963ms
And
Click advice save button and wait for advice form to disappear
33s 277ms
And
Go to "TRANSPORT_TABLE"
436ms
And
Go to transport details "TRANSPORT_ORDER"
2s 831ms
Then
Check are advice values equals
2s 885ms
After
Hooks.deleteTransportAfterTest()
897ms
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 694ms
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 "CREATE_ADVICE" "super-admin-skz"
016ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
7s 149ms
When
Click button advice in transport table "OWN_COLLECTION"
249ms
And
Set advice window in schedule
3s 378ms
And
Fill advice form
18s 043ms
And
Click advice save button and wait for advice form to disappear
33s 281ms
And
Go to "TRANSPORT_TABLE"
435ms
Then
Check advice data in SK API database "OWN_COLLECTION"
453ms
After
Hooks.deleteTransportAfterTest()
887ms
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 586ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
015ms
And
Check is transport "CONTAINER" created in transport table and set transport id
3s 894ms
When
Click button advice in transport table "CONTAINER"
216ms
And
Set advice window in schedule
3s 345ms
And
Fill advice form
17s 909ms
And
Click advice save button and wait for advice form to disappear
33s 178ms
And
Go to "TRANSPORT_TABLE"
426ms
Then
Check advice data in SK API database "CONTAINER"
208ms
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 582ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
062ms
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
6s 564ms
When
Click button advice in transport table "TRANSPORT_ORDER"
218ms
And
Set advice window in schedule
3s 387ms
And
Fill advice form
17s 893ms
And
Click advice save button and wait for advice form to disappear
33s 387ms
And
Go to "TRANSPORT_TABLE"
446ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
086ms
After
Hooks.deleteTransportAfterTest()
965ms
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"
025ms
And
Add transport by SKApi in "MGW"
027ms
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 969ms
When
Click button advice in transport table "CONTAINER"
243ms
And
Set advice window in schedule in the past
3s 331ms
And
Fill advice form
17s 945ms
And
Click advice save button to check error message
200ms
Then
Check if possible advice alert is displayed
30s 229ms
java.lang.AssertionError: Komunikat o tym, że nie możesz awizować w przeszłości nie pojawił się.
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.assertTrue(Assert.java:41)
at CucumberTests.Transport.AdviceTransport.notPossibleAdviceAlertIsDisplayed(AdviceTransport.java:158)
at ✽.Check if possible advice alert is displayed(file:Features/Atom/SK_API/SkApiTransportAdvice.feature:56)
After
Hooks.deleteTransportAfterTest()
876ms
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 639ms
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 "EDIT_ADVICE" "super-admin-skz"
016ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
4s 091ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
54s 951ms
And
Go to "TRANSPORT_TABLE"
422ms
When
Go to transport details "OWN_COLLECTION"
2s 843ms
And
Expand advice panel
306ms
And
Edit advice in transport details
16s 442ms
And
Fill arrival date field
2s 639ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 298ms
Then
Check advice data in database after edition "OWN_COLLECTION"
111ms
After
Hooks.deleteTransportAfterTest()
921ms
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 628ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
018ms
And
Add transport by SKApi in "MGW"
019ms
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 930ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
54s 695ms
And
Go to "TRANSPORT_TABLE"
470ms
When
Go to transport details "CONTAINER"
2s 933ms
And
Expand advice panel
288ms
And
Edit advice in transport details
16s 578ms
And
Fill arrival date field
2s 613ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 251ms
Then
Check advice data in database after edition "CONTAINER"
107ms
After
Hooks.deleteTransportAfterTest()
800ms
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 732ms
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"
016ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 597ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
54s 999ms
And
Go to "TRANSPORT_TABLE"
452ms
When
Go to transport details "TRANSPORT_ORDER"
2s 838ms
And
Expand advice panel
309ms
And
Edit advice in transport details
16s 611ms
And
Fill arrival date field
2s 631ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 254ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
108ms
After
Hooks.deleteTransportAfterTest()
941ms