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 "swisskrono-admin" and set token of apiUsername "super-admin-skz"
1s 051ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
390ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
039ms
And
Add transport by SKApi in "MGW" assigned to ""
002ms
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 312ms
When
Click button advice in transport table "CONTAINER"
092ms
And
Set advice window in schedule
2s 527ms
And
Fill advice form
14s 462ms
And
Click advice save button and wait for advice form to disappear
30s 703ms
And
Go to "TRANSPORT_TABLE"
186ms
And
Go to transport details "CONTAINER"
2s 451ms
Then
Check are advice values equals
2s 288ms
After
Hooks.deleteTransportAfterTest()
107ms
After
Hooks.cleanUserDetailsAfterTest()
272ms
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 "swisskrono-admin" and set token of apiUsername "super-admin-skz"
1s 907ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
318ms
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 "CREATE_ADVICE" "super-admin-skz"
034ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
6s 371ms
When
Click button advice in transport table "OWN_COLLECTION"
100ms
And
Set advice window in schedule
2s 494ms
And
Fill advice form
14s 448ms
And
Click advice save button and wait for advice form to disappear
30s 741ms
And
Go to "TRANSPORT_TABLE"
171ms
And
Go to transport details "OWN_COLLECTION"
2s 425ms
Then
Check are advice values equals
2s 288ms
After
Hooks.deleteTransportAfterTest()
137ms
After
Hooks.cleanUserDetailsAfterTest()
331ms
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 890ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
307ms
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"
033ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
2s 855ms
When
Click button advice in transport table "TRANSPORT_ORDER"
094ms
And
Set advice window in schedule
2s 526ms
And
Fill advice form
14s 475ms
And
Click advice save button and wait for advice form to disappear
30s 735ms
And
Go to "TRANSPORT_TABLE"
233ms
And
Go to transport details "TRANSPORT_ORDER"
2s 470ms
Then
Check are advice values equals
2s 288ms
After
Hooks.deleteTransportAfterTest()
091ms
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)
000ms
Given
Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz"
1s 973ms
And
Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file
480ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "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 "TRANSPORT_ORDER" created in transport table and set transport id
3s 822ms
When
Click button advice in transport table "TRANSPORT_ORDER"
083ms
And
Set advice window in schedule
2s 513ms
And
Fill advice form
14s 495ms
And
Click advice save button and wait for advice form to disappear
30s 718ms
And
Go to "TRANSPORT_TABLE"
215ms
And
Go to transport details "TRANSPORT_ORDER"
2s 424ms
Then
Check are advice values equals
2s 297ms
After
Hooks.deleteTransportAfterTest()
103ms
After
Hooks.cleanUserDetailsAfterTest()
330ms
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 773ms
And
Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file
253ms
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"
035ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
5s 921ms
When
Click button advice in transport table "TRANSPORT_ORDER"
085ms
And
Set advice window in schedule
30s 549ms
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.GeneratedMethodAccessor239.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()
076ms
After
Hooks.cleanUserDetailsAfterTest()
251ms
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 777ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
353ms
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"
036ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
6s 381ms
When
Click button advice in transport table "OWN_COLLECTION"
089ms
And
Set advice window in schedule
2s 533ms
And
Fill advice form
14s 465ms
And
Click advice save button and wait for advice form to disappear
30s 706ms
And
Go to "TRANSPORT_TABLE"
183ms
Then
Check advice data in SK API database "OWN_COLLECTION"
161ms
After
Hooks.deleteTransportAfterTest()
118ms
After
Hooks.cleanUserDetailsAfterTest()
285ms
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 991ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
306ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
038ms
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
3s 313ms
When
Click button advice in transport table "CONTAINER"
089ms
And
Set advice window in schedule
2s 535ms
And
Fill advice form
14s 429ms
And
Click advice save button and wait for advice form to disappear
30s 691ms
And
Go to "TRANSPORT_TABLE"
184ms
Then
Check advice data in SK API database "CONTAINER"
086ms
After
Hooks.deleteTransportAfterTest()
113ms
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 "swisskrono-admin" and set token of apiUsername "super-admin-skz"
1s 774ms
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"
037ms
And
Add transport by SKApi in "MGW" assigned to ""
001ms
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 815ms
When
Click button advice in transport table "TRANSPORT_ORDER"
080ms
And
Set advice window in schedule
2s 534ms
And
Fill advice form
14s 443ms
And
Click advice save button and wait for advice form to disappear
30s 750ms
And
Go to "TRANSPORT_TABLE"
209ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
031ms
After
Hooks.deleteTransportAfterTest()
112ms
After
Hooks.cleanUserDetailsAfterTest()
309ms
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 758ms
And
Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file
476ms
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 "CREATE_ADVICE" "super-admin-skz"
036ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
2s 846ms
When
Click button advice in transport table "TRANSPORT_ORDER"
088ms
And
Set advice window in schedule
2s 536ms
And
Fill advice form
14s 436ms
And
Click advice save button and wait for advice form to disappear
30s 764ms
And
Go to "TRANSPORT_TABLE"
226ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
038ms
After
Hooks.deleteTransportAfterTest()
121ms
After
Hooks.cleanUserDetailsAfterTest()
352ms
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"
2s 047ms
And
Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file
253ms
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
3s 815ms
When
Click button advice in transport table "TRANSPORT_ORDER"
087ms
And
Set advice window in schedule
2s 511ms
And
Fill advice form
14s 484ms
And
Click advice save button and wait for advice form to disappear
30s 737ms
And
Go to "TRANSPORT_TABLE"
172ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
085ms
After
Hooks.deleteTransportAfterTest()
128ms
After
Hooks.cleanUserDetailsAfterTest()
235ms
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)
002ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
1s 741ms
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"
033ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 309ms
When
Click button advice in transport table "CONTAINER"
086ms
And
Set advice window in schedule in the past
2s 503ms
And
Fill advice form
14s 501ms
And
Click advice save button to check error message
084ms
Then
Check if possible advice alert is displayed
020ms
After
Hooks.deleteTransportAfterTest()
092ms
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 176ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
038ms
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 369ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
47s 896ms
And
Go to "TRANSPORT_TABLE"
176ms
When
Go to transport details "OWN_COLLECTION"
2s 426ms
And
Expand advice panel
094ms
And
Edit advice in transport details
13s 909ms
And
Fill arrival date field
2s 287ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 064ms
Then
Check advice data in database after edition "OWN_COLLECTION"
033ms
After
Hooks.deleteTransportAfterTest()
112ms
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 193ms
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 "EDIT_ADVICE" "super-admin-skz"
034ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 296ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
47s 813ms
And
Go to "TRANSPORT_TABLE"
196ms
When
Go to transport details "CONTAINER"
2s 525ms
And
Expand advice panel
084ms
And
Edit advice in transport details
13s 872ms
And
Fill arrival date field
2s 267ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 115ms
Then
Check advice data in database after edition "CONTAINER"
031ms
After
Hooks.deleteTransportAfterTest()
105ms
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 167ms
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 "EDIT_ADVICE" "super-admin-skz"
034ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
6s 208ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
47s 806ms
And
Go to "TRANSPORT_TABLE"
207ms
When
Go to transport details "TRANSPORT_ORDER"
2s 440ms
And
Expand advice panel
089ms
And
Edit advice in transport details
13s 901ms
And
Fill arrival date field
2s 271ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 106ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
027ms
After
Hooks.deleteTransportAfterTest()
111ms