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"
1s 110ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
367ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
037ms
And
Add transport by SKApi in "MGW" assigned to ""
003ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
034ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 305ms
When
Click button advice in transport table "CONTAINER"
086ms
And
Set advice window in schedule
2s 528ms
And
Fill advice form
16s 843ms
And
Click advice save button and wait for advice form to disappear
30s 704ms
And
Go to "TRANSPORT_TABLE"
157ms
And
Go to transport details "CONTAINER"
2s 463ms
Then
Check are advice values equals
4s 363ms
After
Hooks.deleteTransportAfterTest()
099ms
After
Hooks.cleanUserDetailsAfterTest()
289ms
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"
1s 891ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
329ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
036ms
And
Add transport by SKApi in "MGW" assigned to ""
003ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 373ms
When
Click button advice in transport table "OWN_COLLECTION"
091ms
And
Set advice window in schedule
2s 547ms
And
Fill advice form
16s 713ms
And
Click advice save button and wait for advice form to disappear
30s 782ms
And
Go to "TRANSPORT_TABLE"
200ms
And
Go to transport details "OWN_COLLECTION"
2s 451ms
Then
Check are advice values equals
4s 332ms
After
Hooks.deleteTransportAfterTest()
126ms
After
Hooks.cleanUserDetailsAfterTest()
280ms
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"
1s 870ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
349ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
038ms
And
Add transport by SKApi in "MGW" assigned to ""
003ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
034ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
5s 805ms
When
Click button advice in transport table "TRANSPORT_ORDER"
092ms
And
Set advice window in schedule
2s 572ms
And
Fill advice form
16s 756ms
And
Click advice save button and wait for advice form to disappear
30s 725ms
And
Go to "TRANSPORT_TABLE"
209ms
And
Go to transport details "TRANSPORT_ORDER"
2s 445ms
Then
Check are advice values equals
4s 326ms
After
Hooks.deleteTransportAfterTest()
127ms
After
Hooks.cleanUserDetailsAfterTest()
278ms
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"
2s 100ms
And
Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file
468ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
036ms
And
Add transport by SKApi in "MGW" assigned to ""
003ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
5s 836ms
When
Click button advice in transport table "TRANSPORT_ORDER"
094ms
And
Set advice window in schedule
2s 538ms
And
Fill advice form
16s 813ms
And
Click advice save button and wait for advice form to disappear
30s 769ms
And
Go to "TRANSPORT_TABLE"
187ms
And
Go to transport details "TRANSPORT_ORDER"
2s 429ms
Then
Check are advice values equals
4s 340ms
After
Hooks.deleteTransportAfterTest()
101ms
After
Hooks.cleanUserDetailsAfterTest()
340ms
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"
1s 816ms
And
Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file
220ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
037ms
And
Add transport by SKApi in "MGW" assigned to "automaty@test.pl"
003ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 850ms
When
Click button advice in transport table "TRANSPORT_ORDER"
091ms
And
Set advice window in schedule
30s 541ms
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:90)
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', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-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:90)
at sun.reflect.GeneratedMethodAccessor242.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()
094ms
After
Hooks.cleanUserDetailsAfterTest()
264ms
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"
1s 815ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
325ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
037ms
And
Add transport by SKApi in "MGW" assigned to ""
003ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
034ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 385ms
When
Click button advice in transport table "OWN_COLLECTION"
091ms
And
Set advice window in schedule
2s 548ms
And
Fill advice form
16s 714ms
And
Click advice save button and wait for advice form to disappear
30s 750ms
And
Go to "TRANSPORT_TABLE"
189ms
Then
Check advice data in SK API database "OWN_COLLECTION"
154ms
After
Hooks.deleteTransportAfterTest()
104ms
After
Hooks.cleanUserDetailsAfterTest()
289ms
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"
1s 859ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
383ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
037ms
And
Add transport by SKApi in "MGW" assigned to ""
004ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 338ms
When
Click button advice in transport table "CONTAINER"
073ms
And
Set advice window in schedule
2s 580ms
And
Fill advice form
16s 771ms
And
Click advice save button and wait for advice form to disappear
30s 765ms
And
Go to "TRANSPORT_TABLE"
156ms
Then
Check advice data in SK API database "CONTAINER"
100ms
After
Hooks.deleteTransportAfterTest()
117ms
After
Hooks.cleanUserDetailsAfterTest()
284ms
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"
1s 809ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
359ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
037ms
And
Add transport by SKApi in "MGW" assigned to ""
004ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
5s 814ms
When
Click button advice in transport table "TRANSPORT_ORDER"
101ms
And
Set advice window in schedule
2s 537ms
And
Fill advice form
16s 847ms
And
Click advice save button and wait for advice form to disappear
30s 720ms
And
Go to "TRANSPORT_TABLE"
197ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
042ms
After
Hooks.deleteTransportAfterTest()
099ms
After
Hooks.cleanUserDetailsAfterTest()
272ms
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"
1s 753ms
And
Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file
456ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
036ms
And
Add transport by SKApi in "MGW" assigned to ""
002ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
2s 788ms
When
Click button advice in transport table "TRANSPORT_ORDER"
093ms
And
Set advice window in schedule
2s 568ms
And
Fill advice form
16s 730ms
And
Click advice save button and wait for advice form to disappear
30s 744ms
And
Go to "TRANSPORT_TABLE"
215ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
035ms
After
Hooks.deleteTransportAfterTest()
097ms
After
Hooks.cleanUserDetailsAfterTest()
334ms
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-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz"
2s 029ms
And
Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file
261ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
037ms
And
Add transport by SKApi in "MGW" assigned to "automaty@test.pl"
003ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
034ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
1s 137ms
When
Click button advice in transport table "TRANSPORT_ORDER"
093ms
And
Set advice window in schedule
2s 552ms
And
Fill advice form
16s 746ms
And
Click advice save button and wait for advice form to disappear
30s 754ms
And
Go to "TRANSPORT_TABLE"
204ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
085ms
After
Hooks.deleteTransportAfterTest()
112ms
After
Hooks.cleanUserDetailsAfterTest()
249ms
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"
1s 798ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
036ms
And
Add transport by SKApi in "MGW" assigned to ""
002ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "CONTAINER" created in transport table and set transport id
3s 331ms
When
Click button advice in transport table "CONTAINER"
076ms
And
Set advice window in schedule in the past
2s 526ms
And
Fill advice form
16s 735ms
And
Click advice save button to check error message
087ms
Then
Check if possible advice alert is displayed
017ms
After
Hooks.deleteTransportAfterTest()
074ms
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"
1s 188ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
038ms
And
Add transport by SKApi in "MGW" assigned to ""
003ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
035ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 381ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
50s 060ms
And
Go to "TRANSPORT_TABLE"
191ms
When
Go to transport details "OWN_COLLECTION"
2s 418ms
And
Expand advice panel
093ms
And
Edit advice in transport details
16s 093ms
And
Fill arrival date field
2s 280ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 096ms
Then
Check advice data in database after edition "OWN_COLLECTION"
032ms
After
Hooks.deleteTransportAfterTest()
124ms
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"
1s 210ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW" assigned to ""
003ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
033ms
And
Check is transport "CONTAINER" created in transport table and set transport id
3s 313ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
50s 201ms
And
Go to "TRANSPORT_TABLE"
166ms
When
Go to transport details "CONTAINER"
2s 452ms
And
Expand advice panel
089ms
And
Edit advice in transport details
16s 025ms
And
Fill arrival date field
2s 292ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 159ms
Then
Check advice data in database after edition "CONTAINER"
032ms
After
Hooks.deleteTransportAfterTest()
111ms
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"
1s 243ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
038ms
And
Add transport by SKApi in "MGW" assigned to ""
003ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
033ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
6s 203ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
50s 133ms
And
Go to "TRANSPORT_TABLE"
217ms
When
Go to transport details "TRANSPORT_ORDER"
2s 454ms
And
Expand advice panel
090ms
And
Edit advice in transport details
16s 149ms
And
Fill arrival date field
2s 268ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 099ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
032ms
After
Hooks.deleteTransportAfterTest()
121ms