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 067ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
353ms
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 300ms
When
Click button advice in transport table "CONTAINER"
085ms
And
Set advice window in schedule
2s 541ms
And
Fill advice form
14s 431ms
And
Click advice save button and wait for advice form to disappear
30s 744ms
And
Go to "TRANSPORT_TABLE"
185ms
And
Go to transport details "CONTAINER"
2s 452ms
Then
Check are advice values equals
2s 264ms
After
Hooks.deleteTransportAfterTest()
110ms
After
Hooks.cleanUserDetailsAfterTest()
271ms
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)
002ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
1s 853ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
335ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id
3s 355ms
When
Click button advice in transport table "OWN_COLLECTION"
102ms
And
Set advice window in schedule
2s 526ms
And
Fill advice form
14s 438ms
And
Click advice save button and wait for advice form to disappear
30s 732ms
And
Go to "TRANSPORT_TABLE"
182ms
And
Go to transport details "OWN_COLLECTION"
2s 425ms
Then
Check are advice values equals
2s 292ms
After
Hooks.deleteTransportAfterTest()
143ms
After
Hooks.cleanUserDetailsAfterTest()
268ms
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 905ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
346ms
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 803ms
When
Click button advice in transport table "TRANSPORT_ORDER"
085ms
And
Set advice window in schedule
2s 547ms
And
Fill advice form
14s 437ms
And
Click advice save button and wait for advice form to disappear
30s 710ms
And
Go to "TRANSPORT_TABLE"
222ms
And
Go to transport details "TRANSPORT_ORDER"
2s 437ms
Then
Check are advice values equals
2s 287ms
After
Hooks.deleteTransportAfterTest()
099ms
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)
001ms
Given
Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz"
2s 092ms
And
Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file
490ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
043ms
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
2s 797ms
When
Click button advice in transport table "TRANSPORT_ORDER"
082ms
And
Set advice window in schedule
2s 516ms
And
Fill advice form
14s 426ms
And
Click advice save button and wait for advice form to disappear
30s 727ms
And
Go to "TRANSPORT_TABLE"
216ms
And
Go to transport details "TRANSPORT_ORDER"
2s 426ms
Then
Check are advice values equals
2s 281ms
After
Hooks.deleteTransportAfterTest()
109ms
After
Hooks.cleanUserDetailsAfterTest()
375ms
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 767ms
And
Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file
267ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
042ms
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
5s 885ms
When
Click button advice in transport table "TRANSPORT_ORDER"
102ms
And
Set advice window in schedule
30s 598ms
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', 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:85)
at sun.reflect.GeneratedMethodAccessor240.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()
062ms
After
Hooks.cleanUserDetailsAfterTest()
213ms
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 801ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
338ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
039ms
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
6s 373ms
When
Click button advice in transport table "OWN_COLLECTION"
102ms
And
Set advice window in schedule
2s 526ms
And
Fill advice form
14s 436ms
And
Click advice save button and wait for advice form to disappear
30s 719ms
And
Go to "TRANSPORT_TABLE"
172ms
Then
Check advice data in SK API database "OWN_COLLECTION"
155ms
After
Hooks.deleteTransportAfterTest()
114ms
After
Hooks.cleanUserDetailsAfterTest()
290ms
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 833ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
324ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
3s 304ms
When
Click button advice in transport table "CONTAINER"
089ms
And
Set advice window in schedule
2s 532ms
And
Fill advice form
14s 394ms
And
Click advice save button and wait for advice form to disappear
30s 685ms
And
Go to "TRANSPORT_TABLE"
190ms
Then
Check advice data in SK API database "CONTAINER"
105ms
After
Hooks.deleteTransportAfterTest()
100ms
After
Hooks.cleanUserDetailsAfterTest()
258ms
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 821ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
318ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
039ms
And
Add transport by SKApi in "MGW" assigned to ""
002ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
036ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
5s 843ms
When
Click button advice in transport table "TRANSPORT_ORDER"
095ms
And
Set advice window in schedule
2s 509ms
And
Fill advice form
14s 448ms
And
Click advice save button and wait for advice form to disappear
30s 751ms
And
Go to "TRANSPORT_TABLE"
235ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
031ms
After
Hooks.deleteTransportAfterTest()
107ms
After
Hooks.cleanUserDetailsAfterTest()
325ms
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 "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz"
1s 692ms
And
Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file
516ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
037ms
And
Add transport by SKApi in "MGW" assigned to ""
002ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
038ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 818ms
When
Click button advice in transport table "TRANSPORT_ORDER"
083ms
And
Set advice window in schedule
2s 538ms
And
Fill advice form
14s 489ms
And
Click advice save button and wait for advice form to disappear
30s 699ms
And
Go to "TRANSPORT_TABLE"
204ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
039ms
After
Hooks.deleteTransportAfterTest()
119ms
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)
002ms
Given
Login as "swisskrono-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz"
1s 965ms
And
Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file
272ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
037ms
And
Add transport by SKApi in "MGW" assigned to "automaty@test.pl"
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
3s 792ms
When
Click button advice in transport table "TRANSPORT_ORDER"
089ms
And
Set advice window in schedule
2s 501ms
And
Fill advice form
14s 463ms
And
Click advice save button and wait for advice form to disappear
30s 721ms
And
Go to "TRANSPORT_TABLE"
188ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
090ms
After
Hooks.deleteTransportAfterTest()
121ms
After
Hooks.cleanUserDetailsAfterTest()
245ms
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 853ms
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"
036ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 306ms
When
Click button advice in transport table "CONTAINER"
080ms
And
Set advice window in schedule in the past
2s 538ms
And
Fill advice form
14s 502ms
And
Click advice save button to check error message
083ms
Then
Check if possible advice alert is displayed
018ms
After
Hooks.deleteTransportAfterTest()
075ms
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"
1s 160ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
036ms
And
Add transport by SKApi in "MGW" assigned to ""
002ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
033ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
6s 366ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
47s 735ms
And
Go to "TRANSPORT_TABLE"
158ms
When
Go to transport details "OWN_COLLECTION"
2s 400ms
And
Expand advice panel
087ms
And
Edit advice in transport details
13s 889ms
And
Fill arrival date field
2s 258ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 080ms
Then
Check advice data in database after edition "OWN_COLLECTION"
026ms
After
Hooks.deleteTransportAfterTest()
120ms
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 170ms
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 "EDIT_ADVICE" "super-admin-skz"
033ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 327ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
47s 755ms
And
Go to "TRANSPORT_TABLE"
189ms
When
Go to transport details "CONTAINER"
2s 467ms
And
Expand advice panel
081ms
And
Edit advice in transport details
13s 885ms
And
Fill arrival date field
2s 259ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 084ms
Then
Check advice data in database after edition "CONTAINER"
027ms
After
Hooks.deleteTransportAfterTest()
099ms
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"
1s 137ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
037ms
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 192ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
47s 913ms
And
Go to "TRANSPORT_TABLE"
227ms
When
Go to transport details "TRANSPORT_ORDER"
2s 448ms
And
Expand advice panel
095ms
And
Edit advice in transport details
13s 902ms
And
Fill arrival date field
2s 290ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 081ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
031ms
After
Hooks.deleteTransportAfterTest()
135ms