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 034ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
353ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
6s 299ms
When
Click button advice in transport table "CONTAINER"
096ms
And
Set advice window in schedule
2s 516ms
And
Fill advice form
14s 475ms
And
Click advice save button and wait for advice form to disappear
30s 760ms
And
Go to "TRANSPORT_TABLE"
183ms
And
Go to transport details "CONTAINER"
2s 496ms
Then
Check are advice values equals
2s 263ms
After
Hooks.deleteTransportAfterTest()
117ms
After
Hooks.cleanUserDetailsAfterTest()
291ms
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 886ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
336ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
048ms
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 343ms
When
Click button advice in transport table "OWN_COLLECTION"
097ms
And
Set advice window in schedule
2s 523ms
And
Fill advice form
14s 435ms
And
Click advice save button and wait for advice form to disappear
30s 678ms
And
Go to "TRANSPORT_TABLE"
184ms
And
Go to transport details "OWN_COLLECTION"
2s 429ms
Then
Check are advice values equals
2s 277ms
After
Hooks.deleteTransportAfterTest()
122ms
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)
001ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
1s 844ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
334ms
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
5s 810ms
When
Click button advice in transport table "TRANSPORT_ORDER"
099ms
And
Set advice window in schedule
2s 519ms
And
Fill advice form
14s 466ms
And
Click advice save button and wait for advice form to disappear
30s 707ms
And
Go to "TRANSPORT_TABLE"
215ms
And
Go to transport details "TRANSPORT_ORDER"
2s 455ms
Then
Check are advice values equals
2s 269ms
After
Hooks.deleteTransportAfterTest()
124ms
After
Hooks.cleanUserDetailsAfterTest()
319ms
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"
1s 999ms
And
Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file
471ms
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"
035ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 827ms
When
Click button advice in transport table "TRANSPORT_ORDER"
100ms
And
Set advice window in schedule
2s 543ms
And
Fill advice form
14s 532ms
And
Click advice save button and wait for advice form to disappear
30s 680ms
And
Go to "TRANSPORT_TABLE"
232ms
And
Go to transport details "TRANSPORT_ORDER"
2s 426ms
Then
Check are advice values equals
2s 292ms
After
Hooks.deleteTransportAfterTest()
109ms
After
Hooks.cleanUserDetailsAfterTest()
335ms
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-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz"
1s 869ms
And
Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file
284ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
036ms
And
Add transport by SKApi in "MGW" assigned to "automaty@test.pl"
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
3s 818ms
When
Click button advice in transport table "TRANSPORT_ORDER"
108ms
And
Set advice window in schedule
30s 557ms
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()
092ms
After
Hooks.cleanUserDetailsAfterTest()
211ms
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 829ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
348ms
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"
036ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 377ms
When
Click button advice in transport table "OWN_COLLECTION"
091ms
And
Set advice window in schedule
2s 510ms
And
Fill advice form
14s 400ms
And
Click advice save button and wait for advice form to disappear
30s 720ms
And
Go to "TRANSPORT_TABLE"
194ms
Then
Check advice data in SK API database "OWN_COLLECTION"
152ms
After
Hooks.deleteTransportAfterTest()
120ms
After
Hooks.cleanUserDetailsAfterTest()
273ms
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-admin" and set token of apiUsername "super-admin-skz"
1s 832ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
328ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
038ms
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 327ms
When
Click button advice in transport table "CONTAINER"
092ms
And
Set advice window in schedule
2s 542ms
And
Fill advice form
14s 439ms
And
Click advice save button and wait for advice form to disappear
30s 771ms
And
Go to "TRANSPORT_TABLE"
178ms
Then
Check advice data in SK API database "CONTAINER"
114ms
After
Hooks.deleteTransportAfterTest()
116ms
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)
000ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
1s 819ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
315ms
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"
033ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 830ms
When
Click button advice in transport table "TRANSPORT_ORDER"
087ms
And
Set advice window in schedule
2s 500ms
And
Fill advice form
14s 514ms
And
Click advice save button and wait for advice form to disappear
30s 728ms
And
Go to "TRANSPORT_TABLE"
218ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
032ms
After
Hooks.deleteTransportAfterTest()
099ms
After
Hooks.cleanUserDetailsAfterTest()
306ms
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 767ms
And
Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file
438ms
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"
035ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
5s 732ms
When
Click button advice in transport table "TRANSPORT_ORDER"
087ms
And
Set advice window in schedule
2s 512ms
And
Fill advice form
14s 470ms
And
Click advice save button and wait for advice form to disappear
30s 678ms
And
Go to "TRANSPORT_TABLE"
244ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
037ms
After
Hooks.deleteTransportAfterTest()
099ms
After
Hooks.cleanUserDetailsAfterTest()
332ms
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"
1s 965ms
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"
033ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
2s 903ms
When
Click button advice in transport table "TRANSPORT_ORDER"
104ms
And
Set advice window in schedule
2s 519ms
And
Fill advice form
14s 459ms
And
Click advice save button and wait for advice form to disappear
30s 716ms
And
Go to "TRANSPORT_TABLE"
185ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
088ms
After
Hooks.deleteTransportAfterTest()
118ms
After
Hooks.cleanUserDetailsAfterTest()
211ms
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 769ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
038ms
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 319ms
When
Click button advice in transport table "CONTAINER"
100ms
And
Set advice window in schedule in the past
2s 513ms
And
Fill advice form
14s 414ms
And
Click advice save button to check error message
074ms
Then
Check if possible advice alert is displayed
019ms
After
Hooks.deleteTransportAfterTest()
079ms
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 166ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
037ms
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 375ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
47s 765ms
And
Go to "TRANSPORT_TABLE"
181ms
When
Go to transport details "OWN_COLLECTION"
2s 412ms
And
Expand advice panel
093ms
And
Edit advice in transport details
13s 858ms
And
Fill arrival date field
2s 296ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 111ms
Then
Check advice data in database after edition "OWN_COLLECTION"
033ms
After
Hooks.deleteTransportAfterTest()
116ms
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 182ms
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 335ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
47s 792ms
And
Go to "TRANSPORT_TABLE"
192ms
When
Go to transport details "CONTAINER"
2s 469ms
And
Expand advice panel
096ms
And
Edit advice in transport details
13s 889ms
And
Fill arrival date field
2s 283ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 090ms
Then
Check advice data in database after edition "CONTAINER"
032ms
After
Hooks.deleteTransportAfterTest()
137ms
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 194ms
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"
035ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
6s 207ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
47s 788ms
And
Go to "TRANSPORT_TABLE"
215ms
When
Go to transport details "TRANSPORT_ORDER"
2s 444ms
And
Expand advice panel
088ms
And
Edit advice in transport details
13s 931ms
And
Fill arrival date field
2s 278ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 077ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
035ms
After
Hooks.deleteTransportAfterTest()
107ms