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 484ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 481ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW" assigned to ""
022ms
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 961ms
When
Click button advice in transport table "CONTAINER"
219ms
And
Set advice window in schedule
3s 350ms
And
Fill advice form
17s 697ms
And
Click advice save button and wait for advice form to disappear
33s 218ms
And
Go to "TRANSPORT_TABLE"
440ms
And
Go to transport details "CONTAINER"
2s 910ms
Then
Check are advice values equals
2s 932ms
After
Hooks.deleteTransportAfterTest()
923ms
After
Hooks.cleanUserDetailsAfterTest()
2s 178ms
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"
8s 045ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 421ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
025ms
And
Add transport by SKApi in "MGW" assigned to ""
019ms
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
4s 114ms
When
Click button advice in transport table "OWN_COLLECTION"
227ms
And
Set advice window in schedule
3s 352ms
And
Fill advice form
17s 923ms
And
Click advice save button and wait for advice form to disappear
33s 229ms
And
Go to "TRANSPORT_TABLE"
443ms
And
Go to transport details "OWN_COLLECTION"
2s 904ms
Then
Check are advice values equals
2s 897ms
After
Hooks.deleteTransportAfterTest()
955ms
After
Hooks.cleanUserDetailsAfterTest()
2s 112ms
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"
7s 622ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 378ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
026ms
And
Add transport by SKApi in "MGW" assigned to ""
021ms
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
7s 309ms
When
Click button advice in transport table "TRANSPORT_ORDER"
231ms
And
Set advice window in schedule
3s 322ms
And
Fill advice form
18s 049ms
And
Click advice save button and wait for advice form to disappear
33s 265ms
And
Go to "TRANSPORT_TABLE"
503ms
And
Go to transport details "TRANSPORT_ORDER"
2s 985ms
Then
Check are advice values equals
2s 826ms
After
Hooks.deleteTransportAfterTest()
928ms
After
Hooks.cleanUserDetailsAfterTest()
2s 358ms
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 "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz"
8s 973ms
And
Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file
3s 580ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW" assigned to ""
017ms
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
6s 724ms
When
Click button advice in transport table "TRANSPORT_ORDER"
217ms
And
Set advice window in schedule
3s 474ms
And
Fill advice form
18s 143ms
And
Click advice save button and wait for advice form to disappear
33s 842ms
And
Go to "TRANSPORT_TABLE"
444ms
And
Go to transport details "TRANSPORT_ORDER"
2s 846ms
Then
Check are advice values equals
2s 897ms
After
Hooks.deleteTransportAfterTest()
833ms
After
Hooks.cleanUserDetailsAfterTest()
2s 904ms
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-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz"
7s 580ms
And
Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file
1s 812ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
020ms
And
Add transport by SKApi in "MGW" assigned to "automaty@test.pl"
021ms
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
4s 488ms
When
Click button advice in transport table "TRANSPORT_ORDER"
207ms
And
Set advice window in schedule
30s 608ms
org.openqa.selenium.TimeoutException: Expected condition failed: waiting for visibility of element located by By.xpath: //div[contains(@class, 'success-alert')] (tried for 30 second(s) with 500 MILLISECONDS interval)
at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
at Pages.BasePage.checkElementIsVisible(BasePage.java:177)
at CucumberTests.Transport.AdviceTransport.setAdviceWindowInSchedule(AdviceTransport.java:85)
at ✽.Set advice window in schedule(file:Features/Atom/SK_API/SkApiTransportAdvice.feature:13)
Caused by: org.openqa.selenium.NoSuchElementException: Cannot locate an element using By.xpath: //div[contains(@class, 'success-alert')]
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test-2', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-50-generic', java.version: '1.8.0_292'
Driver info: driver.version: unknown
at org.openqa.selenium.support.ui.ExpectedConditions.lambda$findElement$0(ExpectedConditions.java:882)
at java.util.Optional.orElseThrow(Optional.java:290)
at org.openqa.selenium.support.ui.ExpectedConditions.findElement(ExpectedConditions.java:881)
at org.openqa.selenium.support.ui.ExpectedConditions.access$000(ExpectedConditions.java:43)
at org.openqa.selenium.support.ui.ExpectedConditions$7.apply(ExpectedConditions.java:205)
at org.openqa.selenium.support.ui.ExpectedConditions$7.apply(ExpectedConditions.java:201)
at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208)
at Pages.BasePage.checkElementIsVisible(BasePage.java:177)
at CucumberTests.Transport.AdviceTransport.setAdviceWindowInSchedule(AdviceTransport.java:85)
at sun.reflect.GeneratedMethodAccessor238.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at cucumber.runtime.Utils$1.call(Utils.java:26)
at cucumber.runtime.Timeout.timeout(Timeout.java:16)
at cucumber.runtime.Utils.invoke(Utils.java:20)
at cucumber.runtime.java.JavaStepDefinition.execute(JavaStepDefinition.java:57)
at cucumber.runner.PickleStepDefinitionMatch.runStep(PickleStepDefinitionMatch.java:50)
at cucumber.runner.TestStep.executeStep(TestStep.java:63)
at cucumber.runner.TestStep.run(TestStep.java:49)
at cucumber.runner.PickleStepTestStep.run(PickleStepTestStep.java:43)
at cucumber.runner.TestCase.run(TestCase.java:45)
at cucumber.runner.Runner.runPickle(Runner.java:40)
at cucumber.runtime.junit.PickleRunners$WithStepDescriptions.run(PickleRunners.java:97)
at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
And
Fill advice form
000ms
And
Click advice save button and wait for advice form to disappear
000ms
And
Go to "TRANSPORT_TABLE"
000ms
And
Go to transport details "TRANSPORT_ORDER"
000ms
Then
Check are advice values equals
000ms
After
Hooks.deleteTransportAfterTest()
567ms
After
Hooks.cleanUserDetailsAfterTest()
1s 840ms
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"
7s 818ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 387ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
020ms
And
Add transport by SKApi in "MGW" assigned to ""
017ms
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 132ms
When
Click button advice in transport table "OWN_COLLECTION"
229ms
And
Set advice window in schedule
3s 315ms
And
Fill advice form
17s 988ms
And
Click advice save button and wait for advice form to disappear
33s 386ms
And
Go to "TRANSPORT_TABLE"
407ms
Then
Check advice data in SK API database "OWN_COLLECTION"
393ms
After
Hooks.deleteTransportAfterTest()
845ms
After
Hooks.cleanUserDetailsAfterTest()
2s 163ms
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"
7s 440ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 416ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW" assigned to ""
017ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
015ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 956ms
When
Click button advice in transport table "CONTAINER"
215ms
And
Set advice window in schedule
3s 319ms
And
Fill advice form
18s 012ms
And
Click advice save button and wait for advice form to disappear
33s 297ms
And
Go to "TRANSPORT_TABLE"
447ms
Then
Check advice data in SK API database "CONTAINER"
190ms
After
Hooks.deleteTransportAfterTest()
884ms
After
Hooks.cleanUserDetailsAfterTest()
2s 261ms
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"
7s 718ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 384ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
020ms
And
Add transport by SKApi in "MGW" assigned to ""
017ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
014ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
4s 445ms
When
Click button advice in transport table "TRANSPORT_ORDER"
211ms
And
Set advice window in schedule
3s 426ms
And
Fill advice form
17s 936ms
And
Click advice save button and wait for advice form to disappear
18s 335ms
And
Go to "TRANSPORT_TABLE"
458ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
094ms
After
Hooks.deleteTransportAfterTest()
985ms
After
Hooks.cleanUserDetailsAfterTest()
2s 084ms
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 "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz"
6s 404ms
And
Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file
3s 545ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW" assigned to ""
020ms
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 825ms
When
Click button advice in transport table "TRANSPORT_ORDER"
209ms
And
Set advice window in schedule
3s 387ms
And
Fill advice form
17s 952ms
And
Click advice save button and wait for advice form to disappear
33s 336ms
And
Go to "TRANSPORT_TABLE"
439ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
087ms
After
Hooks.deleteTransportAfterTest()
936ms
After
Hooks.cleanUserDetailsAfterTest()
2s 911ms
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-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz"
8s 586ms
And
Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file
1s 876ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW" assigned to "automaty@test.pl"
017ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
013ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
7s 538ms
When
Click button advice in transport table "TRANSPORT_ORDER"
225ms
And
Set advice window in schedule
3s 354ms
And
Fill advice form
17s 654ms
And
Click advice save button and wait for advice form to disappear
33s 814ms
And
Go to "TRANSPORT_TABLE"
442ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
282ms
After
Hooks.deleteTransportAfterTest()
889ms
After
Hooks.cleanUserDetailsAfterTest()
1s 730ms
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"
7s 511ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW" assigned to ""
021ms
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 941ms
When
Click button advice in transport table "CONTAINER"
208ms
And
Set advice window in schedule in the past
3s 352ms
And
Fill advice form
18s 004ms
And
Click advice save button to check error message
203ms
Then
Check if possible advice alert is displayed
078ms
After
Hooks.deleteTransportAfterTest()
716ms
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)
009ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 702ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW" assigned to ""
022ms
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 175ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
54s 677ms
And
Go to "TRANSPORT_TABLE"
419ms
When
Go to transport details "OWN_COLLECTION"
2s 849ms
And
Expand advice panel
316ms
And
Edit advice in transport details
16s 637ms
And
Fill arrival date field
2s 656ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 180ms
Then
Check advice data in database after edition "OWN_COLLECTION"
111ms
After
Hooks.deleteTransportAfterTest()
969ms
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 833ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
017ms
And
Add transport by SKApi in "MGW" assigned to ""
020ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
016ms
And
Check is transport "CONTAINER" created in transport table and set transport id
3s 905ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
39s 931ms
And
Go to "TRANSPORT_TABLE"
477ms
When
Go to transport details "CONTAINER"
2s 891ms
And
Expand advice panel
298ms
And
Edit advice in transport details
16s 507ms
And
Fill arrival date field
2s 624ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 189ms
Then
Check advice data in database after edition "CONTAINER"
089ms
After
Hooks.deleteTransportAfterTest()
917ms
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 665ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
018ms
And
Add transport by SKApi in "MGW" assigned to ""
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
3s 627ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
54s 968ms
And
Go to "TRANSPORT_TABLE"
433ms
When
Go to transport details "TRANSPORT_ORDER"
2s 845ms
And
Expand advice panel
306ms
And
Edit advice in transport details
16s 473ms
And
Fill arrival date field
2s 632ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 295ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
117ms
After
Hooks.deleteTransportAfterTest()
929ms