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 668ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
023ms
And
Add transport by SKApi in "MGW"
024ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
019ms
And
Check is transport "CONTAINER" created in transport table and set transport id
52s 080ms
When
Click button advice in transport table "CONTAINER"
234ms
And
Set advice window in schedule
3s 964ms
And
Fill advice form
17s 981ms
And
Click advice save button and wait for advice form to disappear
33s 827ms
And
Go to "TRANSPORT_TABLE"
452ms
And
Go to transport details "CONTAINER"
4s 899ms
Then
Check are advice values equals
2s 880ms
After
Hooks.deleteTransportAfterTest()
1s 031ms
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 746ms
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"
016ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
52s 264ms
When
Click button advice in transport table "OWN_COLLECTION"
244ms
And
Set advice window in schedule
4s 024ms
And
Fill advice form
17s 895ms
And
Click advice save button and wait for advice form to disappear
33s 866ms
And
Go to "TRANSPORT_TABLE"
460ms
And
Go to transport details "OWN_COLLECTION"
4s 910ms
Then
Check are advice values equals
2s 897ms
After
Hooks.deleteTransportAfterTest()
1s 034ms
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 728ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
022ms
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
51s 779ms
When
Click button advice in transport table "TRANSPORT_ORDER"
246ms
And
Set advice window in schedule
3s 957ms
And
Fill advice form
18s 040ms
And
Click advice save button and wait for advice form to disappear
33s 929ms
And
Go to "TRANSPORT_TABLE"
490ms
And
Go to transport details "TRANSPORT_ORDER"
4s 871ms
Then
Check are advice values equals
2s 901ms
After
Hooks.deleteTransportAfterTest()
1s 048ms
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 697ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
019ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
52s 239ms
When
Click button advice in transport table "OWN_COLLECTION"
243ms
And
Set advice window in schedule
3s 947ms
And
Fill advice form
17s 894ms
And
Click advice save button and wait for advice form to disappear
33s 893ms
And
Go to "TRANSPORT_TABLE"
445ms
Then
Check advice data in SK API database "OWN_COLLECTION"
415ms
After
Hooks.deleteTransportAfterTest()
1s 052ms
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 605ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
022ms
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
58s 046ms
When
Click button advice in transport table "CONTAINER"
241ms
And
Set advice window in schedule
3s 977ms
And
Fill advice form
17s 986ms
And
Click advice save button and wait for advice form to disappear
18s 338ms
And
Go to "TRANSPORT_TABLE"
416ms
Then
Check advice data in SK API database "CONTAINER"
10s 416ms
After
Hooks.deleteTransportAfterTest()
1s 114ms
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 634ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
023ms
And
Add transport by SKApi in "MGW"
023ms
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
4s 432ms
When
Click button advice in transport table "TRANSPORT_ORDER"
245ms
And
Set advice window in schedule
3s 933ms
And
Fill advice form
17s 961ms
And
Click advice save button and wait for advice form to disappear
33s 836ms
And
Go to "TRANSPORT_TABLE"
454ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
089ms
After
Hooks.deleteTransportAfterTest()
1s 100ms
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 605ms
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"
019ms
And
Check is transport "CONTAINER" created in transport table and set transport id
1m 1s 062ms
When
Click button advice in transport table "CONTAINER"
220ms
And
Set advice window in schedule in the past
3s 991ms
And
Fill advice form
17s 923ms
And
Click advice save button to check error message
196ms
Then
Check if possible advice alert is displayed
30s 159ms
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:154)
at ✽.Check if possible advice alert is displayed(file:Features/Atom/SK_API/SkApiTransportAdvice.feature:55)
After
Hooks.deleteTransportAfterTest()
1s 173ms
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 738ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
024ms
And
Add transport by SKApi in "MGW"
028ms
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
4s 115ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
55s 986ms
And
Go to "TRANSPORT_TABLE"
461ms
When
Go to transport details "OWN_COLLECTION"
4s 872ms
And
Expand advice panel
260ms
And
Edit advice in transport details
16s 525ms
And
Fill arrival date field
2s 553ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 486ms
Then
Check advice data in database after edition "OWN_COLLECTION"
106ms
After
Hooks.deleteTransportAfterTest()
1s 029ms
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 764ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
018ms
And
Add transport by SKApi in "MGW"
024ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
016ms
And
Check is transport "CONTAINER" created in transport table and set transport id
15s 974ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
55s 837ms
And
Go to "TRANSPORT_TABLE"
463ms
When
Go to transport details "CONTAINER"
4s 941ms
And
Expand advice panel
253ms
And
Edit advice in transport details
16s 569ms
And
Fill arrival date field
2s 598ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 479ms
Then
Check advice data in database after edition "CONTAINER"
098ms
After
Hooks.deleteTransportAfterTest()
1s 023ms
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 714ms
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"
017ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
18s 704ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
56s 155ms
And
Go to "TRANSPORT_TABLE"
478ms
When
Go to transport details "TRANSPORT_ORDER"
4s 909ms
And
Expand advice panel
271ms
And
Edit advice in transport details
16s 566ms
And
Fill arrival date field
2s 552ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 416ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
099ms
After
Hooks.deleteTransportAfterTest()
1s 060ms